[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M730Y2PVWYQJ0AMC51F7YZGP":3,"skill-same:01M730Y2PVWYQJ0AMC51F7YZGP":85},{"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":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":32,"ownerHtmlUrl":33,"ownerBlogUrl":34,"ownerDescription":35,"updatedAt":36,"install":37,"resources":50},"01M730Y2PVWYQJ0AMC51F7YZGP","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).","Horonomos-laps\u002FYana-AI","Horonomos-laps","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F355299122?v=4","01M76B3QPXE88ET2SQPDPVATZT"," Horonomos-laps","01M72ZQRJPCYPSSWT4D00VJR2A",13,"MIT","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbrand-discovery\u002FSKILL.md",[],[],"2026-11-11 15:11:14",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).\norigin: affaan-m\u002FECC (MIT) — .agents\u002Fskills\u002Fbrand-discovery\u002FSKILL.md\nlicense: MIT\nversion: 1.0.0\nimported: 2026-06-19 — pinned commit 34faa39bd3cd496a0aece0245f2b7e38b7923abc\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,"origin":24,"license":15,"version":25,"imported":26,"description":7},"affaan-m\u002FECC (MIT) — .agents\u002Fskills\u002Fbrand-discovery\u002FSKILL.md","1.0.0","2026-06-19 — pinned commit 34faa39bd3cd496a0aece0245f2b7e38b7923abc","main","481dcd7dd2e288b9d627a2bd017db70e64e6c6fa",".claude\u002Fskills\u002Fbrand-discovery",2,"https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI","https:\u002F\u002Fyana.vutam.link\u002F","https:\u002F\u002Fgithub.com\u002FHoronomos-laps","https:\u002F\u002Fyana.vutam.link","An open-source governed runtime & execution environment for multi-agent AI systems.","2026-11-14 13:24:09",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add Horonomos-laps\u002FYana-AI --skill brand-discovery",{"tool":43,"command":44},"bunx","bunx skills add Horonomos-laps\u002FYana-AI --skill brand-discovery",{"tool":46,"command":47},"pnpm","pnpm dlx skills add Horonomos-laps\u002FYana-AI --skill brand-discovery","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbrand-discovery\u002FSKILL.md",true,[51,57,61,65,69,73,77,81],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002F10_purpose-why.md","REFERENCE","参考文档",1179,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbrand-discovery\u002Freferences\u002F10_purpose-why.md",{"path":58,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002F20_positioning.md",1481,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbrand-discovery\u002Freferences\u002F20_positioning.md",{"path":62,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002F30_audience-niche.md",1496,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbrand-discovery\u002Freferences\u002F30_audience-niche.md",{"path":66,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002F40_personality-archetype.md",1925,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbrand-discovery\u002Freferences\u002F40_personality-archetype.md",{"path":70,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002F50_voice-tone.md",1767,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbrand-discovery\u002Freferences\u002F50_voice-tone.md",{"path":74,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002F60_narrative-story.md",1560,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbrand-discovery\u002Freferences\u002F60_narrative-story.md",{"path":78,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002F70_founder-tension.md",1517,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbrand-discovery\u002Freferences\u002F70_founder-tension.md",{"path":82,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002F90_SYNTHESIS.md",3063,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbrand-discovery\u002Freferences\u002F90_SYNTHESIS.md",[86,93,101,109,117,125],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M735GKET5YVYKAY62W2P5YXB","openai--sentry--sentry","Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fopenai--sentry--sentry\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":97,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M73DCAP83T17HY7SMGK7MGFE","ito-basket-compare","Compare Itô prediction-market baskets against a user's knowledge base, portfolio notes, financial context, watchlist, or research thesis. Use for read-only basket comparison and gap analysis without investment advice or live trading.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fito-basket-compare\u002FSKILL.md",[],[],{"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":97,"licenseFileUrl":105,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":19},"01M734CYEMZFDR3KH6SW0JP8TD","implementing-network-traffic-baselining","Build network traffic baselines from NetFlow\u002FIPFIX data using Python pandas for statistical analysis, z-score anomaly detection, and hourly\u002Fdaily traffic pattern profiling","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":97,"licenseFileUrl":113,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":19},"01M73ASZ6NJRJM44Z2P84NGQ3Q","detecting-evasion-techniques-in-endpoint-logs","Detects defense evasion techniques used by adversaries in endpoint logs including log tampering, timestomping, process injection, and security tool disabling. Use when investigating suspicious endpoint behavior, building detection rules for evasion tactics, or conducting threat hunting for stealthy adversary activity. Activates for requests involving evasion detection, defense evasion analysis, log tampering detection, or MITRE ATT&CK TA0005.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FSKILL.md",[],[],{"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":97,"licenseFileUrl":121,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":19},"01M734AFNXD06Z78QRK0VKGT7Q","implementing-microsegmentation-with-guardicore","Implementing microsegmentation using Akamai Guardicore Segmentation to map application dependencies, create granular network policies, visualize east-west traffic flows, and enforce least-privilege communication between workloads across data centers and cloud.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FSKILL.md",[],[],{"skillNo":126,"name":127,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":97,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":19},"01M736TK27QMCXK0DVCH25SJN5","ramdisk-tmpfs-patterns","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Framdisk-tmpfs-patterns\u002FSKILL.md",[],[]]