using-kit
Use when starting any conversation to establish skill discovery and usage patterns
Overall
score
61%
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
0%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 description fails on all dimensions. It uses abstract internal terminology instead of concrete actions, contains no natural user keywords, and the trigger condition 'starting any conversation' would cause it to conflict with every other skill. The description appears to be meta-level guidance rather than a functional skill description.
Suggestions
Replace abstract language with specific concrete actions (e.g., 'Lists available skills, explains skill capabilities, recommends appropriate skills for tasks').
Add natural trigger terms users would actually say (e.g., 'what can you do', 'help me find', 'which skill', 'capabilities').
Narrow the 'Use when' clause to specific scenarios rather than 'any conversation' (e.g., 'Use when user asks about available capabilities, requests help finding the right tool, or says phrases like "what skills do you have"').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions - 'establish skill discovery and usage patterns' is abstract language with no specific capabilities listed. | 1 / 3 |
Completeness | The 'what' is extremely vague ('establish skill discovery and usage patterns') and while there's a 'when' clause ('starting any conversation'), it's overly broad and doesn't provide meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | Contains no natural keywords users would say. Terms like 'skill discovery' and 'usage patterns' are internal/technical jargon, not user language. | 1 / 3 |
Distinctiveness Conflict Risk | 'Starting any conversation' would trigger on virtually every interaction, creating maximum conflict with all other skills. This is the opposite of distinctive. | 1 / 3 |
Total | 4 / 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 strong meta-skill that clearly establishes skill discovery and usage patterns. The workflow clarity and actionability are excellent with concrete decision trees and explicit chains. Minor verbosity in the Red Flags section and emphatic opening could be tightened without losing clarity.
Suggestions
Condense the 'Red Flags' table by grouping similar rationalizations (e.g., 'I need context/information first' patterns could be one row)
The EXTREMELY-IMPORTANT block could be integrated into 'The Rule' section more concisely rather than using emphatic formatting
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is moderately efficient but includes some redundancy (the 'Red Flags' table is extensive and repetitive, the EXTREMELY-IMPORTANT block is emphatic but could be tighter). The dot graph and tables add value but the overall content could be trimmed. | 2 / 3 |
Actionability | Provides concrete, actionable guidance: specific workflow chain (brainstorming → writing-plans → team-dev → finish-branch), clear decision points, explicit tool usage ('Use the Skill tool'), and a detailed flowchart showing exact decision logic. | 3 / 3 |
Workflow Clarity | The workflow is exceptionally clear with a visual flowchart, numbered default workflow chain, explicit priority ordering, and clear decision points. The 'Red Flags' table serves as validation checkpoints against common failure modes. | 3 / 3 |
Progressive Disclosure | Well-structured with clear sections (How to Access, The Rule, Default Workflow Chain, Team Context, Red Flags, Skill Priority, Skill Types). References other skills by name without deep nesting. Appropriate length for a governance/meta-skill. | 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.