pseudocode-extractor
Extracts language-agnostic pseudocode from real code, stripping syntax noise and language-specific machinery while preserving the algorithmic structure. Use when documenting an algorithm for a paper or spec, when porting and wanting a neutral intermediate, or when explaining code to someone who doesn't know the source language.
Install with Tessl CLI
npx tessl i github:santosomar/general-secure-coding-agent-skills --skill pseudocode-extractor94
Quality
92%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Discovery
85%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 skill description that clearly articulates what the skill does and when to use it. The explicit 'Use when...' clause with three distinct scenarios provides excellent guidance for skill selection. The main weakness is that trigger terms could include more natural variations of how users might request this functionality.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists specific concrete actions: 'Extracts language-agnostic pseudocode', 'stripping syntax noise and language-specific machinery', 'preserving the algorithmic structure'. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what (extracts pseudocode, strips syntax noise, preserves algorithmic structure) AND when with explicit triggers ('Use when documenting an algorithm for a paper or spec, when porting and wanting a neutral intermediate, or when explaining code'). | 3 / 3 |
Trigger Term Quality | Includes some natural terms like 'pseudocode', 'algorithm', 'porting', 'explaining code', but misses common variations users might say like 'convert to pseudocode', 'simplify code', 'algorithm extraction', or 'code abstraction'. | 2 / 3 |
Distinctiveness Conflict Risk | Has a clear niche focused specifically on pseudocode extraction with distinct use cases (documentation, porting, explanation). Unlikely to conflict with general code analysis or documentation skills due to the specific 'language-agnostic pseudocode' focus. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill that demonstrates mastery of the format. It's concise yet comprehensive, with actionable tables, a realistic worked example showing before/after transformation, and clear guardrails in the 'Do not' section. The content respects Claude's intelligence while providing the specific domain knowledge needed for pseudocode extraction.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, assuming Claude's competence. No unnecessary explanations of what pseudocode is or why it's useful—jumps straight into actionable guidance with well-structured tables and examples. | 3 / 3 |
Actionability | Provides concrete, executable guidance through detailed tables mapping source elements to pseudocode, a complete worked example with real Python code and its transformation, and specific idiom translations. The output format template is copy-paste ready. | 3 / 3 |
Workflow Clarity | For this type of skill (transformation/extraction), the workflow is implicit but clear: identify abstraction level, apply keep/strip rules, translate idioms, document what was changed. The 'Do not' section provides validation guardrails, and the output format enforces a structured process. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections (Keep vs. strip, Abstraction levels, Worked example, Common idioms, Do not, Output format). The comparison to `verified-pseudocode-extractor` at the top provides appropriate cross-referencing. No unnecessary nesting or monolithic walls of text. | 3 / 3 |
Total | 12 / 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.