mcpbeat Sign in

Authoring Skills for Claude

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

448 tokens
context cost
SKILL.md, read when the skill is used
3
files
plus reference files
0
copies elsewhere
how many repositories repackaged it
1 727
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.

Other skills for the same job

different authors, same section of the catalogue
Skill Creator
by anthropics
vendor ×12

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.

8.3k tokens scripts
Skill Creator
by vercel-labs
vendor ×12

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.

4.5k tokens scripts
Skill Creator
by JayZeeDesign
×9

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.

2.9k tokens scripts
Dispatching Parallel Agents
by ZhanlinCui
×7

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

1.5k tokens
Template Skill
by JayZeeDesign
×7

Replace with description of the skill and when Claude should use it.

35 tokens
Writing Skills
by ZhanlinCui
×6

Use when creating new skills, editing existing skills, or verifying skills work before deployment

5.6k tokens scripts
Skill Development
by anthropics
vendor ×5

This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.

5.7k tokens
Subagent Driven Development
by ZhanlinCui
×5

Use when executing implementation plans with independent tasks in the current session

2.5k tokens

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.