agent-pseudocode

Agent skill for pseudocode - invoke with $agent-pseudocode

1.61x

Quality

43%

Does it follow best practices?

Impact

84%

1.61x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/agent-pseudocode/SKILL.md

Quality

Content

65%

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

The body is a thorough, well-structured pseudocode reference with concrete templates and a clear deliverables list, but it is verbose and monolithic — explaining patterns Claude already knows and keeping all content inline rather than splitting detailed references into separate files. Adding a lightweight validation step and trimming generic material would meaningfully improve it.

Suggestions

Trim the 'Design Patterns in Pseudocode' and 'Pseudocode Best Practices' sections, which restate concepts Claude already knows; keep only skill-specific standards.

Move the worked complexity-analysis and design-pattern examples into a reference file and link to it from the body to reduce the main file's token load.

Add a short verification checkpoint to the phase workflow (e.g. 'Confirm each algorithm has stated inputs/outputs and complexity before finalizing deliverables').

Dimension	Reasoning	Score
Conciseness	The pseudocode templates are on-topic, but ~320 lines include generic best practices ('Language Agnostic', 'Clear Logic') and Strategy/Observer pattern explanations Claude already knows, plus an out-of-place hooks YAML block — efficient in places but could be tightened.	2 / 3
Actionability	It provides concrete, copy-paste-ready pseudocode templates with explicit INPUT/OUTPUT/BEGIN/END structure, data-structure specs, and a complexity-analysis format; for an instruction-only design skill the guidance is specific and actionable.	3 / 3
Workflow Clarity	The five Pseudocode-phase steps and Deliverables are listed in sequence, but there are no validation checkpoints or feedback loops tying spec-input to output verification, so the sequence is present but checkpoints are implicit.	2 / 3
Progressive Disclosure	Sections are well-organized with clear headers, but the document is a monolithic 320-line file with no external references; the design-pattern and complexity-analysis content that could live in separate files is all inline.	2 / 3
	Total	9 / 12 Passed

Description

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.

The description is too vague to be effective: it states only that this is a pseudocode skill and how to invoke it, without naming concrete actions or giving any 'Use when...' trigger guidance. It risks poor activation because users and Claude get little signal about when to select it.

Suggestions

Add concrete actions, e.g. 'Designs algorithms, selects data structures, and analyzes complexity for the SPARC pseudocode phase.'

Include an explicit 'Use when...' trigger clause naming natural phrases like 'write pseudocode', 'design an algorithm', or 'analyze time/space complexity'.

Drop the invocation syntax from the description or move it to the body; reserve the description for what the skill does and when to use it.

Dimension	Reasoning	Score
Specificity	The phrase 'Agent skill for pseudocode' names a domain but lists no concrete actions (e.g. designing algorithms, selecting data structures), matching the vague/abstract anchor rather than the 'some actions' anchor at 2.	1 / 3
Completeness	The 'what' is only weakly implied ('skill for pseudocode') and the 'when' is entirely absent with no 'Use when...' trigger guidance, so it fails the explicit-trigger requirement and matches 'both very weak'.	1 / 3
Trigger Term Quality	'pseudocode' is a natural term a user would say, but coverage is thin — it omits common variations like 'algorithm design', 'write pseudocode', or 'logic flow', landing on 'some relevant keywords but missing common variations'.	2 / 3
Distinctiveness Conflict Risk	'pseudocode' is a recognizable niche and '$agent-pseudocode' gives a distinct invocation, but with no clear trigger phrases it could still overlap with general coding or algorithm-design skills.	2 / 3
	Total	6 / 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: ruvnet/claude-flow
Path: .agents/skills/agent-pseudocode/SKILL.md
Commit: 26c35b5

Reviewed: about 7 hours 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.