packmind-create-skill
tessl i github:cteyton/packmind --skill packmind-create-skillGuide 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.
Validation
88%| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
Total | 14 / 16 Passed | |
Implementation
77%This is a well-structured, actionable skill with excellent workflow clarity and concrete executable guidance. Its main weakness is length—the 'About Skills' section contains conceptual explanations that could be moved to a reference file, and some content explains things Claude likely already understands. The progressive disclosure principle it teaches isn't fully applied to itself.
Suggestions
Move the 'About Skills' conceptual overview (What Skills Provide, Anatomy of a Skill, Progressive Disclosure Design Principle) to a references/skill-concepts.md file, keeping only essential procedural content in SKILL.md
Remove or condense explanatory text like 'Think of them as onboarding guides' and 'they transform Claude from a general-purpose agent'—Claude understands these concepts
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary explanations (e.g., 'Think of them as onboarding guides', explaining what skills provide in abstract terms) and could be tightened. However, it's not excessively verbose and most content serves a purpose. | 2 / 3 |
Actionability | Provides fully executable commands throughout (python3 scripts/init_skill.py, packmind-cli skills add, validation scripts), concrete examples for each step, and copy-paste ready code blocks with clear usage patterns. | 3 / 3 |
Workflow Clarity | Excellent multi-step workflow with 8 clearly numbered steps, explicit validation checkpoint (Step 5) before distribution, and clear iteration feedback loop (Step 6). Prerequisites are checked before each script execution. | 3 / 3 |
Progressive Disclosure | The skill is well-structured with clear sections, but it's quite long (~1500 words) and could benefit from moving detailed content (like the 'Anatomy of a Skill' section or 'What Skills Provide') to reference files. The content is all inline rather than appropriately split. | 2 / 3 |
Total | 10 / 12 Passed |
Activation
75%This description adequately communicates its purpose and includes explicit 'when to use' guidance, which is a strength. However, it lacks specific concrete actions (what exactly does 'creating effective skills' involve?) and could benefit from more natural trigger terms that users might actually say when they need this skill.
Suggestions
Add specific concrete actions like 'write YAML frontmatter, define trigger conditions, structure skill content sections, add usage examples'
Include additional trigger terms users might naturally say: 'write a skill', 'skill file', 'SKILL.md', 'teach Claude', 'new capability'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (creating skills) and mentions some actions ('create a new skill', 'update an existing skill'), but lacks concrete specific actions like 'write YAML frontmatter', 'define trigger conditions', or 'structure skill content'. | 2 / 3 |
Completeness | Clearly answers both what ('Guide for creating effective skills') and when ('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'). | 3 / 3 |
Trigger Term Quality | Includes relevant keywords like 'skill', 'create', 'update', but misses common variations users might say such as 'write a skill', 'new capability', 'skill file', 'SKILL.md', or 'extend Claude'. | 2 / 3 |
Distinctiveness Conflict Risk | Has a clear niche focused specifically on skill creation/modification, which is distinct from general documentation or coding skills. The explicit mention of 'extends Claude's capabilities' makes it unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.