agent-pseudocode
Agent skill for pseudocode - invoke with $agent-pseudocode
Install with Tessl CLI
npx tessl i github:ruvnet/claude-flow --skill agent-pseudocode55
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
22%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 severely underdeveloped, functioning more as a label than a useful description. It fails to explain what actions the skill performs with pseudocode and provides no guidance on when Claude should select it. The invocation syntax '$agent-pseudocode' is not useful for skill selection purposes.
Suggestions
Add specific actions the skill performs (e.g., 'Generates pseudocode from requirements, converts pseudocode to working code, reviews algorithm logic').
Add an explicit 'Use when...' clause with trigger scenarios (e.g., 'Use when the user asks for pseudocode, algorithm outlines, logic flows, or wants to plan code before implementation').
Include related trigger terms users might naturally say: 'algorithm', 'logic outline', 'code planning', 'step-by-step logic'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions - only states it's an 'agent skill for pseudocode' without explaining what it actually does (generate, convert, analyze, etc.). | 1 / 3 |
Completeness | Missing both 'what' (no actions described) and 'when' (no usage triggers). Only provides invocation syntax which doesn't help Claude decide when to select this skill. | 1 / 3 |
Trigger Term Quality | Contains 'pseudocode' which is a relevant keyword users might say, but lacks variations or related terms like 'algorithm', 'logic flow', 'code outline', or 'pseudo code'. | 2 / 3 |
Distinctiveness Conflict Risk | The term 'pseudocode' provides some specificity, but without knowing what the skill does with pseudocode, it could conflict with general coding or documentation skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides excellent concrete examples of pseudocode standards and patterns, making it highly actionable for algorithm design tasks. However, it's verbose with explanatory content Claude doesn't need, lacks validation checkpoints for the design workflow, and could benefit from splitting detailed examples into referenced files to improve token efficiency.
Suggestions
Add explicit validation steps for pseudocode review (e.g., 'Verify all edge cases are handled before proceeding')
Move detailed pattern examples (Strategy, Observer, etc.) to a separate PATTERNS.md file and reference it
Remove general best practices section - Claude already knows these principles
Add a feedback loop for complexity analysis verification before finalizing algorithms
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is moderately efficient but includes some unnecessary explanation (e.g., 'Good pseudocode is the blueprint for efficient implementation' and general best practices that Claude already knows). The extensive examples are valuable but could be more selective. | 2 / 3 |
Actionability | Provides fully concrete, executable pseudocode examples with clear syntax conventions, data structure definitions, and complexity analysis templates. The examples are copy-paste ready and demonstrate exact formatting expectations. | 3 / 3 |
Workflow Clarity | The SPARC phase steps are listed (1-5) but lack explicit validation checkpoints or feedback loops. There's no guidance on how to verify pseudocode quality before proceeding to implementation, which is important for this design phase. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but it's a monolithic document with no references to external files for detailed patterns or examples. The extensive inline examples could be split into separate reference files. | 2 / 3 |
Total | 9 / 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.