CtrlK
BlogDocsLog inGet started
Tessl Logo

pseudocode-extractor

Extract programming-language-agnostic pseudocode from source code in any language, preserving control flow and logical structure while filtering out implementation details. Use when the user asks to convert code to pseudocode, abstract code logic, understand code structure without syntax, create language-independent documentation, or analyze algorithmic flow without language-specific details.

64

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/pseudocode-extractor/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%Weight 40%Scale 1-5

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

A well-structured, actionable skill body with clear sequencing and concrete examples. Its main weakness is verbosity from redundant sections (Common Patterns rehashes Format and Examples) that could be consolidated or moved to a reference file.

Suggestions

Consolidate the 'Common Patterns' section into the 'Format Pseudocode' conventions or the Examples, since it largely restates the same control-flow templates.

Trim the eight-item 'Best Practices' list to the few that are not already implied by the format conventions (e.g., Maintain Clarity, Be Consistent duplicate the conventions).

If the examples and pattern catalog grow further, split them into a references/ file and keep SKILL.md as an overview with one-level-deep links.

DimensionReasoningScore

Conciseness

The body is mostly efficient and well-organized, but the 'Common Patterns' section substantially duplicates the 'Format Pseudocode' conventions and the three full examples, and the eight Best Practices are partly self-evident, so it could be tightened.

3 / 5

Actionability

Provides a concrete pseudocode format spec and three complete input-to-output examples across Python, JavaScript, and Java, giving mostly executable guidance with only minor gaps.

4 / 5

Workflow Clarity

The 'Extraction Process' lays out four clearly sequenced steps (Analyze, Extract Core Logic, Format, Organize Output); no validation loops are present, but the task is non-destructive and non-batch so the workflow cap does not apply.

4 / 5

Progressive Disclosure

No bundle files exist, so content lives in a single SKILL.md with good section structure (Overview, Extraction Process, Examples, Best Practices, Common Patterns); minor redundancy between Common Patterns and Examples keeps it just short of ideal.

4 / 5

Total

15

/

20

Passed

Description

82%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, well-structured description that explicitly answers both what the skill does and when to use it, with natural trigger phrases and a distinct niche. The only minor gap is that specificity rests on a single primary action rather than a list of several distinct capabilities.

DimensionReasoningScore

Specificity

Names the domain and one concrete action ('Extract programming-language-agnostic pseudocode') with two qualifiers (preserving control flow, filtering implementation details), but does not list multiple distinct actions, matching the anchor for naming domain plus 1-2 actions.

3 / 5

Completeness

Clearly states what it does (extract pseudocode preserving control flow) and gives an explicit 'Use when...' clause with concrete trigger phrases, satisfying both what and when.

5 / 5

Trigger Term Quality

Includes several natural phrases users would say ('convert code to pseudocode', 'abstract code logic', 'understand code structure without syntax', 'algorithmic flow'); good coverage though a few synonyms are absent.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (language-agnostic pseudocode extraction) with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

17

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
ArabelaTso/Skills-4-SE
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.