solve-challenge

Solves CTF challenges by performing first-pass triage, identifying the dominant category, and routing execution to the right specialized ctf-* skill. Use when the user gives you a challenge bundle, a remote service, a suspicious file, or only a vague challenge description and you must determine where to start. Do not use it when the category is already clear and a specialized skill can be invoked directly; this is the dispatcher and recon entrypoint, not the deepest reference for category-specific techniques.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

77%Weight 40%Scale 1-3

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

The body is highly actionable with a clear, well-sequenced workflow and validation checkpoints, but it carries some token-inefficient padding in the speculative multi-category pattern list and a duplicated quick-reference catalog. Progressive disclosure is adequate but monolithic given no bundle files exist.

Suggestions

Trim the 'Common multi-category patterns' list to 3–4 representative examples; the highly specific exotic patterns (GF(256) Nim, LWE→AES-GCM chains) read as padding Claude is unlikely to need.

Remove or condense the 'Quick Reference' section since its commands already appear in Step 1 Recon and the categorization workflow, avoiding duplication.

If the skill grows, move the flag-format catalog and recon command reference into a references/ file so SKILL.md stays a lean dispatcher overview.

Dimension	Reasoning	Score
Conciseness	Mostly efficient routing tables and commands, but the 'Common multi-category patterns' list drifts into exotic encyclopedic examples (e.g. 'GF(256) Nim', 'subspace recovery → LWE solving → AES-GCM decryption') and the Quick Reference duplicates commands already shown in the workflow, so it could be tightened.	2 / 3
Actionability	Provides fully executable commands throughout — `file *`, `strings`, `xxd \| head`, `binwalk`, `checksec`, `nc`, `curl`, grep flag patterns, and a copy-paste pwntools Python template — plus a concrete invoke table per category.	3 / 3
Workflow Clarity	Clearly sequenced Steps 0–5 with a feedback loop in Step 4 ('If your first approach doesn't work') and an explicit flag validation checkpoint ('validate before finalizing', corpus-wide uniqueness check) before reporting.	3 / 3
Progressive Disclosure	Well-organized into sections and appropriately delegates category techniques to sibling skills via a signaled table, but the skill is a monolithic single file with no bundle files of its own and inline reference material (Quick Reference, Flag Formats) that could live in a separate reference.	2 / 3
	Total	10 / 12 Passed

Description

100%Weight 40%Scale 1-3

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 specific, third-person, and explicitly pairs a what-clause with a when-clause plus a negative trigger, giving it a clear dispatcher niche distinct from the specialized ctf-* skills. It is concise without padding and uses natural trigger terms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'performing first-pass triage, identifying the dominant category, and routing execution to the right specialized ctf-* skill' — matching the anchor for several specific concrete actions.	3 / 3
Completeness	Explicitly answers what ('Solves CTF challenges by performing first-pass triage...') and when ('Use when the user gives you a challenge bundle...'), plus a negative trigger, satisfying both halves with explicit triggers.	3 / 3
Trigger Term Quality	Covers natural terms a user would say — 'challenge bundle, a remote service, a suspicious file, or only a vague challenge description' — alongside 'CTF challenges', giving good coverage of likely user phrasings.	3 / 3
Distinctiveness Conflict Risk	Clear niche as 'the dispatcher and recon entrypoint' with an explicit carve-out ('Do not use it when the category is already clear and a specialized skill can be invoked directly'), making conflict with sibling ctf-* skills unlikely.	3 / 3
	Total	12 / 12 Passed

Validation

81%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
relative_links	Relative link issues: 1 suspicious	Warning
referenced_paths_exist	Referenced path issues: 8 missing	Warning

	Total	13 / 16 Passed

Repository: ljagiello/ctf-skills
Path: solve-challenge/SKILL.md
Commit: d19f35f

Reviewed: 9 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.