[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F6JEXDT2XA5YAF83DRVCKX":3,"skill-same:01M7F6JEXDT2XA5YAF83DRVCKX":84},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7F6JEXDT2XA5YAF83DRVCKX","brand-discovery",null,"Use when a brand needs to discover or articulate its identity through structured multi-session interviews. Covers purpose, positioning, audience, personality, voice, narrative, and founder-brand tension across 8 modules using laddering, 5 Whys, and projective techniques. Produces a resumable session with disk-persisted state and a master brandbook (90_SYNTHESIS.md).","JUICEWRLD998\u002Fmyskills","JUICEWRLD998","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F112366831?v=4","01M7F6BY76NXJQY5JX1JQ0J9GA","BLVCK_NINJA","01M7F6BY8EBEVH8BX79AVB9B5T",0,"MIT","https:\u002F\u002Fgithub.com\u002FJUICEWRLD998\u002Fmyskills\u002Fblob\u002Fmain\u002Fplugins\u002Fecc__ecc\u002F.agents\u002Fskills\u002Fbrand-discovery\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: brand-discovery\ndescription: >-\n  Use when a brand needs to discover or articulate its identity through\n  structured multi-session interviews. Covers purpose, positioning, audience,\n  personality, voice, narrative, and founder-brand tension across 8 modules\n  using laddering, 5 Whys, and projective techniques. Produces a resumable\n  session with disk-persisted state and a master brandbook (90_SYNTHESIS.md).\nlicense: MIT\n---\n\n# Brand Discovery\n\nUse this skill to conduct a structured, adaptive brand identity interview.\nThe goal is a complete `90_SYNTHESIS.md` — a master brandbook the\norganization can use to brief designers, writers, and external\ncollaborators.\n\nThe interview runs across multiple sessions. Capture answers to disk as you\ngo so that no elicited knowledge is lost when a conversation ends, and so a\nlater session can resume from where the last one stopped.\n\n## When to Activate\n\n- A brand is being created, repositioned, or needs a written identity reference to brief collaborators.\n- Multiple sessions are expected — the conversation will span days or weeks.\n- Multiple founders or stakeholders need individual interviews before a reconciliation pass.\n- The user wants a structured, repeatable method rather than an ad-hoc chat.\n- Existing brand documentation is scattered, implicit, or founder-dependent and needs to be made explicit.\n\n## Session start protocol\n\nOn every activation, perform these steps **before** asking any interview\nquestion:\n\n1. **Check for prior progress.** Look for an existing set of module files\n   and a `state.json` checkpoint in the project's brand-identity directory.\n   If none exists, this is a fresh start — confirm the brand name,\n   participants, and where to save the brand-identity files, then begin at\n   the first module.\n2. **Read the current module file** if one is in progress, and scan its Raw\n   section for previously captured answers.\n3. **Report to the user** in two or three sentences: which module we are\n   in, its status, and what remains. Then ask: \"Continue here, or switch\n   module?\"\n\n## Interview discipline\n\nApply these rules throughout every module:\n\n1. **One question at a time.** Never present a list of questions.\n2. **After each answer:** short paraphrase → one deepening probe OR close\n   the thread if the topic is saturated. Never move on silently.\n3. **Laddering:** for every \"what\" answer, follow with \"Why does that\n   matter to you?\" until a core value surfaces (typically two to four\n   iterations).\n4. **5 Whys:** for beliefs or positioning claims — push until the root\n   reason, not the surface declaration, is on the table.\n5. **Detect thin answers:** if generic, jargon-heavy, or vague, ask for\n   one concrete example, a client story, or a number.\n6. **Projective techniques** (use once per module to break a plateau):\n   - \"If the brand were a person, how would they walk into a room?\"\n   - Brand obituary: \"If the organization closed in five years, what would\n     customers miss? What would you regret not having said?\"\n   - Competitive contrast: \"Name one peer you admire but would never want\n     to become. What specifically makes them the wrong model?\"\n7. **Saturation signal:** when two consecutive probes produce no new\n   information, summarise and close the module.\n8. **End of module:** write a structured module file with two sections:\n   - `## Raw` — verbatim quotes and examples.\n   - `## Synthesis` — your interpretation, three candidate formulations,\n     open questions, contradictions between participants.\n   Then update the `state.json` checkpoint (see State protocol below).\n\n## Module sequence\n\n| File | Label | Frameworks used |\n|------|-------|-----------------|\n| `10_purpose-why.md` | Purpose \u002F Why | Sinek Golden Circle, Lencioni |\n| `20_positioning.md` | Positioning | Dunford \"Obviously Awesome\", Moore template |\n| `30_audience-niche.md` | Audience & Niche | Baker \"Business of Expertise\", ICP |\n| `40_personality-archetype.md` | Personality & Archetype | Mark & Pearson 12 archetypes, J. Aaker 5 dims |\n| `50_voice-tone.md` | Voice & Tone | Brand voice guidelines |\n| `60_narrative-story.md` | Narrative \u002F Story | Neumeier trueline, brand story arc |\n| `70_founder-tension.md` | Founder Brands vs Studio Brand | Enns \"Win Without Pitching\" |\n| `90_SYNTHESIS.md` | Master Brandbook | Kapferer prism, Aaker brand system |\n\nComplete modules in order. Honour a user request to jump modules and note\nthe skip in `state.json`.\n\n## State write protocol\n\nAfter each module reaches saturation or done status, write two files:\n\n**Module file** at `modules\u002F{moduleFile}` — full Raw and Synthesis content.\n\n**`state.json`** — a lightweight checkpoint so a later session can resume.\nUpdate `completedModules`, `inProgressModule`, `nextModule`, `lastUpdated`.\nSchema:\n\n```json\n{\n  \"session\": \"{brand_name}-brand-{YYYY-MM}\",\n  \"outputPath\": \"{path_to_brand_identity_directory}\",\n  \"completedModules\": [],\n  \"inProgressModule\": \"10_purpose-why.md\",\n  \"nextModule\": \"20_positioning.md\",\n  \"participants\": [\"founder-A\"],\n  \"lastUpdated\": \"{ISO-8601}\"\n}\n```\n\nAfter writing, confirm: \"Module X saved. State updated. Next: Y.\"\n\n**Terminal module (90_SYNTHESIS.md):** when writing the final synthesis,\nset `inProgressModule` to `\"90_SYNTHESIS.md\"` and `nextModule` to `null`\nin `state.json`. After writing, set `completedModules` to include\n`\"90_SYNTHESIS.md\"`, then set `inProgressModule` to `null` — leaving it\npopulated would cause a future resumption to treat the completed brandbook\nas still in progress. Confirm: \"Brandbook complete. All modules saved.\"\n\n## Multi-founder mode\n\nWhen more than one founder participates, write each founder's answers to\n`founders\u002F{participant}.md` instead of the main module files. Validate the\n`participant` name before writing: accept only alphanumeric characters and\nhyphens (e.g. `founder-a`, `anna`); reject names containing path separators\n(`\u002F`, `\\`, `..`) or special characters. Validate `moduleFile` against the\nenumerated module sequence (10 through 90 only). Validate `outputPath` to\nensure it is an absolute path within the project directory — reject relative\npaths and paths that escape via `..` segments. After all founders complete a\nmodule, run a reconciliation pass: summarise convergences and divergences in\nthe module file, flag \"productive tensions\" for the group alignment workshop.\n\n## Anti-Patterns\n\n- **Starting without reading state first.** Every session must open by checking for existing module files and `state.json`. Skipping this loses all continuity from prior sessions.\n- **Asking multiple questions at once.** One question at a time is not optional — lists produce checklist answers, not real insight.\n- **Moving to Synthesis before saturation.** If the last two probes produced no new information, the module is done. If they did — it isn't.\n- **Skipping multi-founder reconciliation.** When multiple stakeholders are involved, individual interviews must complete before reconciliation. Discussing the brand collectively first introduces anchoring bias.\n- **Treating this as a one-shot session.** This skill is designed for multiple sessions. Rushing to `90_SYNTHESIS.md` in one conversation produces shallow output.\n\n## Related Skills\n\n- `competitive-platform-analysis` — after brand-discovery establishes the positioning brief, use this to scope and categorise the competitor set.\n- `brand-voice` (ECC) — if the brand-discovery voice-and-tone module needs a separate, source-derived writing-style profile.\n","# Brand Discovery\n\nUse this skill to conduct a structured, adaptive brand identity interview.\nThe goal is a complete `90_SYNTHESIS.md` — a master brandbook the\norganization can use to brief designers, writers, and external\ncollaborators.\n\nThe interview runs across multiple sessions. Capture answers to disk as you\ngo so that no elicited knowledge is lost when a conversation ends, and so a\nlater session can resume from where the last one stopped.\n\n## When to Activate\n\n- A brand is being created, repositioned, or needs a written identity reference to brief collaborators.\n- Multiple sessions are expected — the conversation will span days or weeks.\n- Multiple founders or stakeholders need individual interviews before a reconciliation pass.\n- The user wants a structured, repeatable method rather than an ad-hoc chat.\n- Existing brand documentation is scattered, implicit, or founder-dependent and needs to be made explicit.\n\n## Session start protocol\n\nOn every activation, perform these steps **before** asking any interview\nquestion:\n\n1. **Check for prior progress.** Look for an existing set of module files\n   and a `state.json` checkpoint in the project's brand-identity directory.\n   If none exists, this is a fresh start — confirm the brand name,\n   participants, and where to save the brand-identity files, then begin at\n   the first module.\n2. **Read the current module file** if one is in progress, and scan its Raw\n   section for previously captured answers.\n3. **Report to the user** in two or three sentences: which module we are\n   in, its status, and what remains. Then ask: \"Continue here, or switch\n   module?\"\n\n## Interview discipline\n\nApply these rules throughout every module:\n\n1. **One question at a time.** Never present a list of questions.\n2. **After each answer:** short paraphrase → one deepening probe OR close\n   the thread if the topic is saturated. Never move on silently.\n3. **Laddering:** for every \"what\" answer, follow with \"Why does that\n   matter to you?\" until a core value surfaces (typically two to four\n   iterations).\n4. **5 Whys:** for beliefs or positioning claims — push until the root\n   reason, not the surface declaration, is on the table.\n5. **Detect thin answers:** if generic, jargon-heavy, or vague, ask for\n   one concrete example, a client story, or a number.\n6. **Projective techniques** (use once per module to break a plateau):\n   - \"If the brand were a person, how would they walk into a room?\"\n   - Brand obituary: \"If the organization closed in five years, what would\n     customers miss? What would you regret not having said?\"\n   - Competitive contrast: \"Name one peer you admire but would never want\n     to become. What specifically makes them the wrong model?\"\n7. **Saturation signal:** when two consecutive probes produce no new\n   information, summarise and close the module.\n8. **End of module:** write a structured module file with two sections:\n   - `## Raw` — verbatim quotes and examples.\n   - `## Synthesis` — your interpretation, three candidate formulations,\n     open questions, contradictions between participants.\n   Then update the `state.json` checkpoint (see State protocol below).\n\n## Module sequence\n\n| File | Label | Frameworks used |\n|------|-------|-----------------|\n| `10_purpose-why.md` | Purpose \u002F Why | Sinek Golden Circle, Lencioni |\n| `20_positioning.md` | Positioning | Dunford \"Obviously Awesome\", Moore template |\n| `30_audience-niche.md` | Audience & Niche | Baker \"Business of Expertise\", ICP |\n| `40_personality-archetype.md` | Personality & Archetype | Mark & Pearson 12 archetypes, J. Aaker 5 dims |\n| `50_voice-tone.md` | Voice & Tone | Brand voice guidelines |\n| `60_narrative-story.md` | Narrative \u002F Story | Neumeier trueline, brand story arc |\n| `70_founder-tension.md` | Founder Brands vs Studio Brand | Enns \"Win Without Pitching\" |\n| `90_SYNTHESIS.md` | Master Brandbook | Kapferer prism, Aaker brand system |\n\nComplete modules in order. Honour a user request to jump modules and note\nthe skip in `state.json`.\n\n## State write protocol\n\nAfter each module reaches saturation or done status, write two files:\n\n**Module file** at `modules\u002F{moduleFile}` — full Raw and Synthesis content.\n\n**`state.json`** — a lightweight checkpoint so a later session can resume.\nUpdate `completedModules`, `inProgressModule`, `nextModule`, `lastUpdated`.\nSchema:\n\n```json\n{\n  \"session\": \"{brand_name}-brand-{YYYY-MM}\",\n  \"outputPath\": \"{path_to_brand_identity_directory}\",\n  \"completedModules\": [],\n  \"inProgressModule\": \"10_purpose-why.md\",\n  \"nextModule\": \"20_positioning.md\",\n  \"participants\": [\"founder-A\"],\n  \"lastUpdated\": \"{ISO-8601}\"\n}\n```\n\nAfter writing, confirm: \"Module X saved. State updated. Next: Y.\"\n\n**Terminal module (90_SYNTHESIS.md):** when writing the final synthesis,\nset `inProgressModule` to `\"90_SYNTHESIS.md\"` and `nextModule` to `null`\nin `state.json`. After writing, set `completedModules` to include\n`\"90_SYNTHESIS.md\"`, then set `inProgressModule` to `null` — leaving it\npopulated would cause a future resumption to treat the completed brandbook\nas still in progress. Confirm: \"Brandbook complete. All modules saved.\"\n\n## Multi-founder mode\n\nWhen more than one founder participates, write each founder's answers to\n`founders\u002F{participant}.md` instead of the main module files. Validate the\n`participant` name before writing: accept only alphanumeric characters and\nhyphens (e.g. `founder-a`, `anna`); reject names containing path separators\n(`\u002F`, `\\`, `..`) or special characters. Validate `moduleFile` against the\nenumerated module sequence (10 through 90 only). Validate `outputPath` to\nensure it is an absolute path within the project directory — reject relative\npaths and paths that escape via `..` segments. After all founders complete a\nmodule, run a reconciliation pass: summarise convergences and divergences in\nthe module file, flag \"productive tensions\" for the group alignment workshop.\n\n## Anti-Patterns\n\n- **Starting without reading state first.** Every session must open by checking for existing module files and `state.json`. Skipping this loses all continuity from prior sessions.\n- **Asking multiple questions at once.** One question at a time is not optional — lists produce checklist answers, not real insight.\n- **Moving to Synthesis before saturation.** If the last two probes produced no new information, the module is done. If they did — it isn't.\n- **Skipping multi-founder reconciliation.** When multiple stakeholders are involved, individual interviews must complete before reconciliation. Discussing the brand collectively first introduces anchoring bias.\n- **Treating this as a one-shot session.** This skill is designed for multiple sessions. Rushing to `90_SYNTHESIS.md` in one conversation produces shallow output.\n\n## Related Skills\n\n- `competitive-platform-analysis` — after brand-discovery establishes the positioning brief, use this to scope and categorise the competitor set.\n- `brand-voice` (ECC) — if the brand-discovery voice-and-tone module needs a separate, source-derived writing-style profile.\n",{"name":5,"license":15,"description":7},"main","e4b5c5ed00b1419bd769ad56a0621e872609ac23","plugins\u002Fecc__ecc\u002F.agents\u002Fskills\u002Fbrand-discovery","https:\u002F\u002Fgithub.com\u002FJUICEWRLD998\u002Fmyskills","https:\u002F\u002Fgithub.com\u002FJUICEWRLD998","blvckninja.vercel.app","Full-stack Dev 💻|| Smart Contract Auditor||Blockchain Engineer||Road to mastery 🚀","2026-10-30 17:50:51",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add JUICEWRLD998\u002Fmyskills --skill brand-discovery",{"tool":38,"command":39},"bunx","bunx skills add JUICEWRLD998\u002Fmyskills --skill brand-discovery",{"tool":41,"command":42},"pnpm","pnpm dlx skills add JUICEWRLD998\u002Fmyskills --skill brand-discovery","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FJUICEWRLD998\u002Fmyskills\u002Fblob\u002Fmain\u002Fplugins\u002Fecc__ecc\u002F.agents\u002Fskills\u002Fbrand-discovery\u002FSKILL.md",true,[46,52,56,60,64,68,72,76,80],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"agents\u002Fopenai.yaml","REFERENCE","参考文档",271,"https:\u002F\u002Fgithub.com\u002FJUICEWRLD998\u002Fmyskills\u002Fblob\u002Fmain\u002Fplugins\u002Fecc__ecc\u002F.agents\u002Fskills\u002Fbrand-discovery\u002Fagents\u002Fopenai.yaml",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002F10_purpose-why.md",1179,"https:\u002F\u002Fgithub.com\u002FJUICEWRLD998\u002Fmyskills\u002Fblob\u002Fmain\u002Fplugins\u002Fecc__ecc\u002F.agents\u002Fskills\u002Fbrand-discovery\u002Freferences\u002F10_purpose-why.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002F20_positioning.md",1481,"https:\u002F\u002Fgithub.com\u002FJUICEWRLD998\u002Fmyskills\u002Fblob\u002Fmain\u002Fplugins\u002Fecc__ecc\u002F.agents\u002Fskills\u002Fbrand-discovery\u002Freferences\u002F20_positioning.md",{"path":61,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002F30_audience-niche.md",1496,"https:\u002F\u002Fgithub.com\u002FJUICEWRLD998\u002Fmyskills\u002Fblob\u002Fmain\u002Fplugins\u002Fecc__ecc\u002F.agents\u002Fskills\u002Fbrand-discovery\u002Freferences\u002F30_audience-niche.md",{"path":65,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002F40_personality-archetype.md",1925,"https:\u002F\u002Fgithub.com\u002FJUICEWRLD998\u002Fmyskills\u002Fblob\u002Fmain\u002Fplugins\u002Fecc__ecc\u002F.agents\u002Fskills\u002Fbrand-discovery\u002Freferences\u002F40_personality-archetype.md",{"path":69,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002F50_voice-tone.md",1767,"https:\u002F\u002Fgithub.com\u002FJUICEWRLD998\u002Fmyskills\u002Fblob\u002Fmain\u002Fplugins\u002Fecc__ecc\u002F.agents\u002Fskills\u002Fbrand-discovery\u002Freferences\u002F50_voice-tone.md",{"path":73,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002F60_narrative-story.md",1560,"https:\u002F\u002Fgithub.com\u002FJUICEWRLD998\u002Fmyskills\u002Fblob\u002Fmain\u002Fplugins\u002Fecc__ecc\u002F.agents\u002Fskills\u002Fbrand-discovery\u002Freferences\u002F60_narrative-story.md",{"path":77,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002F70_founder-tension.md",1517,"https:\u002F\u002Fgithub.com\u002FJUICEWRLD998\u002Fmyskills\u002Fblob\u002Fmain\u002Fplugins\u002Fecc__ecc\u002F.agents\u002Fskills\u002Fbrand-discovery\u002Freferences\u002F70_founder-tension.md",{"path":81,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002F90_SYNTHESIS.md",3063,"https:\u002F\u002Fgithub.com\u002FJUICEWRLD998\u002Fmyskills\u002Fblob\u002Fmain\u002Fplugins\u002Fecc__ecc\u002F.agents\u002Fskills\u002Fbrand-discovery\u002Freferences\u002F90_SYNTHESIS.md",[85,92,99,106,115,123],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7FBFRSSQYQZNR9JDBF5KS4Q","web-pentest","Authorized web pentest: recon, proof-based exploits, report.","https:\u002F\u002Fgithub.com\u002FJUICEWRLD998\u002Fmyskills\u002Fblob\u002Fmain\u002Fskills\u002Fweb-pentest\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M7FBEWDAAP23Z2VAAG3N6BXZ","test-driven-development","TDD: enforce RED-GREEN-REFACTOR, tests before code.","https:\u002F\u002Fgithub.com\u002FJUICEWRLD998\u002Fmyskills\u002Fblob\u002Fmain\u002Fskills\u002Ftest-driven-development\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":19},"01M7FBENYKD6ZK0R73SVEZ0RVK","systematic-debugging","4-phase root cause debugging: understand bugs before fixing.","https:\u002F\u002Fgithub.com\u002FJUICEWRLD998\u002Fmyskills\u002Fblob\u002Fmain\u002Fskills\u002Fsystematic-debugging\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":110,"licenseFileUrl":111,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":19},"01M7FBE16336DACSKJ88EVNQV2","skill-creator","Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FJUICEWRLD998\u002Fmyskills\u002Fblob\u002Fmain\u002Fskills\u002Fsynced\u002F2afcd8ab-ba1f-4bc7-97aa-30e65b87f9ec_e979b332-d9cd-418f-b1bb-ef8141c48880\u002Fskill-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FJUICEWRLD998\u002Fmyskills\u002Fblob\u002Fmain\u002Fskills\u002Fsynced\u002F2afcd8ab-ba1f-4bc7-97aa-30e65b87f9ec_e979b332-d9cd-418f-b1bb-ef8141c48880\u002Fskill-creator\u002FSKILL.md",[],[],{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":110,"licenseFileUrl":119,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":19},"01M7FBCTE262XYW1MF4AXS7W4T","learn","Use this skill when the user wants intellectual understanding — learning how or why something works, not getting a task done or soliciting Claude's judgment.\n\nTrigger for:\n- Explicit learning requests: teach, explain, ELI5, walk me through, quiz me, flashcards, \"I'm rusty on\"; definitions (\"what is X\")\n- Terse concept names implying \"help me understand this\": \"Galois theory,\" \"transformers, from scratch\"\n- Confusion signals: \"won't stick,\" \"keep mixing these up,\" \"not getting it\"\n- Learning-path questions: prerequisites, sequencing, what to study before X\n- Conceptual questions about mechanisms, causes, or dynamics\n\nDon't trigger for:\n- Tasks: coding, writing, calculation, translation, factual lookup, news updates\n- Personal troubleshooting; resource\u002Ftextbook recommendations\n- Claude's evaluative verdict: opinion prompts (\"do you think X\", \"settle this\", \"honest take\", \"is X dead \u002F still taken seriously\") and interpretive takes (\"was X really as harsh as people say\")","https:\u002F\u002Fgithub.com\u002FJUICEWRLD998\u002Fmyskills\u002Fblob\u002Fmain\u002Fskills\u002Fsynced\u002F2afcd8ab-ba1f-4bc7-97aa-30e65b87f9ec_e979b332-d9cd-418f-b1bb-ef8141c48880\u002Flearn\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FJUICEWRLD998\u002Fmyskills\u002Fblob\u002Fmain\u002Fskills\u002Fsynced\u002F2afcd8ab-ba1f-4bc7-97aa-30e65b87f9ec_e979b332-d9cd-418f-b1bb-ef8141c48880\u002Flearn\u002FSKILL.md",[],[],{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":19},"01M7FB94QHCE1GV8VA8V0TGQAX","plan","Write a markdown plan to .hermes\u002Fplans\u002F; no execution.","https:\u002F\u002Fgithub.com\u002FJUICEWRLD998\u002Fmyskills\u002Fblob\u002Fmain\u002Fskills\u002Fplan\u002FSKILL.md",[],[]]