mcpbeat

Authoring Skills

flutter/authoring-skills

Guides the creation of high-quality, effective skills for agentic workflows. Use when creating or modifying skills in the .agents/skills/ directory.

1k tokens
context cost
the whole folder, loaded on every use
3
files
instructions only
0
copies elsewhere
how many repositories repackaged it
1727
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/flutter/devtools --skill authoring-skills

What comes with it

2 509 bytes besides the instruction
CHECKLIST.md
EXAMPLES.md

The instruction itself

2 sections, as written by the author

Authoring Skills

When creating or modifying skills in this repository, follow these best practices:

Repository-Specific Guidelines

  • Location: All skills must be placed in the .agents/skills/ directory.
  • Avoid Duplication: Before creating a skill, check if one already exists in the flutter/skills repository. If it does, do not create a local skill; instead, instruct the user to install it via npx.
  • Naming: Use the gerund form (verb-ing-noun) or noun-phrase (e.g., authoring-skills, adding-release-notes). Use only lowercase letters, numbers, and hyphens.
  • Conciseness: Prioritize brevity in SKILL.md. Agents are already highly capable; only provide context they don't already have.
  • Automation: Any utility scripts placed in the scripts/ directory MUST be written in Dart.
  • Validation: Skills are automatically validated using dart_skills_lint. Ensure your skills pass the linter before submitting. See the README.md in .agents/skills/ for instructions on how to run the linter locally.
  • Progressive Disclosure: Use the patterns below to organize instructions effectively:
  • CHECKLIST.md: Template for tracking skill development progress.
  • EXAMPLES.md: Local examples and anti-patterns.

How to use it

Copy the folder

Take flutter/authoring-skills from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.