skill-creator
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 Gemini CLI's capabilities with specialized knowledge, workflows, or tool integrations.
Install with Tessl CLI
npx tessl i github:google-gemini/gemini-cli --skill skill-creator82
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillAgent success when using this skill
Validation for skill structure
Discovery
67%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description adequately explains what the skill does and when to use it, earning a strong completeness score. However, it lacks specific concrete actions (like defining YAML frontmatter or structuring skill files) and could benefit from more natural trigger term variations. The reference to 'Gemini CLI' rather than the expected platform may indicate a mismatch or error.
Suggestions
Add more specific concrete actions like 'write YAML frontmatter', 'define skill triggers', 'structure markdown skill files' to improve specificity.
Include additional natural trigger terms users might say: 'write a skill', 'add a skill', 'skill template', 'new capability', '.md skill file'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain ('creating effective skills') and mentions some actions ('create a new skill', 'update an existing skill', 'extends capabilities'), but lacks concrete specific actions like 'write YAML frontmatter', 'define triggers', or 'structure markdown content'. | 2 / 3 |
Completeness | Clearly answers both what ('Guide for creating effective skills' that 'extends Gemini CLI's capabilities with specialized knowledge, workflows, or tool integrations') and when ('when users want to create a new skill or update an existing skill'). | 3 / 3 |
Trigger Term Quality | Includes relevant keywords like 'create a new skill', 'update an existing skill', and 'Gemini CLI', but missing common variations users might say like 'write a skill', 'add a skill', 'skill template', or 'skill file'. | 2 / 3 |
Distinctiveness Conflict Risk | Reasonably specific to skill creation for Gemini CLI, but could potentially conflict with general documentation or template skills. The mention of 'Gemini CLI' helps distinguish it, though 'specialized knowledge, workflows, or tool integrations' is somewhat broad. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, comprehensive skill creation guide with excellent workflow clarity and progressive disclosure. The actionability is strong with concrete commands and examples throughout. The main weakness is some verbosity in explanatory sections that could be trimmed, particularly the 'About Skills' section which explains concepts Gemini CLI likely already understands.
Suggestions
Trim the 'About Skills' and 'What Skills Provide' sections significantly - Gemini CLI doesn't need explanations of what skills are or why they're useful
Remove or condense the 'Core Principles' explanations that describe general concepts (e.g., the bridge/field metaphor for degrees of freedom) and focus on actionable guidance
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary explanations (e.g., explaining what skills are, what PDFs are in examples) and could be tightened. However, it generally provides useful information without excessive padding, and the examples are helpful rather than verbose. | 2 / 3 |
Actionability | The skill provides concrete, executable guidance including specific script commands (init_skill.cjs, package_skill.cjs), exact directory structures, code examples, and copy-paste ready bash commands for installation. The step-by-step process is fully actionable. | 3 / 3 |
Workflow Clarity | The 7-step skill creation process is clearly sequenced with explicit validation built into the packaging step. Each step has clear entry/exit criteria, and the workflow includes feedback loops (Step 7: Iterate) for error recovery and improvement. | 3 / 3 |
Progressive Disclosure | The skill demonstrates excellent progressive disclosure with clear references to external files (references/workflows.md, references/output-patterns.md), well-organized sections, and appropriate content splitting. Navigation is clear with one-level-deep references. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.