skill-tuning
Universal skill diagnosis and optimization tool. Detect and fix skill execution issues including context explosion, long-tail forgetting, data flow disruption, and agent coordination failures. Supports Gemini CLI for deep analysis. Triggers on "skill tuning", "tune skill", "skill diagnosis", "optimize skill", "skill debug".
65
78%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.claude/skills/skill-tuning/SKILL.mdQuality
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 strong description that clearly communicates what the skill does (diagnose and fix skill execution issues), lists specific problem types it addresses, and provides explicit trigger terms. It uses proper third-person voice and is concise without being vague. The only minor note is that 'Universal skill diagnosis and optimization tool' is slightly grandiose but is immediately backed up with concrete specifics.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Detect and fix skill execution issues including context explosion, long-tail forgetting, data flow disruption, and agent coordination failures.' Also mentions Gemini CLI support for deep analysis. | 3 / 3 |
Completeness | Clearly answers both what ('Detect and fix skill execution issues including context explosion, long-tail forgetting, data flow disruption, and agent coordination failures') and when ('Triggers on "skill tuning", "tune skill", "skill diagnosis", "optimize skill", "skill debug"'). | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger terms: 'skill tuning', 'tune skill', 'skill diagnosis', 'optimize skill', 'skill debug'. These are terms users would naturally say when needing this functionality, with good variation coverage. | 3 / 3 |
Distinctiveness Conflict Risk | Occupies a clear niche around skill diagnosis and optimization with very specific trigger terms. The domain of 'skill execution issues' like 'context explosion' and 'long-tail forgetting' is distinctive and unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a well-structured overview of a complex diagnostic and optimization framework with good progressive disclosure and clear categorization of problems and actions. Its main weaknesses are that actionable implementation details are almost entirely deferred to referenced files (none of which are available for verification), and the workflow lacks inline validation checkpoints for what are potentially destructive fix operations. The content reads more as an architectural specification than an actionable skill guide.
Suggestions
Add at least one concrete, executable example of a diagnosis action (e.g., a detection pattern or code snippet for context explosion detection) directly in the SKILL.md rather than deferring everything to referenced files.
Include explicit validation/feedback loops inline in the workflow section, e.g., 'If action-verify fails → revert via backup → re-diagnose → re-apply' with specific commands or state transitions.
Reduce redundancy between the Architecture diagram, Workflow table, and Action Reference table—consider merging the workflow and action reference into a single comprehensive table.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably structured with tables and diagrams, but includes some redundancy (e.g., the action reference table largely repeats the workflow table, and the architecture diagram restates what the tables cover). The priority table and key principles are efficient, but overall could be tightened. | 2 / 3 |
Actionability | The skill provides a structured workflow with named actions and state schema, but the actual executable guidance is deferred to referenced files (problem-taxonomy.md, tuning-strategies.md, orchestrator.md, etc.). The SKILL.md itself contains no concrete implementation code or detection logic—just structural descriptions and bash invocation examples that are illustrative rather than executable. | 2 / 3 |
Workflow Clarity | The workflow table provides a clear 8-step sequence with orchestrator decisions, and the architecture diagram shows the flow. However, validation/verification is mentioned only as a single step ('action-verify') without explicit feedback loops or error recovery details in the main document—those are deferred to phases/orchestrator.md. For a skill involving potentially destructive fix operations, the lack of inline validation checkpoints caps this at 2. | 2 / 3 |
Progressive Disclosure | The skill excels at progressive disclosure: it provides a clear overview with well-organized tables and diagrams, then points to one-level-deep references (specs/, phases/, phases/actions/) with a clean reference table at the bottom. Navigation is clear and references are well-signaled with purpose descriptions. However, since no bundle files were provided, we cannot verify the referenced paths actually exist. | 3 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
Total | 10 / 11 Passed | |
- Repository
- catlog22/Claude-Code-Workflow
- Commit
5ff5e86
- 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.