ctf-writeup

Generates a single standardized submission-style CTF writeup for competition handoff and organizer review. Use after solving a CTF challenge to document the solution steps, tools used, and lessons learned in a structured format.

Quality

77%

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

Fix and improve this skill with Tessl

tessl review fix ./ctf-writeup/SKILL.md

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.

The body is well-structured and actionable, with a concrete submission template, executable discovery commands, and a final verification checklist. Its main weakness is redundant guidance repeated across three sections, which lightly hurts token efficiency.

Suggestions

Consolidate the overlapping guidance in the template "Guidance", "Best Practices Checklist", and "Quality Guidelines" DO/DON'T into a single checklist to remove repetition and improve conciseness.

Add an explicit validation sub-step in Step 1 (e.g. confirm flag format and required metadata are present before writing the file) to strengthen the workflow's feedback loop.

Tighten the "Default behavior" bullets so they do not restate constraints already enforced by the template guidance.

Dimension	Reasoning	Score
Conciseness	The body avoids explaining concepts Claude already knows (no "what is a CTF" preamble) and stays actionable, but the same guidance is restated across three sections — template "Guidance", "Best Practices Checklist", and "Quality Guidelines" DO/DON'T — adding repetition that could be tightened, fitting the score-3 anchor.	3 / 5
Actionability	Provides a copy-paste-ready submission template with concrete frontmatter fields and executable bash (`find ... \| head -20`, `grep -rniE '(flag\|ctf\|...)\{'`); only the inline solve-script slot remains a placeholder by design, matching the score-4 anchor.	4 / 5
Workflow Clarity	A clear two-step sequence (Gather Information → Generate Write-up) is followed by a "Before finalizing the writeup, verify" checklist acting as a validation checkpoint; this is not a destructive/batch operation so the score-3 cap does not apply, but the gather step lacks an explicit validation sub-check, fitting score 4 over 5.	4 / 5
Progressive Disclosure	No bundle files exist (references/scripts/assets absent) and the single file is well-organized with clear section headers (Workflow, Templates, Best Practices Checklist, Quality Guidelines); content is appropriately placed with only minor redundancy, matching the score-4 anchor.	4 / 5
	Total	15 / 20 Passed

Description

87%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.

The description is third-person, concise, and clearly states both what the skill does and when to use it, with concrete trigger phrases tied to CTF competition handoff. Minor specificity and synonym coverage gaps keep it just short of a perfect specificity/trigger score.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions — "Generates a single standardized submission-style CTF writeup", "document the solution steps, tools used, and lessons learned in a structured format" — with only minor coverage gaps, fitting the score-4 anchor better than the fully comprehensive score-5 anchor.	4 / 5
Completeness	Explicitly answers both what ("Generates a single standardized submission-style CTF writeup for competition handoff and organizer review") and when ("Use after solving a CTF challenge to document...") with concrete trigger phrases, matching the score-5 anchor.	5 / 5
Trigger Term Quality	Good natural keyword coverage ("CTF writeup", "CTF challenge", "competition handoff", "organizer review") that users would plausibly say, but a few common synonyms/extensions (e.g. "flag", specific category terms) are missing, matching the score-4 anchor.	4 / 5
Distinctiveness Conflict Risk	"CTF writeup" / "submission-style CTF writeup for competition handoff and organizer review" carves a clear niche with distinct triggers and minimal overlap risk with other skills, matching the score-5 anchor.	5 / 5
	Total	18 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: ljagiello/ctf-skills
Path: ctf-writeup/SKILL.md
Commit: c332c7b

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