agent-refinement
Agent skill for refinement - invoke with $agent-refinement
43
13%
Does it follow best practices?
Impact
96%
1.23xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agents/skills/agent-refinement/SKILL.mdQuality
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 is critically deficient across all dimensions. It provides no information about what the skill does, when it should be used, or what domain it operates in. The word 'refinement' is too vague to serve as either a capability description or a trigger term.
Suggestions
Specify what is being refined (e.g., code, text, prompts, designs) and list 2-3 concrete actions the skill performs (e.g., 'Iteratively improves code quality by analyzing structure, reducing complexity, and applying best practices').
Add an explicit 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when the user asks to improve, polish, iterate on, or refine their code/text').
Replace the invocation instruction ('invoke with $agent-refinement') with a domain-specific description that distinguishes this skill from other editing or improvement skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Refinement' is abstract and undefined — it does not specify what is being refined, how, or what outputs are produced. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is answered. There is no explanation of capabilities and no 'Use when...' clause or equivalent trigger guidance. | 1 / 3 |
Trigger Term Quality | The only potentially relevant keyword is 'refinement,' which is vague and not a natural term users would use. The invocation command '$agent-refinement' is a technical artifact, not a user-facing trigger term. | 1 / 3 |
Distinctiveness Conflict Risk | 'Refinement' is extremely generic and could apply to code refinement, text refinement, image refinement, prompt refinement, or any iterative improvement task. This would conflict with virtually any editing or improvement skill. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
27%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads like a general software engineering tutorial on TDD, refactoring, and error handling rather than an actionable agent skill. It is extremely verbose, explaining patterns and concepts Claude already knows well (TDD cycles, circuit breakers, error hierarchies, cyclomatic complexity). The content would benefit enormously from being condensed to a concise workflow with project-specific guidance and splitting detailed examples into referenced files.
Suggestions
Reduce content by 80%+ by removing explanations of concepts Claude already knows (TDD, circuit breakers, error hierarchies, complexity) and focus on project-specific refinement steps and decision criteria.
Add a clear, concise workflow with explicit validation checkpoints: e.g., 1. Run existing tests → 2. Identify improvement targets → 3. Apply refinement → 4. Validate tests pass → 5. Measure improvement.
Split detailed code examples (error handling patterns, circuit breakers, performance optimization) into separate reference files and link to them from a concise overview.
Add concrete decision criteria for when to apply each refinement technique rather than just showing generic examples of each pattern.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~400+ lines. Explains basic concepts Claude already knows (TDD red/green/refactor, what circuit breakers are, what error hierarchies are, cyclomatic complexity). The lengthy code examples are illustrative rather than project-specific, essentially teaching general software engineering patterns that Claude already understands. | 1 / 3 |
Actionability | Contains concrete, executable TypeScript code examples which is good, but they are generic teaching examples rather than actionable instructions for a specific refinement workflow. There's no guidance on how to apply these patterns to an actual codebase - it reads more like a textbook chapter than an operational skill. | 2 / 3 |
Workflow Clarity | The TDD Red/Green/Refactor phases are sequenced, but there are no explicit validation checkpoints or feedback loops for the overall refinement process. The skill doesn't define when refinement is 'done,' how to prioritize which refinements to make, or how to verify improvements. The numbered sections provide structure but lack operational decision points. | 2 / 3 |
Progressive Disclosure | Monolithic wall of text with all content inline. No references to external files for detailed patterns. The error handling, performance optimization, circuit breaker, and quality metrics sections could each be separate reference files, with the main skill providing a concise overview and navigation. | 1 / 3 |
Total | 6 / 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 |
|---|---|---|
skill_md_line_count | SKILL.md is long (530 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
- Repository
- ruvnet/ruflo
- Commit
ccb062f
- 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.