[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CAPX4J8Z6CYRFSDVFADDS1":3,"skill-same:01M6CAPX4J8Z6CYRFSDVFADDS1":122},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":50,"linkOnly":51,"markdownContent":52,"markdownBody":53,"frontMatter":54,"refName":55,"commitSha":56,"skillDirectory":57,"forksCount":58,"repositoryHtmlUrl":59,"repositoryHomepageUrl":6,"ownerHtmlUrl":60,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":61,"install":62,"resources":75},"01M6CAPX4J8Z6CYRFSDVFADDS1","agentic-coding-methodology-composition",null,"When the user asks to compare, evaluate, or compose AI coding agent methodologies and skills frameworks (Superpowers, GSD Core, grill-me, OpenSpec, BMAD, Spec-Kit, Kiro, gstack, GSTACK, custom \u002Fskill packs). Use for \"should we install X?\", \"how do X and Y differ?\", \"can we combine Z with W?\", \"is there a methodology for X?\", or any question about how multiple AI-tooling philosophies interact. Class-level umbrella covering methodology profiling, installation status verification, composition pattern analysis, and anti-pattern documentation.","jleechanorg\u002Fjleechan-skills","jleechanorg","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F221404966?v=4","01M6C1VJ99XG950X1DWPEBCBGX","01M6C1VJDK5YVDNT3362RT5WSB",6,"MIT","https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002Fhermes\u002Fskills\u002Fsoftware-development\u002Fagentic-coding-methodology-composition\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49],"agentic","agentic coding","methodology","Composition","coding","agentic coding methodology composition","when","coding agent","kit","kiro","pattern","me","gstack","grill","ai coding","compose","tooling","grill-me","superpowers","use","question","profiling","how","analysis","verification","core","documentation","2026-11-10 10:12:30",false,"---\nname: agentic-coding-methodology-composition\ndescription: When the user asks to compare, evaluate, or compose AI coding agent methodologies and skills frameworks (Superpowers, GSD Core, grill-me, OpenSpec, BMAD, Spec-Kit, Kiro, gstack, GSTACK, custom \u002Fskill packs). Use for \"should we install X?\", \"how do X and Y differ?\", \"can we combine Z with W?\", \"is there a methodology for X?\", or any question about how multiple AI-tooling philosophies interact. Class-level umbrella covering methodology profiling, installation status verification, composition pattern analysis, and anti-pattern documentation.\n---\n\n# Agentic Coding Methodology Composition\n\nCompare, evaluate, and compose AI coding agent methodologies and skills frameworks. Class of work: \"should we use methodology X?\" \u002F \"how do X and Y compare?\" \u002F \"can Z and W coexist?\" \u002F \"why is my agent misbehaving in a way that maps to a methodology design?\".\n\n## When to load this skill\n\n- User asks about a specific AI coding methodology (Superpowers, GSD Core, grill-me, OpenSpec, BMAD, Spec-Kit, Kiro, gstack, GSTACK, custom \u002Fskill packs).\n- User asks \"should we install X?\" \u002F \"is X worth it?\" \u002F \"how do X and Y differ?\".\n- User asks for a combo analysis (\"can we run X with Y?\" \u002F \"what's the best of both worlds?\").\n- User asks about an emerging methodology and wants to know how it relates to existing ones.\n- User reports an agent failure that maps to a methodology design (e.g., \"it skipped TDD\" → check Superpowers' HARD-GATE; \"context bloat after 2 hours\" → check GSD Core's context-engineering rationale).\n\n## Methodology landscape (snapshot 2026-07-30)\n\n| Methodology | Author | Canonical source | Local status |\n|---|---|---|---|\n| Superpowers | Jesse Vincent (obra) | https:\u002F\u002Fgithub.com\u002Fobra\u002Fsuperpowers | Installed v6.2.0 |\n| GSD Core | TÂCHES | https:\u002F\u002Fgithub.com\u002Fopen-gsd\u002Fgsd-core | Installed v1.9.0 (`--profile=full`) — see `--profile` pitfall |\n| grill-me \u002F grilling | Matt Pocock | https:\u002F\u002Fgithub.com\u002Fmattpocock\u002Fskills | Installed (21 Matt Pocock skills at `~\u002F.claude\u002Fskills\u002F{grill-me,...}`) |\n| OpenSpec | Fission-AI | https:\u002F\u002Fgithub.com\u002FFission-AI\u002FOpenSpec | Not installed |\n| BMAD Method | bmadcode | https:\u002F\u002Fgithub.com\u002Fbmadcode\u002FBMAD-METHOD | Not installed |\n| Spec-Kit | GitHub | https:\u002F\u002Fgithub.com\u002Fgithub\u002Fspec-kit | Not installed |\n| Kiro Specs | AWS | https:\u002F\u002Fkiro.dev | Not installed |\n| GSTACK | garrytan | https:\u002F\u002Fgithub.com\u002Fgarrytan\u002Fgstack | Not installed |\n\n(See `references\u002F` for per-methodology profiles with verified installation paths, distinctive features, and source-of-truth URLs.)\n\n## Workflow — methodology-composition analysis\n\n### Phase 0: clarify scope\n\nSingle-methodology or comparison? If comparison, name candidates or \"compare all major frameworks\" (≥3).\n\n### Phase 1: canonical-source verification\n\nFor each methodology:\n1. **Find the canonical repo** — GitHub org, official docs site, npm package, plugin marketplace. Reject mirrors\u002Fforks unless explicit.\n2. **Verify recency** — confirm the canonical repo is still maintained. Watch for \"this repo has moved\" redirects (e.g., `gsd-build\u002Fget-shit-done` archived → `open-gsd\u002Fgsd-core`).\n3. **Verify local install** — see `references\u002Finstallation-check.md`.\n\n### Phase 2: profile each methodology\n\nUse `references\u002Fmethodology-profile-template.md` to capture:\n- Author + canonical source\n- One-line positioning\n- Pipeline \u002F loop \u002F workflow\n- Distinctive features (what it does that others don't)\n- Invocation model (auto-fire vs opt-in)\n- Artifact tree (where state lives)\n- Multi-harness support\n- Known anti-patterns\n\n### Phase 3: composition analysis\n\nIdentify:\n- **Overlap zones** (where two methodologies do similar things — pick one as authoritative).\n- **Complement zones** (where one extends the other).\n- **Conflict zones** (where one explicitly fights the other, e.g., Superpowers' HARD-GATE vs opt-in frameworks).\n- **Outer-loop \u002F inner-loop splits** (GSD Core for milestone continuity, Superpowers for per-task TDD).\n\nOutput: a composition-recommendation matrix with concrete install paths.\n\n### Phase 4: anti-pattern audit\n\nCheck against `references\u002Fcomposition-patterns.md` for known anti-patterns. Flag any that apply to the user's setup.\n\n### Phase 5: deliver\n\nSlack-native format per SOUL.md `colored-icons-in-status-reports`:\n- ? Healthy (sources confirmed, install status)\n- ? What each does that others don't\n- ? How they compose\n- ? Risky \u002F anti-patterns\n- ? Recommended combo\n- ? Next actions\n\nApply LLM-provenance caveat footer per SOUL.md `llm-provenance-caveat`. Hyperlink every URL per `no-trailing-asteri[REDACTED_OPENAI_KEY]` and `pr-hyperlink` rules.\n\n### Phase 5.5: execute the install (don't post the list and stop)\n\n**Load-bearing rule, verified 2026-07-30.** When the recommended-combo or Next-actions section enumerates installable commands (`npx @opengsd\u002Fgsd-core@latest --claude --global`, `npx skills@latest add mattpocock\u002Fskills --skill=grill-me -y -g`, etc.) AND the user said anything like \"install them\", \"set it up\", \"go ahead\", \"ship it\", \"let's do X\" — **execute the install in the same turn**, do not post the list and wait. The user will read the install summary in the next reply, not a static plan.\n\nIf the user asked for analysis only (\"compare X and Y\", \"how do they differ\"), do not install — analysis-only is a valid request.\n\nIf the user gave a guarded install directive (\"install them all but don't add default guidance\"), execute the install but **honor the guard**:\n- Default-install flags that auto-enable hooks → downgrade to lean profile (GSD: `--profile=core` not `full`; grill-me keeps `disable-model-invocation: true`).\n- Default guidance files → don't touch (`SOUL.md`, `CLAUDE.md`, plugin enable flags).\n- Verify post-install what got auto-configured and call it out honestly in the next reply. Don't hide it.\n\n## Anti-patterns (load-bearing)\n\n1. **Don't recommend installing all global frameworks.** Superpowers' HARD-GATE will fight GSD's `\u002Fgsd:*` namespace and grill-me's `disable-model-invocation: true`. Pick one as the per-session default; bring others in explicitly per-phase.\n2. **Don't accept GSD's `--profile=full` default when the user said \"no default guidance.\"** Full installs ~15 always-on hooks to `settings.json` (verified v1.9.0). Use `--profile=core` (~700 tokens eager-load) instead. See `references\u002Fgsd-core.md` for the full hook table.\n3. **Don't duplicate state trees.** GSD → `.planning\u002F`. Superpowers → `docs\u002Fsuperpowers\u002F{specs,plans}\u002F`. grill-me → nothing or CONTEXT.md. Designate one artifact tree as authoritative.\n4. **Don't use a pure interview primitive (grill-me) inside an execution loop.** Grill-me is for upstream alignment only.\n5. **Don't recommend a framework whose canonical repo has moved without flagging the redirect.** Always verify the live repo.\n6. **Don't treat star counts as signal of correctness.** GSD's 48.3k stars ≠ better than Superpowers' smaller community. They solve different problems.\n7. **Don't claim a methodology is \"installed\" without probing the filesystem.** See `references\u002Finstallation-check.md`.\n8. **Don't create status-cron jobs that ping the user about a choice they're still making.** When the user says \"install X but don't add default guidance,\" a 20m cron pinging them about \"did you pick a combo?\" violates the directive. Wait for the user's own next message; don't schedule a nudge.\n\n## Support files\n\n- `references\u002Fmethodology-profile-template.md` — capture template for one methodology\n- `references\u002Fsuperpowers.md` — Superpowers profile (obra, installed v6.2.0)\n- `references\u002Fgsd-core.md` — GSD Core profile (TÂCHES, not installed)\n- `references\u002Fgrill-me.md` — grill-me profile (Matt Pocock, not installed)\n- `references\u002Fcomposition-patterns.md` — verified combinations with anti-patterns\n- `references\u002Finstallation-check.md` — how to verify local install status per methodology\n\n## How to extend this skill\n\nWhen a new methodology emerges:\n1. Verify the canonical source (live repo, official docs).\n2. Add `references\u002F\u003Cname>.md` profile using the template.\n3. Update `composition-patterns.md` if it composes with existing methodologies.\n4. Update the landscape table in this SKILL.md.\n\nWhen a methodology moves (e.g., `gsd-build\u002Fget-shit-done` → `open-gsd\u002Fgsd-core`):\n1. Update the profile's canonical source.\n2. Note the redirect history in the profile.\n3. Grep existing references for stale URLs.","# Agentic Coding Methodology Composition\n\nCompare, evaluate, and compose AI coding agent methodologies and skills frameworks. Class of work: \"should we use methodology X?\" \u002F \"how do X and Y compare?\" \u002F \"can Z and W coexist?\" \u002F \"why is my agent misbehaving in a way that maps to a methodology design?\".\n\n## When to load this skill\n\n- User asks about a specific AI coding methodology (Superpowers, GSD Core, grill-me, OpenSpec, BMAD, Spec-Kit, Kiro, gstack, GSTACK, custom \u002Fskill packs).\n- User asks \"should we install X?\" \u002F \"is X worth it?\" \u002F \"how do X and Y differ?\".\n- User asks for a combo analysis (\"can we run X with Y?\" \u002F \"what's the best of both worlds?\").\n- User asks about an emerging methodology and wants to know how it relates to existing ones.\n- User reports an agent failure that maps to a methodology design (e.g., \"it skipped TDD\" → check Superpowers' HARD-GATE; \"context bloat after 2 hours\" → check GSD Core's context-engineering rationale).\n\n## Methodology landscape (snapshot 2026-07-30)\n\n| Methodology | Author | Canonical source | Local status |\n|---|---|---|---|\n| Superpowers | Jesse Vincent (obra) | https:\u002F\u002Fgithub.com\u002Fobra\u002Fsuperpowers | Installed v6.2.0 |\n| GSD Core | TÂCHES | https:\u002F\u002Fgithub.com\u002Fopen-gsd\u002Fgsd-core | Installed v1.9.0 (`--profile=full`) — see `--profile` pitfall |\n| grill-me \u002F grilling | Matt Pocock | https:\u002F\u002Fgithub.com\u002Fmattpocock\u002Fskills | Installed (21 Matt Pocock skills at `~\u002F.claude\u002Fskills\u002F{grill-me,...}`) |\n| OpenSpec | Fission-AI | https:\u002F\u002Fgithub.com\u002FFission-AI\u002FOpenSpec | Not installed |\n| BMAD Method | bmadcode | https:\u002F\u002Fgithub.com\u002Fbmadcode\u002FBMAD-METHOD | Not installed |\n| Spec-Kit | GitHub | https:\u002F\u002Fgithub.com\u002Fgithub\u002Fspec-kit | Not installed |\n| Kiro Specs | AWS | https:\u002F\u002Fkiro.dev | Not installed |\n| GSTACK | garrytan | https:\u002F\u002Fgithub.com\u002Fgarrytan\u002Fgstack | Not installed |\n\n(See `references\u002F` for per-methodology profiles with verified installation paths, distinctive features, and source-of-truth URLs.)\n\n## Workflow — methodology-composition analysis\n\n### Phase 0: clarify scope\n\nSingle-methodology or comparison? If comparison, name candidates or \"compare all major frameworks\" (≥3).\n\n### Phase 1: canonical-source verification\n\nFor each methodology:\n1. **Find the canonical repo** — GitHub org, official docs site, npm package, plugin marketplace. Reject mirrors\u002Fforks unless explicit.\n2. **Verify recency** — confirm the canonical repo is still maintained. Watch for \"this repo has moved\" redirects (e.g., `gsd-build\u002Fget-shit-done` archived → `open-gsd\u002Fgsd-core`).\n3. **Verify local install** — see `references\u002Finstallation-check.md`.\n\n### Phase 2: profile each methodology\n\nUse `references\u002Fmethodology-profile-template.md` to capture:\n- Author + canonical source\n- One-line positioning\n- Pipeline \u002F loop \u002F workflow\n- Distinctive features (what it does that others don't)\n- Invocation model (auto-fire vs opt-in)\n- Artifact tree (where state lives)\n- Multi-harness support\n- Known anti-patterns\n\n### Phase 3: composition analysis\n\nIdentify:\n- **Overlap zones** (where two methodologies do similar things — pick one as authoritative).\n- **Complement zones** (where one extends the other).\n- **Conflict zones** (where one explicitly fights the other, e.g., Superpowers' HARD-GATE vs opt-in frameworks).\n- **Outer-loop \u002F inner-loop splits** (GSD Core for milestone continuity, Superpowers for per-task TDD).\n\nOutput: a composition-recommendation matrix with concrete install paths.\n\n### Phase 4: anti-pattern audit\n\nCheck against `references\u002Fcomposition-patterns.md` for known anti-patterns. Flag any that apply to the user's setup.\n\n### Phase 5: deliver\n\nSlack-native format per SOUL.md `colored-icons-in-status-reports`:\n- ? Healthy (sources confirmed, install status)\n- ? What each does that others don't\n- ? How they compose\n- ? Risky \u002F anti-patterns\n- ? Recommended combo\n- ? Next actions\n\nApply LLM-provenance caveat footer per SOUL.md `llm-provenance-caveat`. Hyperlink every URL per `no-trailing-asteri[REDACTED_OPENAI_KEY]` and `pr-hyperlink` rules.\n\n### Phase 5.5: execute the install (don't post the list and stop)\n\n**Load-bearing rule, verified 2026-07-30.** When the recommended-combo or Next-actions section enumerates installable commands (`npx @opengsd\u002Fgsd-core@latest --claude --global`, `npx skills@latest add mattpocock\u002Fskills --skill=grill-me -y -g`, etc.) AND the user said anything like \"install them\", \"set it up\", \"go ahead\", \"ship it\", \"let's do X\" — **execute the install in the same turn**, do not post the list and wait. The user will read the install summary in the next reply, not a static plan.\n\nIf the user asked for analysis only (\"compare X and Y\", \"how do they differ\"), do not install — analysis-only is a valid request.\n\nIf the user gave a guarded install directive (\"install them all but don't add default guidance\"), execute the install but **honor the guard**:\n- Default-install flags that auto-enable hooks → downgrade to lean profile (GSD: `--profile=core` not `full`; grill-me keeps `disable-model-invocation: true`).\n- Default guidance files → don't touch (`SOUL.md`, `CLAUDE.md`, plugin enable flags).\n- Verify post-install what got auto-configured and call it out honestly in the next reply. Don't hide it.\n\n## Anti-patterns (load-bearing)\n\n1. **Don't recommend installing all global frameworks.** Superpowers' HARD-GATE will fight GSD's `\u002Fgsd:*` namespace and grill-me's `disable-model-invocation: true`. Pick one as the per-session default; bring others in explicitly per-phase.\n2. **Don't accept GSD's `--profile=full` default when the user said \"no default guidance.\"** Full installs ~15 always-on hooks to `settings.json` (verified v1.9.0). Use `--profile=core` (~700 tokens eager-load) instead. See `references\u002Fgsd-core.md` for the full hook table.\n3. **Don't duplicate state trees.** GSD → `.planning\u002F`. Superpowers → `docs\u002Fsuperpowers\u002F{specs,plans}\u002F`. grill-me → nothing or CONTEXT.md. Designate one artifact tree as authoritative.\n4. **Don't use a pure interview primitive (grill-me) inside an execution loop.** Grill-me is for upstream alignment only.\n5. **Don't recommend a framework whose canonical repo has moved without flagging the redirect.** Always verify the live repo.\n6. **Don't treat star counts as signal of correctness.** GSD's 48.3k stars ≠ better than Superpowers' smaller community. They solve different problems.\n7. **Don't claim a methodology is \"installed\" without probing the filesystem.** See `references\u002Finstallation-check.md`.\n8. **Don't create status-cron jobs that ping the user about a choice they're still making.** When the user says \"install X but don't add default guidance,\" a 20m cron pinging them about \"did you pick a combo?\" violates the directive. Wait for the user's own next message; don't schedule a nudge.\n\n## Support files\n\n- `references\u002Fmethodology-profile-template.md` — capture template for one methodology\n- `references\u002Fsuperpowers.md` — Superpowers profile (obra, installed v6.2.0)\n- `references\u002Fgsd-core.md` — GSD Core profile (TÂCHES, not installed)\n- `references\u002Fgrill-me.md` — grill-me profile (Matt Pocock, not installed)\n- `references\u002Fcomposition-patterns.md` — verified combinations with anti-patterns\n- `references\u002Finstallation-check.md` — how to verify local install status per methodology\n\n## How to extend this skill\n\nWhen a new methodology emerges:\n1. Verify the canonical source (live repo, official docs).\n2. Add `references\u002F\u003Cname>.md` profile using the template.\n3. Update `composition-patterns.md` if it composes with existing methodologies.\n4. Update the landscape table in this SKILL.md.\n\nWhen a methodology moves (e.g., `gsd-build\u002Fget-shit-done` → `open-gsd\u002Fgsd-core`):\n1. Update the profile's canonical source.\n2. Note the redirect history in the profile.\n3. Grep existing references for stale URLs.",{"name":5,"description":7},"main","05df7380981a2c4af868ce0fa57962ae0eea62a9","hermes\u002Fskills\u002Fsoftware-development\u002Fagentic-coding-methodology-composition",0,"https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills","https:\u002F\u002Fgithub.com\u002Fjleechanorg","2026-11-12 14:45:07",{"source":8,"skillName":5,"commands":63,"prompt":73,"zipAvailable":74},[64,67,70],{"tool":65,"command":66},"npx","npx skills add jleechanorg\u002Fjleechan-skills --skill agentic-coding-methodology-composition",{"tool":68,"command":69},"bunx","bunx skills add jleechanorg\u002Fjleechan-skills --skill agentic-coding-methodology-composition",{"tool":71,"command":72},"pnpm","pnpm dlx skills add jleechanorg\u002Fjleechan-skills --skill agentic-coding-methodology-composition","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002Fhermes\u002Fskills\u002Fsoftware-development\u002Fagentic-coding-methodology-composition\u002FSKILL.md",true,[76,82,86,90,94,98,102,106,110,114,118],{"path":77,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fadvanced_features.md","REFERENCE","参考文档",14984,"https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fpennylane\u002Freferences\u002Fadvanced_features.md",{"path":83,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Fcomposition-patterns.md",7111,"https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002Fhermes\u002Fskills\u002Fsoftware-development\u002Fagentic-coding-methodology-composition\u002Freferences\u002Fcomposition-patterns.md",{"path":87,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002Fdevices_backends.md",13079,"https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fpennylane\u002Freferences\u002Fdevices_backends.md",{"path":91,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":92,"sourceHtmlUrl":93},"references\u002Fgetting_started.md",5097,"https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fpennylane\u002Freferences\u002Fgetting_started.md",{"path":95,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":96,"sourceHtmlUrl":97},"references\u002Fgrill-me.md",4903,"https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002Fhermes\u002Fskills\u002Fsoftware-development\u002Fagentic-coding-methodology-composition\u002Freferences\u002Fgrill-me.md",{"path":99,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":100,"sourceHtmlUrl":101},"references\u002Finstallation-check.md",4308,"https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002Fhermes\u002Fskills\u002Fsoftware-development\u002Fagentic-coding-methodology-composition\u002Freferences\u002Finstallation-check.md",{"path":103,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":104,"sourceHtmlUrl":105},"references\u002Fmethodology-profile-template.md",1798,"https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002Fhermes\u002Fskills\u002Fsoftware-development\u002Fagentic-coding-methodology-composition\u002Freferences\u002Fmethodology-profile-template.md",{"path":107,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":108,"sourceHtmlUrl":109},"references\u002Foptimization.md",16696,"https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fpennylane\u002Freferences\u002Foptimization.md",{"path":111,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":112,"sourceHtmlUrl":113},"references\u002Fquantum_chemistry.md",14438,"https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fpennylane\u002Freferences\u002Fquantum_chemistry.md",{"path":115,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":116,"sourceHtmlUrl":117},"references\u002Fquantum_circuits.md",9395,"https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fpennylane\u002Freferences\u002Fquantum_circuits.md",{"path":119,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":120,"sourceHtmlUrl":121},"references\u002Fquantum_ml.md",14532,"https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fpennylane\u002Freferences\u002Fquantum_ml.md",[123,139,161,174,188,204],{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":50},"01M716Y5MTJ6GYJZ2ATXCJK8G4","instinct","Use when the user invokes \u002Finstinct or \u002Fin, or asks to \"message Instinct\", \"ask Instinct\", \"tell Instinct\", \"check Instinct\", or read replies from the configured peer assistant. iMessage first, WhatsApp Web as fallback.","https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Finstinct\u002FSKILL.md",[],[125,130,29,131,132,42,133,134,135,136,137,138],"user","replies","check","identity","whatsapp","gmail","read","message","ask",{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":150,"publishedAt":50},"01M716Y4HF7FVVMJSA2CCVN5VF","hr","Compatibility alias for history-resume; produce the same fresh-state, provenance-aware resume briefing.","https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fhr\u002FSKILL.md",[145],{"categoryNo":146,"categoryName":147,"taxonomyType":148,"taxonomyTypeDesc":149},"01JBSEEDCAT000000000000038","人力资源","PROFESSION","适用职业",[141,151,152,153,154,155,156,157,158,159,160],"resume","compatibility","provenance","for","history","produce","alias","briefing","state","fresh",{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":168,"publishedAt":50},"01M716Y1FFNFKFJYYKF8HQA6T8","history-resume","Resume briefing for the current repository branch or worktree using fresh state and admitted history sources.","https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fhistory-resume\u002FSKILL.md",[167],{"categoryNo":146,"categoryName":147,"taxonomyType":148,"taxonomyTypeDesc":149},[155,151,169,170,130,46,158,171,154,172,173,159,160],"history resume","branch","repository","worktree","sources",{"skillNo":175,"name":176,"nameZh":6,"description":177,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":178,"categories":179,"keywords":180,"publishedAt":50},"01M716XWXJ8EPHK4RH9T14TR85","grok","Alias for the canonical grokbot browser conversation workflow; \u002Fgrok talks to the Grok bot the same way \u002Fdot talks to Dot.","https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fgrok\u002FSKILL.md",[],[176,181,182,183,154,184,157,185,186,187],"dot","bot","workflow","canonical","conversation","browser","grokbot",{"skillNo":189,"name":190,"nameZh":6,"description":191,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":192,"categories":193,"keywords":194,"publishedAt":50},"01M70N9Q07DTE0EW5KFXMMMSJ0","codexa-bench","Compare `codexa` and normal `codex` on a fair split of comparable work by default; use `--strict` for duplicate runs of the exact same task.","https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcodexa-bench\u002FSKILL.md",[],[195,196,197,42,198,154,199,200,201,202,203],"codexa bench","work","split","default","duplicate","task","compare","normal","codex",{"skillNo":205,"name":206,"nameZh":6,"description":207,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":208,"licenseFileUrl":209,"sourceHtmlUrl":210,"categories":211,"keywords":221,"publishedAt":50},"01M6C24S2X60SP8BBFGAEKPEGW","frontend-design","Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML\u002FCSS layouts, or when styling\u002Fbeautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ffrontend-design\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ffrontend-design\u002FSKILL.md",[212,215,218],{"categoryNo":213,"categoryName":214,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":216,"categoryName":217,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":219,"categoryName":220,"taxonomyType":148,"taxonomyTypeDesc":149},"01JBSEEDCAT000000000000032","设计师",[222,223,224,42,225,226,227,130,228,229,230,231,232,233,234,235,236,237,238,239,240,241,242,243,244,245,29,246],"frontend","design","frontend design","generic","ui design","react","html","components","code","artifacts","ui","aesthetics","Production","web components","landing","applications","quality","web","css","create","examples","with","react components","web ui","pages"]