[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CG8G330M2FMS1BZSMPVSWG":3,"skill-same:01M7CG8G330M2FMS1BZSMPVSWG":51},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":29,"commitSha":30,"skillDirectory":31,"forksCount":32,"repositoryHtmlUrl":33,"repositoryHomepageUrl":6,"ownerHtmlUrl":34,"ownerBlogUrl":6,"ownerDescription":35,"updatedAt":36,"install":37,"resources":50},"01M7CG8G330M2FMS1BZSMPVSWG","ctf-writeup",null,"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.","om-scogo\u002Fskillsh-scraper","om-scogo","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160466840?v=4","01M79AWB6DFVCQ7RK70CS34B96","Om Achrekar","01M79AWB6ZM9SKR8KDH1WSSM22",0,"MIT","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fljagiello-ctf-skills\u002Fctf-writeup\u002Fctf-writeup\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: ctf-writeup\ndescription: 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.\nlicense: MIT\ncompatibility: Requires filesystem-based agent (Claude Code or similar) with bash and Python 3.\nallowed-tools: Bash Read Write Edit Glob Grep Task WebFetch WebSearch\nmetadata:\n  user-invocable: \"true\"\n  argument-hint: \"[challenge-name]\"\n---\n\n# CTF Write-up Generator\n\nGenerate a standardized submission-style CTF writeup for a solved challenge.\n\nDefault behavior:\n\n- During an active competition, optimize for speed, clarity, and reproducibility\n- Keep writeups short enough that a teammate or organizer can validate the solve quickly\n- Always produce a `submission`-style writeup\n- Prefer one complete solve script from challenge data to final flag\n\n## Workflow\n\n### Step 1: Gather Information\n\nCollect the following from the current session, challenge files, and user input:\n\n1. **Challenge metadata** — name, CTF event, category, difficulty, points, flag format\n2. **Solution artifacts** — exploit scripts, payloads, screenshots, command output\n3. **Timeline** — key steps taken, dead ends, pivots\n\n```bash\n# Scan for exploit scripts and artifacts\nfind . -name '*.py' -o -name '*.sh' -o -name 'exploit*' -o -name 'solve*' | head -20\n# Check for flags in output files\ngrep -rniE '(flag|ctf|eno|htb|pico)\\{' . 2>\u002Fdev\u002Fnull\n```\n\n### Step 2: Generate Write-up\n\nWrite the writeup file as `writeup.md` (or `writeup-\u003Cchallenge-name>.md`) using the submission template below.\n\n---\n\n## Templates\n\n### Submission Format\n\n```markdown\n---\ntitle: \"\u003CChallenge Name>\"\nctf: \"\u003CCTF Event Name>\"\ndate: YYYY-MM-DD\ncategory: web|pwn|crypto|reverse|forensics|osint|malware|misc\ndifficulty: easy|medium|hard\npoints: \u003Cnumber>\nflag_format: \"flag{...}\"\nauthor: \"\u003Cyour name or team>\"\n---\n\n# \u003CChallenge Name>\n\n## Summary\n\n\u003C1-2 sentences: what the challenge was and the core technique. Keep it direct.>\n\n## Solution\n\n### Step 1: \u003CAction>\n\n\u003CExplain the key observation in 3-8 short lines. Keep it direct.>\n\n\\`\\`\\`python\n\u003Cone complete solving script from provided challenge data to printing the final flag>\n\\`\\`\\`\n\n### Step 2: \u003CAction> (optional)\n\n\u003COnly add this when a second short step genuinely helps readability, such as separating the core observation from final verification.>\n\n### Step 3: \u003CAction> (optional)\n\n\u003CUse only if the challenge really needs it. Keep the total number of steps small.>\n\n## Flag\n\n\\`\\`\\`\nflag{example_flag_here}\n\\`\\`\\`\n```\n\nGuidance:\n\n- Prefer 1-3 short steps total\n- Keep code to the smallest complete solving script\n- Do not split \"recover secret\", \"derive key\", and \"decrypt flag\" into separate partial snippets\n- The script should start from the challenge data and end by printing the flag\n- Avoid long background sections\n- Avoid dead ends unless they explain a key pivot\n- Avoid multiple alternative solves; pick one clean path\n- Redact the flag only if the user explicitly asks for redaction\n\n---\n\n## Best Practices Checklist\n\nBefore finalizing the writeup, verify:\n\n- [ ] **Metadata complete** — title, CTF, date, category, difficulty, points, author all filled\n- [ ] **Flag handling matches request** — keep the real flag unless the user asked for redaction\n- [ ] **Reproducible steps** — a reader can follow your writeup and reproduce the solution\n- [ ] **Code is runnable** — exploit scripts include all imports, correct variable names, and comments\n- [ ] **No sensitive data** — no real credentials, API keys, or private infrastructure details\n- [ ] **Length stays concise** — the writeup is short enough for fast review\n- [ ] **Tools and versions noted** — mention specific tool versions if behavior depends on them\n- [ ] **Proper attribution** — credit teammates, referenced writeups, or tools that were essential\n- [ ] **Grammar and formatting** — consistent heading levels, code blocks have language tags\n\n## Quality Guidelines\n\n**DO:**\n- Explain just enough for fast verification\n- Include one complete solving path, not multiple alternative routes\n- Include one complete script that goes all the way to the final flag\n- Show actual output (truncated if very long) to prove the approach worked\n- Tag code blocks with language (`python`, `bash`, `sql`, etc.)\n- Keep the main path front-loaded so a reader can validate it quickly\n\n**DON'T:**\n- Copy-paste raw terminal dumps without explanation\n- Paste several partial snippets that force the reader to reconstruct the final solve\n- Leave placeholder text in the final writeup\n- Include irrelevant tangents that don't contribute to the solution\n- Assume the reader knows the specific challenge setup\n\n## Challenge\n\n$ARGUMENTS\n","# CTF Write-up Generator\n\nGenerate a standardized submission-style CTF writeup for a solved challenge.\n\nDefault behavior:\n\n- During an active competition, optimize for speed, clarity, and reproducibility\n- Keep writeups short enough that a teammate or organizer can validate the solve quickly\n- Always produce a `submission`-style writeup\n- Prefer one complete solve script from challenge data to final flag\n\n## Workflow\n\n### Step 1: Gather Information\n\nCollect the following from the current session, challenge files, and user input:\n\n1. **Challenge metadata** — name, CTF event, category, difficulty, points, flag format\n2. **Solution artifacts** — exploit scripts, payloads, screenshots, command output\n3. **Timeline** — key steps taken, dead ends, pivots\n\n```bash\n# Scan for exploit scripts and artifacts\nfind . -name '*.py' -o -name '*.sh' -o -name 'exploit*' -o -name 'solve*' | head -20\n# Check for flags in output files\ngrep -rniE '(flag|ctf|eno|htb|pico)\\{' . 2>\u002Fdev\u002Fnull\n```\n\n### Step 2: Generate Write-up\n\nWrite the writeup file as `writeup.md` (or `writeup-\u003Cchallenge-name>.md`) using the submission template below.\n\n---\n\n## Templates\n\n### Submission Format\n\n```markdown\n---\ntitle: \"\u003CChallenge Name>\"\nctf: \"\u003CCTF Event Name>\"\ndate: YYYY-MM-DD\ncategory: web|pwn|crypto|reverse|forensics|osint|malware|misc\ndifficulty: easy|medium|hard\npoints: \u003Cnumber>\nflag_format: \"flag{...}\"\nauthor: \"\u003Cyour name or team>\"\n---\n\n# \u003CChallenge Name>\n\n## Summary\n\n\u003C1-2 sentences: what the challenge was and the core technique. Keep it direct.>\n\n## Solution\n\n### Step 1: \u003CAction>\n\n\u003CExplain the key observation in 3-8 short lines. Keep it direct.>\n\n\\`\\`\\`python\n\u003Cone complete solving script from provided challenge data to printing the final flag>\n\\`\\`\\`\n\n### Step 2: \u003CAction> (optional)\n\n\u003COnly add this when a second short step genuinely helps readability, such as separating the core observation from final verification.>\n\n### Step 3: \u003CAction> (optional)\n\n\u003CUse only if the challenge really needs it. Keep the total number of steps small.>\n\n## Flag\n\n\\`\\`\\`\nflag{example_flag_here}\n\\`\\`\\`\n```\n\nGuidance:\n\n- Prefer 1-3 short steps total\n- Keep code to the smallest complete solving script\n- Do not split \"recover secret\", \"derive key\", and \"decrypt flag\" into separate partial snippets\n- The script should start from the challenge data and end by printing the flag\n- Avoid long background sections\n- Avoid dead ends unless they explain a key pivot\n- Avoid multiple alternative solves; pick one clean path\n- Redact the flag only if the user explicitly asks for redaction\n\n---\n\n## Best Practices Checklist\n\nBefore finalizing the writeup, verify:\n\n- [ ] **Metadata complete** — title, CTF, date, category, difficulty, points, author all filled\n- [ ] **Flag handling matches request** — keep the real flag unless the user asked for redaction\n- [ ] **Reproducible steps** — a reader can follow your writeup and reproduce the solution\n- [ ] **Code is runnable** — exploit scripts include all imports, correct variable names, and comments\n- [ ] **No sensitive data** — no real credentials, API keys, or private infrastructure details\n- [ ] **Length stays concise** — the writeup is short enough for fast review\n- [ ] **Tools and versions noted** — mention specific tool versions if behavior depends on them\n- [ ] **Proper attribution** — credit teammates, referenced writeups, or tools that were essential\n- [ ] **Grammar and formatting** — consistent heading levels, code blocks have language tags\n\n## Quality Guidelines\n\n**DO:**\n- Explain just enough for fast verification\n- Include one complete solving path, not multiple alternative routes\n- Include one complete script that goes all the way to the final flag\n- Show actual output (truncated if very long) to prove the approach worked\n- Tag code blocks with language (`python`, `bash`, `sql`, etc.)\n- Keep the main path front-loaded so a reader can validate it quickly\n\n**DON'T:**\n- Copy-paste raw terminal dumps without explanation\n- Paste several partial snippets that force the reader to reconstruct the final solve\n- Leave placeholder text in the final writeup\n- Include irrelevant tangents that don't contribute to the solution\n- Assume the reader knows the specific challenge setup\n\n## Challenge\n\n$ARGUMENTS\n",{"name":5,"license":15,"metadata":24,"description":7,"allowed-tools":27,"compatibility":28},{"argument-hint":25,"user-invocable":26},"[challenge-name]","true","Bash Read Write Edit Glob Grep Task WebFetch WebSearch","Requires filesystem-based agent (Claude Code or similar) with bash and Python 3.","main","8859218955d9504cd18b59e7892100718039d3b4","data\u002Fskills\u002Fljagiello-ctf-skills\u002Fctf-writeup\u002Fctf-writeup",1,"https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper","https:\u002F\u002Fgithub.com\u002Fom-scogo","SDE-1 @ Scogo ","2026-07-18 12:22:46",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add om-scogo\u002Fskillsh-scraper --skill ctf-writeup",{"tool":43,"command":44},"bunx","bunx skills add om-scogo\u002Fskillsh-scraper --skill ctf-writeup",{"tool":46,"command":47},"pnpm","pnpm dlx skills add om-scogo\u002Fskillsh-scraper --skill ctf-writeup","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fljagiello-ctf-skills\u002Fctf-writeup\u002Fctf-writeup\u002FSKILL.md",true,[],[52,59,64,71,76,83],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7D6MC9FAAEV4CMNYX8W7JTG","arxiv-search","Search arXiv physics, math, and computer science preprints using natural language queries. Powered by Valyu semantic search.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\u002Fskills\u002Farxiv-search\u002FSKILL.md",[],[],{"skillNo":60,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M7D6M85CKKN87TA98VCQV4H7","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\u002FSkill.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7D4ZTCS4DR3CE4JY06X84T2","working-with-legacy-code","Safely change and test untested codebases using Feathers' \"Working Effectively with Legacy Code\". Use when the user mentions \"legacy code\", \"no tests\", \"untested codebase\", \"how do I test this\", \"seams\", \"characterization tests\", \"golden master\", \"sprout method\", \"afraid to change this code\", \"monster method\", \"dependency breaking\", or \"inherited a messy codebase\". Also trigger when changing code without tests safely, getting a class under test when constructors, statics, or singletons block it, adding features to tangled modules, or planning incremental test coverage for an old codebase. Covers the legacy-code change algorithm, seams, characterization tests, sprout\u002Fwrap, and dependency-breaking techniques. For refactoring code that already has tests, see refactoring-patterns. For day-to-day code quality, see clean-code.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\u002Fworking-with-legacy-code\u002FSKILL.md",[],[],{"skillNo":72,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7D4ZHZKJD2RSNGAF63V14P4","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\u002FSkill.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7D4ZB4CJBFW5JE67CPH2QRV","web-typography","Select, pair, and implement typefaces for web projects. Use when the user mentions \"font pairing\", \"which typeface\", \"line height\", \"responsive typography\", \"web font loading\", \"type hierarchy\", \"variable fonts\", \"FOUT\u002FFOIT\", \"typographic scale\", or \"the text is hard to read\". Also trigger when choosing between system fonts and web fonts, optimizing font-loading performance, or designing readable long-form content. Covers readability evaluation, CSS implementation, and performance optimization. For overall UI design systems, see refactoring-ui. For dramatic typographic experiences, see top-design.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002Fweb-typography\u002FSKILL.md",[],[],{"skillNo":84,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7D4Z4MVYVY3NMJ18BNV6WNA","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002FSkill.md",[],[]]