AI Skill Report Card

Creating Skills

Creates new skills for the sales_engineer workspace. Use when user says "create skill", "add skill", "new skill", "save as skill", or describes a repetitive workflow that should be automated.

A-88·Mar 6, 2026·Source: Web
15 / 15

Create skills/[name].md:

Markdown
--- name: kebab-case-name description: What it does + when to trigger, third person --- # Title
Recommendation
Add more edge cases like handling skills that need external files or complex workflows

[Brief steps - Claude is smart, don't explain basics]

19 / 20

[Input → Output pairs if output format matters]

Recommendation
Include a template section showing the full structure for different skill types (simple vs complex)
15 / 15

Step 1 — Understand the skill

Ask user (if not obvious from context):

  1. What should the skill do?
  2. When should Claude apply it — what phrases or situations trigger it?

Step 2 — Create file

Create skills/[name].md with structure:

  • YAML frontmatter with name and description
  • Brief instructions (Claude knows basics)
  • Examples if output format is important

Step 3 — Confirm

Say: "Skill '[name]' created in skills/. Trigger: [when]."

Recommendation
Add guidance on testing skills after creation to ensure they trigger properly
19 / 20

Input: "Save as skill: before sending emails, always check tone via SerpAPI"

Output: File skills/email-tone-check.md:

Markdown
--- name: email-tone-check description: Checks cold email tone before sending. Use when user says "check email", "is email ready", "can I send this". --- # Email Tone Check
  1. Read the email
  2. Check: no pressure, has personalization, clear value
  3. Give rating and 1-2 specific edits if needed
  • description is crucial - Claude decides whether to use skill based on this
  • Write third person in description ("Creates..." not "I create...")
  • Don't explain what Claude already knows
  • If skill is large - main file contains overview only, details in separate files
  • File paths: projects/[project]/ for projects, skills/ for skills
  • Don't make description too generic
  • Don't include implementation details in description
  • Don't forget the trigger phrases in description
0
Grade A-AI Skill Framework
Scorecard
Criteria Breakdown
Quick Start
15/15
Workflow
15/15
Examples
19/20
Completeness
10/20
Format
15/15
Conciseness
14/15