[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6P6EBKC603PA9N56322FF16":3,"skill-same:01M6P6EBKC603PA9N56322FF16":97},{"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":26,"publishedAt":47,"linkOnly":48,"markdownContent":49,"markdownBody":50,"frontMatter":51,"refName":76,"commitSha":77,"skillDirectory":78,"forksCount":79,"repositoryHtmlUrl":80,"repositoryHomepageUrl":6,"ownerHtmlUrl":81,"ownerBlogUrl":82,"ownerDescription":6,"updatedAt":83,"install":84,"resources":96},"01M6P6EBKC603PA9N56322FF16","seed-extraction",null,"Produces a seed file — a YAML-fronted markdown document capturing a reusable pattern with trigger, evidence, and application steps — from a conversation or project experience. Use when: 'extract the learnings', 'turn this into a seed', 'what can we learn from this', 'capture this insight', 'document this pattern'.","DojoGenesis\u002Fgateway","DojoGenesis","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F273886418?v=4","01M6P54RXMD3TZ2082Z3Z4JMQP","Cruz Morales (TresPies)","01M6P54S269YR0ZZZ96WGQM439",2,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FDojoGenesis\u002Fgateway\u002Fblob\u002Fmain\u002Fplugins\u002Fwisdom-garden\u002Fskills\u002Fseed-extraction\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000002","文档处理","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46],"extraction","seed extraction","seed","file","learn","true","opus","STRING","trigger","project","wisdom","pattern","markdown","learnings","conversation","document","reusable","evidence","use","system","2026-11-10 10:12:30",false,"---\nname: seed-extraction\nmodel: opus\ndescription: \"Produces a seed file — a YAML-fronted markdown document capturing a reusable pattern with trigger, evidence, and application steps — from a conversation or project experience. Use when: 'extract the learnings', 'turn this into a seed', 'what can we learn from this', 'capture this insight', 'document this pattern'.\"\ncategory: wisdom-garden\ntriggers:\n  - \"extract the learnings\"\n  - \"turn this into a seed\"\n  - \"what can we learn from this\"\n  - \"capture this insight\"\n  - \"document this pattern\"\ntier: 1\nagents:\n  - \"primary\"\ntool_dependencies:\n  - \"file_system\"\n\ninputs:\n  - name: experience\n    type: string\n    description: Description of the conversation, project, or experience to extract a reusable pattern from\n    required: true\noutputs:\n  - name: seed_file\n    type: ref\n    format: cas-ref\n    description: Seed file capturing a reusable pattern with trigger, evidence, and application steps\n---\n\n# Seed Reflector Skill\n\n**Version:** 1.0  \n**Created:** 2026-02-02  \n**Author:** Manus  \n**Purpose:** Extract, document, and apply reusable \"seeds\" (patterns, insights, principles) from experiences\n\n---\n\n## Overview\n\nThis skill encodes the practice of **seed extraction and reflection** — identifying reusable patterns from experiences and documenting them in a way that makes them easy to apply in future contexts.\n\n**Philosophy:** Every experience contains seeds. The practice is learning to see them, extract them, and plant them where they'll grow.\n\n---\n\n## When to Use This Skill\n\n- After completing a major project or release\n- When you notice a pattern emerging across multiple experiences\n- During memory maintenance (Tier A → Tier B compression)\n- When preparing to share knowledge with other agents\n- When you want to reflect on what you've learned\n\n---\n\n## What Is a \"Seed\"?\n\nA **seed** is a reusable pattern, insight, or principle that:\n\n1. **Emerged from experience** (not abstract theory)\n2. **Can be applied in future contexts** (not one-time specific)\n3. **Has a clear trigger** (you know when to use it)\n4. **Captures wisdom** (not just information)\n\n**Examples of Seeds:**\n- \"Three-Tiered Governance\" (from Dataiku research)\n- \"Harness Trace\" (traceability pattern)\n- \"Context Iceberg\" (hierarchical context management)\n- \"3-Month Rule\" (semantic compression heuristic)\n\n---\n\n## Seed Extraction Process\n\n### Step 1: Identify Candidate Patterns\n\n**Look for:**\n- Decisions that worked well (or didn't)\n- Patterns that emerged across multiple instances\n- Insights that changed how you think\n- Principles that guided successful outcomes\n- Tensions or tradeoffs you navigated\n\n**Questions to ask:**\n- What did I learn that I didn't know before?\n- What pattern did I notice repeating?\n- What decision framework did I use?\n- What would I do differently next time?\n- What would I tell someone else facing this situation?\n\n### Step 2: Test for Reusability\n\n**A good seed is:**\n- General enough to apply in multiple contexts\n- Specific enough to be actionable\n- Grounded in experience (not abstract)\n- Has a clear trigger (you know when to apply it)\n\n**A bad seed is:**\n- Too specific (\"Use Mermaid.js for diagrams in Dojo Genesis\")\n- Too vague (\"Be thoughtful\")\n- Not grounded (\"I think this might work\")\n- No trigger (\"Apply this... sometime?\")\n\n### Step 3: Document the Seed\n\nUse the seed template at [references\u002Fseed-template.md](references\u002Fseed-template.md).\n\n### Step 4: Test the Seed\n\n**Apply it in a new context:**\n- Does the trigger work? (Do you recognize when to use it?)\n- Is it actionable? (Can you actually apply it?)\n- Does it produce value? (Does it improve outcomes?)\n\n**If yes:** Keep and refine  \n**If no:** Revise or discard\n\n---\n\n## Seed Categories\n\n### 1. Architectural Seeds\n**Pattern:** Design decisions and system structures\n\n**Examples:**\n- Three-Tiered Governance\n- Harness Trace\n- Context Iceberg\n- Agent Connect (routing-first, not swarm-first)\n\n### 2. Process Seeds\n**Pattern:** Workflows and methodologies\n\n**Examples:**\n- Planning with Files\n- Backend-First, Chunked Development\n- Dual-Track Orchestration\n- Compression Cycle (every 3-7 days)\n\n### 3. Decision Seeds\n**Pattern:** Frameworks for making choices\n\n**Examples:**\n- 3-Month Rule (semantic compression)\n- Cost Guard (token budget management)\n- Safety Switch (feature flags and rollback)\n\n### 4. Wisdom Seeds\n**Pattern:** Principles and philosophies\n\n**Examples:**\n- Beginner's Mind\n- Knowing When to Shut Up\n- Honesty is Wisdom\n\n### 5. Technical Seeds\n**Pattern:** Implementation patterns and best practices\n\n**Examples:**\n- Surgical Context (memory_search → memory_get)\n- Graceful Degradation (resilience patterns)\n- Semantic Compression (content-based, not positional)\n\n---\n\n## Seed Application Workflow\n\n### 1. Recognize the Trigger\n\n**Ask:** Does this situation match a seed's trigger?\n\n**Check:**\n- Context matches seed's \"when to apply\"\n- Keywords or signals are present\n- Problem pattern is similar to seed's origin\n\n### 2. Retrieve the Seed\n\n**Methods:**\n- Search seed library by keyword\n- Browse category (architectural, process, decision, wisdom, technical)\n- Recall from memory (if seed is well-practiced)\n\n### 3. Apply the Seed\n\n**Follow:**\n- Read \"How to Apply\" steps\n- Adapt to current context\n- Check \"Cautions\" to avoid misapplication\n\n### 4. Reflect on Outcome\n\n**Document:**\n- Did the seed work? (Yes\u002FNo\u002FPartially)\n- What was the outcome?\n- What would you adjust?\n- Should the seed be refined?\n\n**Update:**\n- Increment usage count\n- Add new example (if successful)\n- Refine \"How to Apply\" (if needed)\n- Update success rate\n\n---\n\n## Quality Checklist\n\nBefore finalizing a seed, verify:\n\n### Clarity\n- [ ] Name is memorable and descriptive\n- [ ] Pattern is stated in one clear sentence\n- [ ] Origin is documented\n- [ ] Why it matters is explicit\n\n### Reusability\n- [ ] Trigger is specific and recognizable\n- [ ] \"How to Apply\" steps are actionable\n- [ ] Examples demonstrate the pattern\n- [ ] Related seeds are identified\n\n### Grounding\n- [ ] Emerged from real experience (not theory)\n- [ ] Evidence includes 3+ instances\n- [ ] Examples are concrete (not abstract)\n- [ ] Cautions address misapplication\n\n### Metadata\n- [ ] Created date is recorded\n- [ ] Usage count is tracked\n- [ ] Status is set (Active\u002FExperimental\u002FDeprecated)\n- [ ] Category is assigned\n\n---\n\n## Examples of Seeds\n\n### From Dojo Genesis\n\n**Seed: Three-Tiered Governance**\n- **Pattern:** Governance multiplies velocity by providing clear decision frameworks at strategic, tactical, and operational levels\n- **Trigger:** When building complex systems that need both flexibility and control\n- **Origin:** Dataiku research synthesis\n\n**Seed: 3-Month Rule**\n- **Pattern:** If it wouldn't matter in 3 months → compress or discard\n- **Trigger:** When compressing memory or deciding what to keep\n- **Origin:** Cipher's feedback on semantic compression\n\n---\n\n## Common Pitfalls to Avoid\n\n- **Hoarding Seeds:** Keeping every insight — curate ruthlessly\n- **Vague Patterns:** \"Be thoughtful\" — write \"Apply 3-month rule when compressing\"\n- **No Trigger:** Seed without context — include clear \"when to apply\"\n- **Not Testing:** Extract and forget — apply, reflect, refine\n- **Over-Abstracting:** Theory without grounding — use concrete examples from experience\n\n---\n\n## Output\n\n- A seed file saved to the project's `seeds\u002F` directory (or `memory\u002Fseeds\u002F` if no dedicated location exists)\n- File format: Markdown with YAML frontmatter (`seed_id`, `name`, `category`, `status`, `created`)\n- File name convention: `[category-prefix]_[short-name].md` (e.g., `03_context_iceberg.md`)\n\n---\n\n## Examples\n\n**Scenario 1:** User says \"turn this into a seed — always dry-run new scripts before committing\" → produces `process_dry_run_gate.md` with pattern, 2 trigger phrases, one concrete example from the session, and \"Cautions\" noting it does not apply to read-only scripts.\n\n**Scenario 2:** User says \"what can we learn from the three failed migrations?\" → reads session context, identifies the common root cause as a missing pre-flight validation step, and produces `decision_preflight_validation.md` with evidence from all three instances.\n\n---\n\n## Edge Cases\n\n- If the candidate pattern is too specific to one project (e.g., a config path), document it as a project note, not a seed — seeds must be transferable.\n- If the user provides fewer than 2 concrete instances, mark the seed as `status: experimental` until more evidence accumulates.\n- If a seed already exists in the library with the same core pattern, compare and merge rather than duplicating.\n\n---\n\n## Anti-Patterns\n\n- Writing a seed from a single anecdote without checking if it generalizes — check against at least 2 instances before promoting to `active`.\n- Creating a seed whose trigger phrase matches every situation — overly broad triggers make seeds useless for retrieval.\n\n---\n\n**Related Skills:**\n- `specification-writer` - Seeds inform architectural decisions\n- `memory-garden` - Seeds are extracted during memory compression\n- `workspace-navigation` - Seeds are stored in shared workspace for collaboration\n\n---\n\n**Last Updated:** 2026-02-02  \n**Maintained By:** Manus  \n**Status:** Active\n","# Seed Reflector Skill\n\n**Version:** 1.0  \n**Created:** 2026-02-02  \n**Author:** Manus  \n**Purpose:** Extract, document, and apply reusable \"seeds\" (patterns, insights, principles) from experiences\n\n---\n\n## Overview\n\nThis skill encodes the practice of **seed extraction and reflection** — identifying reusable patterns from experiences and documenting them in a way that makes them easy to apply in future contexts.\n\n**Philosophy:** Every experience contains seeds. The practice is learning to see them, extract them, and plant them where they'll grow.\n\n---\n\n## When to Use This Skill\n\n- After completing a major project or release\n- When you notice a pattern emerging across multiple experiences\n- During memory maintenance (Tier A → Tier B compression)\n- When preparing to share knowledge with other agents\n- When you want to reflect on what you've learned\n\n---\n\n## What Is a \"Seed\"?\n\nA **seed** is a reusable pattern, insight, or principle that:\n\n1. **Emerged from experience** (not abstract theory)\n2. **Can be applied in future contexts** (not one-time specific)\n3. **Has a clear trigger** (you know when to use it)\n4. **Captures wisdom** (not just information)\n\n**Examples of Seeds:**\n- \"Three-Tiered Governance\" (from Dataiku research)\n- \"Harness Trace\" (traceability pattern)\n- \"Context Iceberg\" (hierarchical context management)\n- \"3-Month Rule\" (semantic compression heuristic)\n\n---\n\n## Seed Extraction Process\n\n### Step 1: Identify Candidate Patterns\n\n**Look for:**\n- Decisions that worked well (or didn't)\n- Patterns that emerged across multiple instances\n- Insights that changed how you think\n- Principles that guided successful outcomes\n- Tensions or tradeoffs you navigated\n\n**Questions to ask:**\n- What did I learn that I didn't know before?\n- What pattern did I notice repeating?\n- What decision framework did I use?\n- What would I do differently next time?\n- What would I tell someone else facing this situation?\n\n### Step 2: Test for Reusability\n\n**A good seed is:**\n- General enough to apply in multiple contexts\n- Specific enough to be actionable\n- Grounded in experience (not abstract)\n- Has a clear trigger (you know when to apply it)\n\n**A bad seed is:**\n- Too specific (\"Use Mermaid.js for diagrams in Dojo Genesis\")\n- Too vague (\"Be thoughtful\")\n- Not grounded (\"I think this might work\")\n- No trigger (\"Apply this... sometime?\")\n\n### Step 3: Document the Seed\n\nUse the seed template at [references\u002Fseed-template.md](references\u002Fseed-template.md).\n\n### Step 4: Test the Seed\n\n**Apply it in a new context:**\n- Does the trigger work? (Do you recognize when to use it?)\n- Is it actionable? (Can you actually apply it?)\n- Does it produce value? (Does it improve outcomes?)\n\n**If yes:** Keep and refine  \n**If no:** Revise or discard\n\n---\n\n## Seed Categories\n\n### 1. Architectural Seeds\n**Pattern:** Design decisions and system structures\n\n**Examples:**\n- Three-Tiered Governance\n- Harness Trace\n- Context Iceberg\n- Agent Connect (routing-first, not swarm-first)\n\n### 2. Process Seeds\n**Pattern:** Workflows and methodologies\n\n**Examples:**\n- Planning with Files\n- Backend-First, Chunked Development\n- Dual-Track Orchestration\n- Compression Cycle (every 3-7 days)\n\n### 3. Decision Seeds\n**Pattern:** Frameworks for making choices\n\n**Examples:**\n- 3-Month Rule (semantic compression)\n- Cost Guard (token budget management)\n- Safety Switch (feature flags and rollback)\n\n### 4. Wisdom Seeds\n**Pattern:** Principles and philosophies\n\n**Examples:**\n- Beginner's Mind\n- Knowing When to Shut Up\n- Honesty is Wisdom\n\n### 5. Technical Seeds\n**Pattern:** Implementation patterns and best practices\n\n**Examples:**\n- Surgical Context (memory_search → memory_get)\n- Graceful Degradation (resilience patterns)\n- Semantic Compression (content-based, not positional)\n\n---\n\n## Seed Application Workflow\n\n### 1. Recognize the Trigger\n\n**Ask:** Does this situation match a seed's trigger?\n\n**Check:**\n- Context matches seed's \"when to apply\"\n- Keywords or signals are present\n- Problem pattern is similar to seed's origin\n\n### 2. Retrieve the Seed\n\n**Methods:**\n- Search seed library by keyword\n- Browse category (architectural, process, decision, wisdom, technical)\n- Recall from memory (if seed is well-practiced)\n\n### 3. Apply the Seed\n\n**Follow:**\n- Read \"How to Apply\" steps\n- Adapt to current context\n- Check \"Cautions\" to avoid misapplication\n\n### 4. Reflect on Outcome\n\n**Document:**\n- Did the seed work? (Yes\u002FNo\u002FPartially)\n- What was the outcome?\n- What would you adjust?\n- Should the seed be refined?\n\n**Update:**\n- Increment usage count\n- Add new example (if successful)\n- Refine \"How to Apply\" (if needed)\n- Update success rate\n\n---\n\n## Quality Checklist\n\nBefore finalizing a seed, verify:\n\n### Clarity\n- [ ] Name is memorable and descriptive\n- [ ] Pattern is stated in one clear sentence\n- [ ] Origin is documented\n- [ ] Why it matters is explicit\n\n### Reusability\n- [ ] Trigger is specific and recognizable\n- [ ] \"How to Apply\" steps are actionable\n- [ ] Examples demonstrate the pattern\n- [ ] Related seeds are identified\n\n### Grounding\n- [ ] Emerged from real experience (not theory)\n- [ ] Evidence includes 3+ instances\n- [ ] Examples are concrete (not abstract)\n- [ ] Cautions address misapplication\n\n### Metadata\n- [ ] Created date is recorded\n- [ ] Usage count is tracked\n- [ ] Status is set (Active\u002FExperimental\u002FDeprecated)\n- [ ] Category is assigned\n\n---\n\n## Examples of Seeds\n\n### From Dojo Genesis\n\n**Seed: Three-Tiered Governance**\n- **Pattern:** Governance multiplies velocity by providing clear decision frameworks at strategic, tactical, and operational levels\n- **Trigger:** When building complex systems that need both flexibility and control\n- **Origin:** Dataiku research synthesis\n\n**Seed: 3-Month Rule**\n- **Pattern:** If it wouldn't matter in 3 months → compress or discard\n- **Trigger:** When compressing memory or deciding what to keep\n- **Origin:** Cipher's feedback on semantic compression\n\n---\n\n## Common Pitfalls to Avoid\n\n- **Hoarding Seeds:** Keeping every insight — curate ruthlessly\n- **Vague Patterns:** \"Be thoughtful\" — write \"Apply 3-month rule when compressing\"\n- **No Trigger:** Seed without context — include clear \"when to apply\"\n- **Not Testing:** Extract and forget — apply, reflect, refine\n- **Over-Abstracting:** Theory without grounding — use concrete examples from experience\n\n---\n\n## Output\n\n- A seed file saved to the project's `seeds\u002F` directory (or `memory\u002Fseeds\u002F` if no dedicated location exists)\n- File format: Markdown with YAML frontmatter (`seed_id`, `name`, `category`, `status`, `created`)\n- File name convention: `[category-prefix]_[short-name].md` (e.g., `03_context_iceberg.md`)\n\n---\n\n## Examples\n\n**Scenario 1:** User says \"turn this into a seed — always dry-run new scripts before committing\" → produces `process_dry_run_gate.md` with pattern, 2 trigger phrases, one concrete example from the session, and \"Cautions\" noting it does not apply to read-only scripts.\n\n**Scenario 2:** User says \"what can we learn from the three failed migrations?\" → reads session context, identifies the common root cause as a missing pre-flight validation step, and produces `decision_preflight_validation.md` with evidence from all three instances.\n\n---\n\n## Edge Cases\n\n- If the candidate pattern is too specific to one project (e.g., a config path), document it as a project note, not a seed — seeds must be transferable.\n- If the user provides fewer than 2 concrete instances, mark the seed as `status: experimental` until more evidence accumulates.\n- If a seed already exists in the library with the same core pattern, compare and merge rather than duplicating.\n\n---\n\n## Anti-Patterns\n\n- Writing a seed from a single anecdote without checking if it generalizes — check against at least 2 instances before promoting to `active`.\n- Creating a seed whose trigger phrase matches every situation — overly broad triggers make seeds useless for retrieval.\n\n---\n\n**Related Skills:**\n- `specification-writer` - Seeds inform architectural decisions\n- `memory-garden` - Seeds are extracted during memory compression\n- `workspace-navigation` - Seeds are stored in shared workspace for collaboration\n\n---\n\n**Last Updated:** 2026-02-02  \n**Maintained By:** Manus  \n**Status:** Active\n",{"name":5,"tier":52,"model":33,"agents":53,"inputs":55,"outputs":61,"category":67,"triggers":68,"description":7,"tool_dependencies":74},1,[54],"primary",[56],{"name":57,"type":58,"required":59,"description":60},"experience","string",true,"Description of the conversation, project, or experience to extract a reusable pattern from",[62],{"name":63,"type":64,"format":65,"description":66},"seed_file","ref","cas-ref","Seed file capturing a reusable pattern with trigger, evidence, and application steps","wisdom-garden",[69,70,71,72,73],"extract the learnings","turn this into a seed","what can we learn from this","capture this insight","document this pattern",[75],"file_system","main","ff07df5fd8f75762c2a131e6e26d297e8ae403ee","plugins\u002Fwisdom-garden\u002Fskills\u002Fseed-extraction",0,"https:\u002F\u002Fgithub.com\u002FDojoGenesis\u002Fgateway","https:\u002F\u002Fgithub.com\u002FDojoGenesis","dojogenesis.com","2026-10-25 22:59:58",{"source":8,"skillName":5,"commands":85,"prompt":95,"zipAvailable":59},[86,89,92],{"tool":87,"command":88},"npx","npx skills add DojoGenesis\u002Fgateway --skill seed-extraction",{"tool":90,"command":91},"bunx","bunx skills add DojoGenesis\u002Fgateway --skill seed-extraction",{"tool":93,"command":94},"pnpm","pnpm dlx skills add DojoGenesis\u002Fgateway --skill seed-extraction","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FDojoGenesis\u002Fgateway\u002Fblob\u002Fmain\u002Fplugins\u002Fwisdom-garden\u002Fskills\u002Fseed-extraction\u002FSKILL.md",[],[98,117,128,136,176,198],{"skillNo":99,"name":100,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":106,"publishedAt":47},"01M6P6J0WYSD1MTGA3ZX6MGGZ5","kata-test-echo","https:\u002F\u002Fgithub.com\u002FDojoGenesis\u002Fgateway\u002Fblob\u002Fmain\u002Fserver\u002Ftestdata\u002Fkata\u002Fskills\u002Fkata-test-echo\u002FSKILL.md",[103],{"categoryNo":104,"categoryName":105,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",[107,108,109,110,111,112,113,114,115,116],"kata test echo","Echo","test","json","v1","output","input","structured","contracts","schema",{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":124,"publishedAt":47},"01M6P6HQJNGG4WPZW0DEWMAY2N","kata-plain","An ordinary prose skill; not dispatchable.","https:\u002F\u002Fgithub.com\u002FDojoGenesis\u002Fgateway\u002Fblob\u002Fmain\u002Fserver\u002Ftestdata\u002Fkata\u002Fskills\u002Fkata-plain\u002FSKILL.md",[123],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[125,126,127],"kata plain","prose skill","prose",{"skillNo":129,"name":130,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":47},"01M6P6HH6Y7K8K6606MF7VZ1HB","kata-broken","https:\u002F\u002Fgithub.com\u002FDojoGenesis\u002Fgateway\u002Fblob\u002Fmain\u002Fserver\u002Ftestdata\u002Fkata\u002Fskills\u002Fkata-broken\u002FSKILL.md",[],[134,135,114,115,108,116,110,109,113,111,112],"kata broken","broken",{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":156,"publishedAt":47},"01M6P6GW520QJ03A6K7Y5PWJ52","voice-before-structure","Read the project's design language and philosophy before writing structural artifacts. Ground manifests, READMEs, and descriptions in the project's voice, not boilerplate. Use when creating manifests or READMEs for established projects, writing ecosystem-level documentation, building plugin descriptions or marketplace metadata, or authoring metadata that carries a project's identity. Trigger phrases: 'write the manifest', 'create a README', 'describe this plugin', 'ground yourself in the philosophy', 'ecosystem-level work'.","https:\u002F\u002Fgithub.com\u002FDojoGenesis\u002Fgateway\u002Fblob\u002Fmain\u002Fplugins\u002Fwisdom-garden\u002Fskills\u002Fvoice-before-structure\u002FSKILL.md",[142,145,148,153],{"categoryNo":143,"categoryName":144,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":146,"categoryName":147,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":149,"categoryName":150,"taxonomyType":151,"taxonomyTypeDesc":152},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",{"categoryNo":154,"categoryName":155,"taxonomyType":151,"taxonomyTypeDesc":152},"01JBSEEDCAT000000000000036","内容创作者",[157,158,159,160,161,162,163,164,36,165,166,167,168,169,170,171,172,173,174,175],"voice before structure","structure","voice","manifests","ecosystem","false","authoring","structural","artifact","philosophy","design","writing","identity","documentation","create","projects","work","read","write",{"skillNo":177,"name":178,"nameZh":6,"description":179,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":180,"categories":181,"keywords":183,"publishedAt":47},"01M6P6GMNA4HJ4D5RRM3BQZ73M","system-prompt-archaeology","Produces a named ADA disposition preset (YAML) and a layered behavioral analysis (structural decomposition + evidence-cited classifications) from a system prompt. Use when: \"analyze this system prompt\", \"extract disposition from prompt\", \"reverse-engineer agent behavior\", \"what patterns does this prompt use\", \"build a preset from this prompt\".","https:\u002F\u002Fgithub.com\u002FDojoGenesis\u002Fgateway\u002Fblob\u002Fmain\u002Fplugins\u002Fwisdom-garden\u002Fskills\u002Fsystem-prompt-archaeology\u002FSKILL.md",[182],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[184,185,186,46,187,188,164,189,37,190,191,192,44,193,194,195,34,196,32,197],"system prompt archaeology","system prompt","prompt","behavioral","classify","decomposition","patterns","engineer","decompose","ada","analyze","analysis","sonnet","reverse",{"skillNo":199,"name":200,"nameZh":6,"description":201,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":202,"categories":203,"keywords":205,"publishedAt":47},"01M6P6G2D70T9R00HX6K154X5Y","session-lifecycle-automation","Designs and configures all three loops of solo-operator session automation — session bookends, background maintenance agents, and a delegation flywheel. Use when setting up a new workspace, recovering from the 44% zero-artifact session leak, or preparing to scale delegation across multiple concurrent agents.","https:\u002F\u002Fgithub.com\u002FDojoGenesis\u002Fgateway\u002Fblob\u002Fmain\u002Fplugins\u002Fwisdom-garden\u002Fskills\u002Fsession-lifecycle-automation\u002FSKILL.md",[204],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[206,207,208,209,210,39,211,212,213,214,215,216,217,165,218,219,220,221,222,223],"automation","session lifecycle automation","session lifecycle","lifecycle","session","configure","directory","config","delegation","audit","SET","files","solo","across","scheduled","loops","up","template"]