[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CG8KZC59WM0NKCK6GSHF22":3,"skill-same:01M7CG8KZC59WM0NKCK6GSHF22":57},{"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},"01M7CG8KZC59WM0NKCK6GSHF22","solve-challenge",null,"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.","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\u002Fsolve-challenge\u002FSkill.md",[],[],"2026-11-15 14:19:17",false,"---\nname: solve-challenge\ndescription: 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.\nlicense: MIT\ncompatibility: Requires filesystem-based agent (Claude Code or similar) with bash, Python 3, and internet access. Orchestrates other ctf-* skills.\nallowed-tools: Bash Read Write Edit Glob Grep Task WebFetch WebSearch Skill\nmetadata:\n  user-invocable: \"true\"\n  argument-hint: \"[category] [challenge-file-or-url]\"\n---\n\n# CTF Challenge Solver\n\nYou're a skilled CTF player. Your goal is to solve the challenge and find the flag.\n\n## Environment Setup\n\nTwo setup strategies depending on your workflow:\n\n### Pre-install (recommended before competitions)\n\nUse the central installer entrypoint:\n\n```bash\nbash scripts\u002Finstall_ctf_tools.sh all\n```\n\nRun a narrower mode when you only want one tool group:\n\n```bash\nbash scripts\u002Finstall_ctf_tools.sh python\nbash scripts\u002Finstall_ctf_tools.sh apt\nbash scripts\u002Finstall_ctf_tools.sh brew\nbash scripts\u002Finstall_ctf_tools.sh gems\nbash scripts\u002Finstall_ctf_tools.sh go\nbash scripts\u002Finstall_ctf_tools.sh manual\n```\n\nThe full package lists now live in [scripts\u002Finstall_ctf_tools.sh](..\u002Fscripts\u002Finstall_ctf_tools.sh).\n\n### On-demand (during challenges)\n\nEach category skill's `SKILL.md` has a **Prerequisites** section listing only the tools needed for that category. Install as you go.\n\n## Workflow\n\n### Step 0: CTFd Platform Detection\n\nIf the CTF platform URL is known, check if it runs CTFd and switch to API-driven navigation:\n\n```bash\n# Detect CTFd (look for \u002Fapi\u002Fv1\u002F and \u002Fthemes\u002Fcore\u002F)\ncurl -s \"$CTF_URL\u002Fapi\u002Fv1\u002F\" | head -5\ncurl -s \"$CTF_URL\" | grep -oE '\u002Fthemes\u002Fcore\u002F'\n```\n\nIf CTFd is detected, **ask the user for their API token** (generated from CTFd Settings > Access Tokens). The token is not provided by default — the user must create one in the CTFd web UI first. Once provided, set the environment variables and proceed via API:\n\n```bash\nexport CTF_URL=\"https:\u002F\u002Fctf.example.com\"\nexport CTF_TOKEN=\"ctfd_...\"  # Ask user for this\n```\n\nInvoke `\u002Fctf-misc` and load its `ctfd-navigation.md` for the full API reference and Python client class.\n\n### Step 1: Recon\n\n1. **Explore files** -- List the challenge directory, run `file *` on everything\n2. **Triage binaries** -- `strings`, `xxd | head`, `binwalk`, `checksec` on binaries\n3. **Fetch links** -- If the challenge mentions URLs, fetch them FIRST for context\n4. **Connect** -- Try remote services (`nc`) to understand what they expect\n5. **Read hints** -- Challenge descriptions, filenames, and comments often contain clues\n\n### Step 2: Categorize\n\nDetermine the primary category, then invoke the matching skill.\n\n**By file type:**\n- `.pcap`, `.pcapng`, `.evtx`, `.raw`, `.dd`, `.E01` -> forensics\n- `.elf`, `.exe`, `.so`, `.dll`, binary with no extension -> reverse or pwn (check if remote service provided -- if yes, likely pwn)\n- `.py`, `.sage`, `.txt` with numbers -> crypto\n- `.apk`, `.wasm`, `.pyc` -> reverse\n- Web URL or source code with HTML\u002FJS\u002FPHP\u002Ftemplates -> web\n- Images, audio, PDFs with no obvious content -> forensics (steganography)\n\n**By challenge description keywords:**\n- \"buffer overflow\", \"ROP\", \"shellcode\", \"libc\", \"heap\" -> pwn\n- \"RSA\", \"AES\", \"cipher\", \"encrypt\", \"prime\", \"modulus\", \"lattice\", \"LWE\", \"GCM\" -> crypto\n- \"XSS\", \"SQL\", \"injection\", \"cookie\", \"JWT\", \"SSRF\" -> web\n- \"disk image\", \"memory dump\", \"packet capture\", \"registry\", \"power trace\", \"side-channel\", \"spectrogram\", \"audio tracks\", \"MKV\" -> forensics\n- \"find\", \"locate\", \"identify\", \"who\", \"where\" -> osint\n- \"obfuscated\", \"packed\", \"C2\", \"malware\", \"beacon\" -> malware\n- \"jail\", \"sandbox\", \"escape\", \"encoding\", \"signal\", \"game\", \"Nim\", \"commitment\", \"Gray code\" -> misc\n\n**By service behavior:**\n- Port with interactive prompt, crash on long input -> pwn\n- HTTP service -> web\n- netcat with math\u002Fcrypto puzzles -> crypto\n- netcat with restricted shell or eval -> misc (jail)\n\n### Step 3: Invoke the Category Skill\n\nOnce you identify the category, **invoke the matching skill** to get specialized techniques:\n\n| Category | Invoke | When to Use |\n|----------|--------|-------------|\n| Web | `\u002Fctf-web` | XSS, SQLi, SSTI, SSRF, JWT, file uploads, prototype pollution |\n| Pwn | `\u002Fctf-pwn` | Buffer overflow, format string, heap, ROP, sandbox escape |\n| Crypto | `\u002Fctf-crypto` | RSA, AES, ECC, PRNG, ZKP, classical ciphers |\n| Reverse | `\u002Fctf-reverse` | Binary analysis, game clients, VMs, obfuscated code |\n| Forensics | `\u002Fctf-forensics` | Disk images, memory dumps, event logs, stego, network captures |\n| OSINT | `\u002Fctf-osint` | Social media, geolocation, DNS, public records |\n| Malware | `\u002Fctf-malware` | Obfuscated scripts, C2 traffic, PE\u002F.NET analysis |\n| Misc | `\u002Fctf-misc` | Jails, encodings, RF\u002FSDR, esoteric languages, constraint solving |\n\nYou can also invoke `\u002Fctf-\u003Ccategory>` to load the full skill instructions with detailed techniques.\n\n### Step 4: Pivot When Stuck\n\nIf your first approach doesn't work:\n\n1. **Re-examine assumptions** -- Is this really the category you think? A \"web\" challenge might need crypto for JWT forgery. A \"forensics\" PCAP might contain a pwn exploit to replay.\n2. **Try a different category skill** -- Many challenges span multiple categories. Invoke a second skill for the cross-cutting technique.\n3. **Look for what you missed** -- Hidden files, alternate ports, response headers, comments in source, metadata in images.\n4. **Simplify** -- If an exploit is too complex, check if there's a simpler path (default creds, known CVE, logic bug).\n5. **Check edge cases** -- Off-by-one, race conditions, integer overflow, encoding mismatches.\n\n**Common multi-category patterns:**\n- Forensics + Crypto: encrypted data in PCAP\u002Fdisk image, need crypto to decrypt\n- Web + Reverse: WASM or obfuscated JS in web challenge\n- Web + Crypto: JWT forgery, custom MAC\u002Fsignature schemes\n- Reverse + Pwn: reverse the binary first, then exploit the vulnerability\n- Forensics + OSINT: recover data from dump, then trace it via public sources\n- Misc + Crypto: jail escape requires building crypto primitives under constraints\n- OSINT + Stego: social media posts with unicode homoglyph steganography (Cyrillic lookalikes encode bits)\n- Web + Forensics: paywall bypass (curl reveals content hidden by CSS overlays)\n- Misc + Crypto + Game Theory: multi-phase interactive challenges with AES decryption → HMAC commitment → combinatorial game solving (GF(256) Nim)\n- Crypto + Geometry + Lattice: multi-layer challenges progressing from spatial reconstruction → subspace recovery → LWE solving → AES-GCM decryption\n- Forensics + Signal Processing: power traces \u002F side-channel analysis requiring statistical analysis of measurement data\n- Forensics + Network + Encoding: timing-based encoding in PCAP (inter-packet intervals encode binary data)\n\n### Step 5: Generate Write-up\n\nAfter solving the challenge, invoke `\u002Fctf-writeup` to generate a standardized submission-style writeup — concise, reproducible, and ready for competition organizers or teammates to validate.\n\n## Flag Formats\n\nFlags vary by CTF. Common formats:\n- `flag{...}`, `FLAG{...}`, `CTF{...}`, `TEAM{...}`\n- Custom prefixes: check the challenge description or CTF rules for the format (e.g., `ENO{...}`, `HTB{...}`, `picoCTF{...}`)\n- Sometimes just a plaintext string with no wrapper\n\n**Validation rule (important):**\n- If you find multiple flag-like strings, treat them as candidates and validate before finalizing.\n- Prefer the token tied to the intended artifact\u002Fworkflow (not random metadata noise or obvious decoys).\n- Do a corpus-wide uniqueness check and include the source file\u002Fpath when reporting.\n\n```bash\n# Search for common flag patterns in files\ngrep -rniE '(flag|ctf|eno|htb|pico)\\{' .\n# Search in binary\u002Fmemory output\nstrings output.bin | grep -iE '\\{.*\\}'\n```\n\n## Quick Reference\n\n```bash\n# Recon\nfile *                                    # Identify file types\nstrings binary | grep -i flag             # Quick string search\nxxd binary | head -20                     # Hex dump header\nbinwalk -e firmware.bin                   # Extract embedded files\nchecksec --file=binary                    # Check binary protections\n\n# Connect\nnc host port                              # Connect to challenge\necho -e \"answer1\\nanswer2\" | nc host port # Scripted input\ncurl -v http:\u002F\u002Fhost:port\u002F                 # HTTP recon\n\n# Python exploit template\npython3 -c \"\nfrom pwn import *\nr = remote('host', port)\nr.interactive()\n\"\n```\n\n## Challenge\n\n$ARGUMENTS\n","# CTF Challenge Solver\n\nYou're a skilled CTF player. Your goal is to solve the challenge and find the flag.\n\n## Environment Setup\n\nTwo setup strategies depending on your workflow:\n\n### Pre-install (recommended before competitions)\n\nUse the central installer entrypoint:\n\n```bash\nbash scripts\u002Finstall_ctf_tools.sh all\n```\n\nRun a narrower mode when you only want one tool group:\n\n```bash\nbash scripts\u002Finstall_ctf_tools.sh python\nbash scripts\u002Finstall_ctf_tools.sh apt\nbash scripts\u002Finstall_ctf_tools.sh brew\nbash scripts\u002Finstall_ctf_tools.sh gems\nbash scripts\u002Finstall_ctf_tools.sh go\nbash scripts\u002Finstall_ctf_tools.sh manual\n```\n\nThe full package lists now live in [scripts\u002Finstall_ctf_tools.sh](..\u002Fscripts\u002Finstall_ctf_tools.sh).\n\n### On-demand (during challenges)\n\nEach category skill's `SKILL.md` has a **Prerequisites** section listing only the tools needed for that category. Install as you go.\n\n## Workflow\n\n### Step 0: CTFd Platform Detection\n\nIf the CTF platform URL is known, check if it runs CTFd and switch to API-driven navigation:\n\n```bash\n# Detect CTFd (look for \u002Fapi\u002Fv1\u002F and \u002Fthemes\u002Fcore\u002F)\ncurl -s \"$CTF_URL\u002Fapi\u002Fv1\u002F\" | head -5\ncurl -s \"$CTF_URL\" | grep -oE '\u002Fthemes\u002Fcore\u002F'\n```\n\nIf CTFd is detected, **ask the user for their API token** (generated from CTFd Settings > Access Tokens). The token is not provided by default — the user must create one in the CTFd web UI first. Once provided, set the environment variables and proceed via API:\n\n```bash\nexport CTF_URL=\"https:\u002F\u002Fctf.example.com\"\nexport CTF_TOKEN=\"ctfd_...\"  # Ask user for this\n```\n\nInvoke `\u002Fctf-misc` and load its `ctfd-navigation.md` for the full API reference and Python client class.\n\n### Step 1: Recon\n\n1. **Explore files** -- List the challenge directory, run `file *` on everything\n2. **Triage binaries** -- `strings`, `xxd | head`, `binwalk`, `checksec` on binaries\n3. **Fetch links** -- If the challenge mentions URLs, fetch them FIRST for context\n4. **Connect** -- Try remote services (`nc`) to understand what they expect\n5. **Read hints** -- Challenge descriptions, filenames, and comments often contain clues\n\n### Step 2: Categorize\n\nDetermine the primary category, then invoke the matching skill.\n\n**By file type:**\n- `.pcap`, `.pcapng`, `.evtx`, `.raw`, `.dd`, `.E01` -> forensics\n- `.elf`, `.exe`, `.so`, `.dll`, binary with no extension -> reverse or pwn (check if remote service provided -- if yes, likely pwn)\n- `.py`, `.sage`, `.txt` with numbers -> crypto\n- `.apk`, `.wasm`, `.pyc` -> reverse\n- Web URL or source code with HTML\u002FJS\u002FPHP\u002Ftemplates -> web\n- Images, audio, PDFs with no obvious content -> forensics (steganography)\n\n**By challenge description keywords:**\n- \"buffer overflow\", \"ROP\", \"shellcode\", \"libc\", \"heap\" -> pwn\n- \"RSA\", \"AES\", \"cipher\", \"encrypt\", \"prime\", \"modulus\", \"lattice\", \"LWE\", \"GCM\" -> crypto\n- \"XSS\", \"SQL\", \"injection\", \"cookie\", \"JWT\", \"SSRF\" -> web\n- \"disk image\", \"memory dump\", \"packet capture\", \"registry\", \"power trace\", \"side-channel\", \"spectrogram\", \"audio tracks\", \"MKV\" -> forensics\n- \"find\", \"locate\", \"identify\", \"who\", \"where\" -> osint\n- \"obfuscated\", \"packed\", \"C2\", \"malware\", \"beacon\" -> malware\n- \"jail\", \"sandbox\", \"escape\", \"encoding\", \"signal\", \"game\", \"Nim\", \"commitment\", \"Gray code\" -> misc\n\n**By service behavior:**\n- Port with interactive prompt, crash on long input -> pwn\n- HTTP service -> web\n- netcat with math\u002Fcrypto puzzles -> crypto\n- netcat with restricted shell or eval -> misc (jail)\n\n### Step 3: Invoke the Category Skill\n\nOnce you identify the category, **invoke the matching skill** to get specialized techniques:\n\n| Category | Invoke | When to Use |\n|----------|--------|-------------|\n| Web | `\u002Fctf-web` | XSS, SQLi, SSTI, SSRF, JWT, file uploads, prototype pollution |\n| Pwn | `\u002Fctf-pwn` | Buffer overflow, format string, heap, ROP, sandbox escape |\n| Crypto | `\u002Fctf-crypto` | RSA, AES, ECC, PRNG, ZKP, classical ciphers |\n| Reverse | `\u002Fctf-reverse` | Binary analysis, game clients, VMs, obfuscated code |\n| Forensics | `\u002Fctf-forensics` | Disk images, memory dumps, event logs, stego, network captures |\n| OSINT | `\u002Fctf-osint` | Social media, geolocation, DNS, public records |\n| Malware | `\u002Fctf-malware` | Obfuscated scripts, C2 traffic, PE\u002F.NET analysis |\n| Misc | `\u002Fctf-misc` | Jails, encodings, RF\u002FSDR, esoteric languages, constraint solving |\n\nYou can also invoke `\u002Fctf-\u003Ccategory>` to load the full skill instructions with detailed techniques.\n\n### Step 4: Pivot When Stuck\n\nIf your first approach doesn't work:\n\n1. **Re-examine assumptions** -- Is this really the category you think? A \"web\" challenge might need crypto for JWT forgery. A \"forensics\" PCAP might contain a pwn exploit to replay.\n2. **Try a different category skill** -- Many challenges span multiple categories. Invoke a second skill for the cross-cutting technique.\n3. **Look for what you missed** -- Hidden files, alternate ports, response headers, comments in source, metadata in images.\n4. **Simplify** -- If an exploit is too complex, check if there's a simpler path (default creds, known CVE, logic bug).\n5. **Check edge cases** -- Off-by-one, race conditions, integer overflow, encoding mismatches.\n\n**Common multi-category patterns:**\n- Forensics + Crypto: encrypted data in PCAP\u002Fdisk image, need crypto to decrypt\n- Web + Reverse: WASM or obfuscated JS in web challenge\n- Web + Crypto: JWT forgery, custom MAC\u002Fsignature schemes\n- Reverse + Pwn: reverse the binary first, then exploit the vulnerability\n- Forensics + OSINT: recover data from dump, then trace it via public sources\n- Misc + Crypto: jail escape requires building crypto primitives under constraints\n- OSINT + Stego: social media posts with unicode homoglyph steganography (Cyrillic lookalikes encode bits)\n- Web + Forensics: paywall bypass (curl reveals content hidden by CSS overlays)\n- Misc + Crypto + Game Theory: multi-phase interactive challenges with AES decryption → HMAC commitment → combinatorial game solving (GF(256) Nim)\n- Crypto + Geometry + Lattice: multi-layer challenges progressing from spatial reconstruction → subspace recovery → LWE solving → AES-GCM decryption\n- Forensics + Signal Processing: power traces \u002F side-channel analysis requiring statistical analysis of measurement data\n- Forensics + Network + Encoding: timing-based encoding in PCAP (inter-packet intervals encode binary data)\n\n### Step 5: Generate Write-up\n\nAfter solving the challenge, invoke `\u002Fctf-writeup` to generate a standardized submission-style writeup — concise, reproducible, and ready for competition organizers or teammates to validate.\n\n## Flag Formats\n\nFlags vary by CTF. Common formats:\n- `flag{...}`, `FLAG{...}`, `CTF{...}`, `TEAM{...}`\n- Custom prefixes: check the challenge description or CTF rules for the format (e.g., `ENO{...}`, `HTB{...}`, `picoCTF{...}`)\n- Sometimes just a plaintext string with no wrapper\n\n**Validation rule (important):**\n- If you find multiple flag-like strings, treat them as candidates and validate before finalizing.\n- Prefer the token tied to the intended artifact\u002Fworkflow (not random metadata noise or obvious decoys).\n- Do a corpus-wide uniqueness check and include the source file\u002Fpath when reporting.\n\n```bash\n# Search for common flag patterns in files\ngrep -rniE '(flag|ctf|eno|htb|pico)\\{' .\n# Search in binary\u002Fmemory output\nstrings output.bin | grep -iE '\\{.*\\}'\n```\n\n## Quick Reference\n\n```bash\n# Recon\nfile *                                    # Identify file types\nstrings binary | grep -i flag             # Quick string search\nxxd binary | head -20                     # Hex dump header\nbinwalk -e firmware.bin                   # Extract embedded files\nchecksec --file=binary                    # Check binary protections\n\n# Connect\nnc host port                              # Connect to challenge\necho -e \"answer1\\nanswer2\" | nc host port # Scripted input\ncurl -v http:\u002F\u002Fhost:port\u002F                 # HTTP recon\n\n# Python exploit template\npython3 -c \"\nfrom pwn import *\nr = remote('host', port)\nr.interactive()\n\"\n```\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},"[category] [challenge-file-or-url]","true","Bash Read Write Edit Glob Grep Task WebFetch WebSearch Skill","Requires filesystem-based agent (Claude Code or similar) with bash, Python 3, and internet access. Orchestrates other ctf-* skills.","main","8859218955d9504cd18b59e7892100718039d3b4","data\u002Fskills\u002Fljagiello-ctf-skills\u002Fsolve-challenge",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 solve-challenge",{"tool":43,"command":44},"bunx","bunx skills add om-scogo\u002Fskillsh-scraper --skill solve-challenge",{"tool":46,"command":47},"pnpm","pnpm dlx skills add om-scogo\u002Fskillsh-scraper --skill solve-challenge","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fljagiello-ctf-skills\u002Fsolve-challenge\u002FSkill.md",true,[51],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"metadata.json","REFERENCE","参考文档",445,"https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fljagiello-ctf-skills\u002Fsolve-challenge\u002Fmetadata.json",[58,65,70,77,82,89],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"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":66,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7D6M85CKKN87TA98VCQV4H7","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\u002FSkill.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"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":78,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7D4ZHZKJD2RSNGAF63V14P4","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\u002FSkill.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"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":90,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7D4Z4MVYVY3NMJ18BNV6WNA","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002FSkill.md",[],[]]