agent-pseudocode

Agent skill for pseudocode - invoke with $agent-pseudocode

1.61x

Quality

Does it follow best practices?

Impact

84%

1.61x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agents/skills/agent-pseudocode/SKILL.md

Quality

Discovery

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 an extremely weak description that provides almost no useful information for skill selection. It merely names the domain ('pseudocode') without describing any concrete capabilities, use cases, or trigger conditions. It reads more like a label than a functional description.

Suggestions

Add specific concrete actions the skill performs, e.g., 'Generates pseudocode from natural language descriptions, converts code to pseudocode, and refines algorithm logic in pseudocode format.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to write pseudocode, outline an algorithm, draft logic steps, or convert code to pseudocode.'

Remove the invocation syntax ('invoke with $agent-pseudocode') from the description as it wastes space and doesn't help Claude decide when to select this skill.

Dimension	Reasoning	Score
Specificity	The description provides no concrete actions whatsoever. 'Agent skill for pseudocode' is extremely vague and does not describe what the skill actually does (e.g., generate, convert, analyze pseudocode).	1 / 3
Completeness	The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no 'Use when...' clause and no meaningful explanation of capabilities.	1 / 3
Trigger Term Quality	The only keyword is 'pseudocode', which is relevant but insufficient. The description lacks natural variations users might say (e.g., 'algorithm design', 'pseudo code', 'logic outline'). The invocation syntax '$agent-pseudocode' is not a natural user trigger term.	1 / 3
Distinctiveness Conflict Risk	While 'pseudocode' is a somewhat specific domain, the description is so vague that it's unclear what this skill does versus any other coding or algorithm-related skill. It could easily conflict with general coding assistance skills.	1 / 3
	Total	4 / 12 Passed

Implementation

14%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill is excessively verbose, spending most of its token budget on generic pseudocode examples and design pattern explanations that Claude already knows. It lacks a clear actionable workflow for the SPARC Pseudocode phase and provides no validation checkpoints or progressive disclosure. The content reads more like a textbook chapter on pseudocode than an operational skill for an AI agent.

Suggestions

Reduce content to ~30-50 lines: a concise pseudocode format template, the expected deliverables, and a clear step-by-step workflow for the SPARC Pseudocode phase with validation checkpoints.

Remove generic design pattern explanations (Strategy, Observer) and best practices ('use meaningful names') that Claude already knows — focus only on project-specific conventions or non-obvious requirements.

Add a clear sequential workflow with explicit validation steps, e.g., 'After writing pseudocode, verify all edge cases are handled, then analyze complexity, then confirm alignment with specification before marking phase complete.'

Move lengthy examples to a separate reference file (e.g., PSEUDOCODE_EXAMPLES.md) and link to it from the main skill, keeping only one brief example inline.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~200+ lines. Most content is generic pseudocode examples and design pattern explanations that Claude already knows well. The SPARC methodology explanation, design patterns (Strategy, Observer), and best practices like 'use meaningful names' add no value for Claude. The entire skill could be reduced to a concise template and format specification.	1 / 3
Actionability	The examples are concrete and well-structured pseudocode, but they are illustrative rather than executable. The skill describes what pseudocode should look like with examples but doesn't give Claude clear instructions on how to apply this to an actual user request — it's more of a reference document than an actionable workflow.	2 / 3
Workflow Clarity	The five SPARC Pseudocode phase steps (designing solutions, selecting data structures, analyzing complexity, identifying patterns, creating roadmap) are listed but not sequenced into a clear workflow with validation checkpoints. There's no guidance on when to proceed between steps, how to validate outputs, or how to handle issues. The deliverables section is a checklist but lacks process flow.	1 / 3
Progressive Disclosure	The content is a monolithic wall of text with no references to external files. All examples — authentication, rate limiting, search, design patterns — are inlined despite being lengthy. The content would benefit greatly from splitting examples into separate reference files and keeping the SKILL.md as a concise overview.	1 / 3
	Total	5 / 12 Passed

Validation

100%

Warnings & errors only

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.

Repository: ruvnet/ruflo
Commit: 398f7c2

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.