[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DXT8FA72C97SP69GVX8SE2":3,"skill-same:01M6DXT8FA72C97SP69GVX8SE2":72},{"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":28,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":14,"repositoryHtmlUrl":53,"repositoryHomepageUrl":6,"ownerHtmlUrl":54,"ownerBlogUrl":55,"ownerDescription":56,"updatedAt":57,"install":58,"resources":71},"01M6DXT8FA72C97SP69GVX8SE2","plan-writing",null,"Structured task planning with clear breakdowns, dependencies, and verification criteria. Use when implementing features, refactoring, or any multi-step work.","EthanSheehan\u002FGrid-Sentinel","EthanSheehan","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F174215275?v=4","01M6DX9589ENESB2AYW9YK4Y50","Ethan Sheehan","01M6DX95P06JXASASFQZRFQ1NM",0,"MIT","https:\u002F\u002Fgithub.com\u002FEthanSheehan\u002FGrid-Sentinel\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fplan-writing\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"writing","plan writing","plan","planning","task planning","verification","refactoring","grep","work","read","use","task","dependencies","structured","clear","2026-11-10 10:12:30",false,"---\nname: plan-writing\ndescription: Structured task planning with clear breakdowns, dependencies, and verification criteria. Use when implementing features, refactoring, or any multi-step work.\nallowed-tools: Read, Glob, Grep\n---\n\n# Plan Writing\n\n> Source: obra\u002Fsuperpowers\n\n## Overview\nThis skill provides a framework for breaking down work into clear, actionable tasks with verification criteria.\n\n## Task Breakdown Principles\n\n### 1. Small, Focused Tasks\n- Each task should take 2-5 minutes\n- One clear outcome per task\n- Independently verifiable\n\n### 2. Clear Verification\n- How do you know it's done?\n- What can you check\u002Ftest?\n- What's the expected output?\n\n### 3. Logical Ordering\n- Dependencies identified\n- Parallel work where possible\n- Critical path highlighted\n- **Phase X: Verification is always LAST**\n\n### 4. Dynamic Naming in Project Root\n- Plan files are saved as `{task-slug}.md` in the PROJECT ROOT\n- Name derived from task (e.g., \"add auth\" → `auth-feature.md`)\n- **NEVER** inside `.claude\u002F`, `docs\u002F`, or temp folders\n\n## Planning Principles (NOT Templates!)\n\n> ? **NO fixed templates. Each plan is UNIQUE to the task.**\n\n### Principle 1: Keep It SHORT\n\n| ❌ Wrong | ✅ Right |\n|----------|----------|\n| 50 tasks with sub-sub-tasks | 5-10 clear tasks max |\n| Every micro-step listed | Only actionable items |\n| Verbose descriptions | One-line per task |\n\n> **Rule:** If plan is longer than 1 page, it's too long. Simplify.\n\n---\n\n### Principle 2: Be SPECIFIC, Not Generic\n\n| ❌ Wrong | ✅ Right |\n|----------|----------|\n| \"Set up project\" | \"Run `npx create-next-app`\" |\n| \"Add authentication\" | \"Install next-auth, create `\u002Fapi\u002Fauth\u002F[...nextauth].ts`\" |\n| \"Style the UI\" | \"Add Tailwind classes to `Header.tsx`\" |\n\n> **Rule:** Each task should have a clear, verifiable outcome.\n\n---\n\n### Principle 3: Dynamic Content Based on Project Type\n\n**For NEW PROJECT:**\n- What tech stack? (decide first)\n- What's the MVP? (minimal features)\n- What's the file structure?\n\n**For FEATURE ADDITION:**\n- Which files are affected?\n- What dependencies needed?\n- How to verify it works?\n\n**For BUG FIX:**\n- What's the root cause?\n- What file\u002Fline to change?\n- How to test the fix?\n\n---\n\n### Principle 4: Scripts Are Project-Specific\n\n> ? **DO NOT copy-paste script commands. Choose based on project type.**\n\n| Project Type | Relevant Scripts |\n|--------------|------------------|\n| Frontend\u002FReact | `ux_audit.py`, `accessibility_checker.py` |\n| Backend\u002FAPI | `api_validator.py`, `security_scan.py` |\n| Mobile | `mobile_audit.py` |\n| Database | `schema_validator.py` |\n| Full-stack | Mix of above based on what you touched |\n\n**Wrong:** Adding all scripts to every plan\n**Right:** Only scripts relevant to THIS task\n\n---\n\n### Principle 5: Verification is Simple\n\n| ❌ Wrong | ✅ Right |\n|----------|----------|\n| \"Verify the component works correctly\" | \"Run `npm run dev`, click button, see toast\" |\n| \"Test the API\" | \"curl localhost:3000\u002Fapi\u002Fusers returns 200\" |\n| \"Check styles\" | \"Open browser, verify dark mode toggle works\" |\n\n---\n\n## Plan Structure (Flexible, Not Fixed!)\n\n```\n# [Task Name]\n\n## Goal\nOne sentence: What are we building\u002Ffixing?\n\n## Tasks\n- [ ] Task 1: [Specific action] → Verify: [How to check]\n- [ ] Task 2: [Specific action] → Verify: [How to check]\n- [ ] Task 3: [Specific action] → Verify: [How to check]\n\n## Done When\n- [ ] [Main success criteria]\n```\n\n> **That's it.** No phases, no sub-sections unless truly needed.\n> Keep it minimal. Add complexity only when required.\n\n## Notes\n[Any important considerations]\n```\n\n---\n\n## Best Practices (Quick Reference)\n\n1. **Start with goal** - What are we building\u002Ffixing?\n2. **Max 10 tasks** - If more, break into multiple plans\n3. **Each task verifiable** - Clear \"done\" criteria\n4. **Project-specific** - No copy-paste templates\n5. **Update as you go** - Mark `[x]` when complete\n\n---\n\n## When to Use\n\n- New project from scratch\n- Adding a feature\n- Fixing a bug (if complex)\n- Refactoring multiple files\n","# Plan Writing\n\n> Source: obra\u002Fsuperpowers\n\n## Overview\nThis skill provides a framework for breaking down work into clear, actionable tasks with verification criteria.\n\n## Task Breakdown Principles\n\n### 1. Small, Focused Tasks\n- Each task should take 2-5 minutes\n- One clear outcome per task\n- Independently verifiable\n\n### 2. Clear Verification\n- How do you know it's done?\n- What can you check\u002Ftest?\n- What's the expected output?\n\n### 3. Logical Ordering\n- Dependencies identified\n- Parallel work where possible\n- Critical path highlighted\n- **Phase X: Verification is always LAST**\n\n### 4. Dynamic Naming in Project Root\n- Plan files are saved as `{task-slug}.md` in the PROJECT ROOT\n- Name derived from task (e.g., \"add auth\" → `auth-feature.md`)\n- **NEVER** inside `.claude\u002F`, `docs\u002F`, or temp folders\n\n## Planning Principles (NOT Templates!)\n\n> ? **NO fixed templates. Each plan is UNIQUE to the task.**\n\n### Principle 1: Keep It SHORT\n\n| ❌ Wrong | ✅ Right |\n|----------|----------|\n| 50 tasks with sub-sub-tasks | 5-10 clear tasks max |\n| Every micro-step listed | Only actionable items |\n| Verbose descriptions | One-line per task |\n\n> **Rule:** If plan is longer than 1 page, it's too long. Simplify.\n\n---\n\n### Principle 2: Be SPECIFIC, Not Generic\n\n| ❌ Wrong | ✅ Right |\n|----------|----------|\n| \"Set up project\" | \"Run `npx create-next-app`\" |\n| \"Add authentication\" | \"Install next-auth, create `\u002Fapi\u002Fauth\u002F[...nextauth].ts`\" |\n| \"Style the UI\" | \"Add Tailwind classes to `Header.tsx`\" |\n\n> **Rule:** Each task should have a clear, verifiable outcome.\n\n---\n\n### Principle 3: Dynamic Content Based on Project Type\n\n**For NEW PROJECT:**\n- What tech stack? (decide first)\n- What's the MVP? (minimal features)\n- What's the file structure?\n\n**For FEATURE ADDITION:**\n- Which files are affected?\n- What dependencies needed?\n- How to verify it works?\n\n**For BUG FIX:**\n- What's the root cause?\n- What file\u002Fline to change?\n- How to test the fix?\n\n---\n\n### Principle 4: Scripts Are Project-Specific\n\n> ? **DO NOT copy-paste script commands. Choose based on project type.**\n\n| Project Type | Relevant Scripts |\n|--------------|------------------|\n| Frontend\u002FReact | `ux_audit.py`, `accessibility_checker.py` |\n| Backend\u002FAPI | `api_validator.py`, `security_scan.py` |\n| Mobile | `mobile_audit.py` |\n| Database | `schema_validator.py` |\n| Full-stack | Mix of above based on what you touched |\n\n**Wrong:** Adding all scripts to every plan\n**Right:** Only scripts relevant to THIS task\n\n---\n\n### Principle 5: Verification is Simple\n\n| ❌ Wrong | ✅ Right |\n|----------|----------|\n| \"Verify the component works correctly\" | \"Run `npm run dev`, click button, see toast\" |\n| \"Test the API\" | \"curl localhost:3000\u002Fapi\u002Fusers returns 200\" |\n| \"Check styles\" | \"Open browser, verify dark mode toggle works\" |\n\n---\n\n## Plan Structure (Flexible, Not Fixed!)\n\n```\n# [Task Name]\n\n## Goal\nOne sentence: What are we building\u002Ffixing?\n\n## Tasks\n- [ ] Task 1: [Specific action] → Verify: [How to check]\n- [ ] Task 2: [Specific action] → Verify: [How to check]\n- [ ] Task 3: [Specific action] → Verify: [How to check]\n\n## Done When\n- [ ] [Main success criteria]\n```\n\n> **That's it.** No phases, no sub-sections unless truly needed.\n> Keep it minimal. Add complexity only when required.\n\n## Notes\n[Any important considerations]\n```\n\n---\n\n## Best Practices (Quick Reference)\n\n1. **Start with goal** - What are we building\u002Ffixing?\n2. **Max 10 tasks** - If more, break into multiple plans\n3. **Each task verifiable** - Clear \"done\" criteria\n4. **Project-specific** - No copy-paste templates\n5. **Update as you go** - Mark `[x]` when complete\n\n---\n\n## When to Use\n\n- New project from scratch\n- Adding a feature\n- Fixing a bug (if complex)\n- Refactoring multiple files\n",{"name":5,"description":7,"allowed-tools":49},"Read, Glob, Grep","main","33d99efaac9ea5758fc27120b467eca96ad020d9",".agent\u002Fskills\u002Fplan-writing","https:\u002F\u002Fgithub.com\u002FEthanSheehan\u002FGrid-Sentinel","https:\u002F\u002Fgithub.com\u002FEthanSheehan","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fethan-sheehan\u002F","Aerospace Engineering Student at the University of Bristol \u002F\u002F Propulsion Lead at HyPower Bristol","2026-05-22 21:19:23",{"source":8,"skillName":5,"commands":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add EthanSheehan\u002FGrid-Sentinel --skill plan-writing",{"tool":64,"command":65},"bunx","bunx skills add EthanSheehan\u002FGrid-Sentinel --skill plan-writing",{"tool":67,"command":68},"pnpm","pnpm dlx skills add EthanSheehan\u002FGrid-Sentinel --skill plan-writing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FEthanSheehan\u002FGrid-Sentinel\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fplan-writing\u002FSKILL.md",true,[],[73,101,134,147,160,185],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":82,"publishedAt":44},"01M6DY3X97YDSKHCCZG9KMASHA","zapier-make-patterns","No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity - these platforms have their own patterns, pitfalls, and breaking points.  This skill covers when to use which platform, how to build reliable automations, and when to graduate to code-based solutions. Key insight: Zapier optimizes for simplicity and integrations (7000+ apps), Make optimizes for power","https:\u002F\u002Fgithub.com\u002FEthanSheehan\u002FGrid-Sentinel\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fzapier-make-patterns\u002FSKILL.md",[79],{"categoryNo":80,"categoryName":81,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[83,84,85,86,87,88,89,90,91,92,93,94,39,95,96,97,98,99,100,29],"zapier make patterns","patterns","workflow","integrations","how to","apps","platform","but","build","complexity","power","simplicity","business","automate","how","apache","code","automation",{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":113,"publishedAt":44},"01M6DY3SVP128ZZPF2478H9JYZ","Cross-Site Scripting and HTML Injection Testing","This skill should be used when the user asks to \"test for XSS vulnerabilities\", \"perform cross-site scripting attacks\", \"identify HTML injection flaws\", \"exploit client-side injection vulnerabilities\", \"steal cookies via XSS\", or \"bypass content security policies\". It provides comprehensive techniques for detecting, exploiting, and understanding XSS and HTML injection attack vectors in web applications.","https:\u002F\u002Fgithub.com\u002FEthanSheehan\u002FGrid-Sentinel\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fxss-html-injection\u002FSKILL.md",[107,110],{"categoryNo":108,"categoryName":109,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":111,"categoryName":112,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[114,115,116,117,118,119,120,121,122,123,124,125,126,127,128,129,130,131,132,133],"html injection testing","Cross Site Scripting and HTML Injection Testing","injection","scripting","site","html","testing","exploit","user","applications","xss","cookies","content","web","test","vectors","via","steal","security","vulnerabilities",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":143,"publishedAt":44},"01M6DY3D694G80Y5N79CD1J575","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002FEthanSheehan\u002FGrid-Sentinel\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fwriting-skills\u002FSKILL.md",[140,141,142],{"categoryNo":108,"categoryName":109,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},[29,144,145,39,146,37],"writing skills","deployment","editing",{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":155,"publishedAt":44},"01M6DY3A7BM31W5Q2QARW00JHS","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002FEthanSheehan\u002FGrid-Sentinel\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fwriting-plans\u002FSKILL.md",[153,154],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},[156,29,157,158,40,39,99,159],"writing plans","plans","requirements","spec",{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":164,"categories":165,"keywords":167,"publishedAt":44},"01M6DY36NSATM95HR7HMVZJYB3","workflow-automation","Workflow automation is the infrastructure that makes AI agents reliable. Without durable execution, a network hiccup during a 10-step payment flow means lost money and angry customers. With it, workflows resume exactly where they left off.  This skill covers the platforms (n8n, Temporal, Inngest) and patterns (sequential, parallel, orchestrator-worker) that turn brittle scripts into production-grade automation.  Key insight: The platforms make different tradeoffs. n8n optimizes for accessibility","https:\u002F\u002Fgithub.com\u002FEthanSheehan\u002FGrid-Sentinel\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fworkflow-automation\u002FSKILL.md",[166],{"categoryNo":80,"categoryName":81,"taxonomyType":21,"taxonomyTypeDesc":22},[168,100,85,169,170,171,98,172,173,174,175,176,177,178,179,180,181,182,183,184],"Workflow Automation","Production","flow","network","workflows","accessibility","ai agents","execution","scripts","worker","payment","n8n","money","resume","orchestrator","parallel","inngest",{"skillNo":186,"name":187,"nameZh":6,"description":188,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":189,"categories":190,"keywords":192,"publishedAt":44},"01M6DY32QTGD80MQHJ8TPDH53H","WordPress Penetration Testing","This skill should be used when the user asks to \"pentest WordPress sites\", \"scan WordPress for vulnerabilities\", \"enumerate WordPress users, themes, or plugins\", \"exploit WordPress vulnerabilities\", or \"use WPScan\". It provides comprehensive WordPress security assessment methodologies.","https:\u002F\u002Fgithub.com\u002FEthanSheehan\u002FGrid-Sentinel\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fwordpress-penetration-testing\u002FSKILL.md",[191],{"categoryNo":108,"categoryName":109,"taxonomyType":21,"taxonomyTypeDesc":22},[120,187,193,194,195,196,197,198,121,39,122,199,200,133,132],"penetration testing","wordpress","security assessment","sites","scan","pentest","plugins","assessment"]