Load, activate, and optionally install an AI skill from a .skill file. Use this skill when the user wants to load, activate, or use a skill file. The user can invoke this skill with slash command `/load-skill [ --install | -i ] SKILLFILE`, where SKILLFILE is the path to a .skill file.
89
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/skillValidation for skill structure
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that excels across all dimensions. It provides specific actions, includes natural trigger terms users would say, explicitly states both what it does and when to use it, and has a clear distinctive niche with the .skill file focus and slash command syntax.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Load, activate, and optionally install an AI skill from a .skill file.' These are clear, actionable verbs describing exactly what the skill does. | 3 / 3 |
Completeness | Clearly answers both what ('Load, activate, and optionally install an AI skill from a .skill file') AND when ('Use this skill when the user wants to load, activate, or use a skill file') with explicit triggers and even includes the slash command syntax. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'load', 'activate', 'install', 'skill file', '.skill file', plus the explicit slash command '/load-skill'. Good coverage of terms a user would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche with distinct triggers - specifically targets '.skill' files and skill loading/activation. The explicit file extension and slash command make it highly unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides clear, actionable instructions for loading skill files with good structure and concrete examples. The main weaknesses are missing error handling/validation steps for file operations and some minor verbosity that could be trimmed. The workflow would benefit from explicit checkpoints for common failure modes.
Suggestions
Add validation checkpoints after steps 2-4 (e.g., 'If file doesn't exist, inform user and stop', 'If SKILL.md not found, report error with extracted contents')
Remove the screenshot mention in the intro as it adds no value for the AI agent
Add error recovery guidance for common failures: invalid zip format, missing SKILL.md, permission denied on install directory
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some unnecessary explanation like the screenshot mention and could be tightened. The step-by-step instructions are clear but slightly verbose for an AI agent that understands file operations. | 2 / 3 |
Actionability | Provides concrete, executable commands (unzip with specific flags), clear argument parsing instructions, and specific examples of usage. The workflow is copy-paste ready with actual bash commands. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced, but lacks explicit validation checkpoints. No error handling guidance for common failures (invalid zip, missing SKILL.md, permission issues) which are important for file operations. | 2 / 3 |
Progressive Disclosure | For a skill of this size (~80 lines), the structure is appropriate with clear sections (Usage, How to Process, Examples, Notes). No unnecessary external references and content is well-organized for quick scanning. | 3 / 3 |
Total | 10 / 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.
Table of Contents
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.