[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71P4770D5ZX48P38VMDNF48":3,"skill-same:01M71P4770D5ZX48P38VMDNF48":86},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":15,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":55,"repositoryHtmlUrl":56,"repositoryHomepageUrl":57,"ownerHtmlUrl":58,"ownerBlogUrl":59,"ownerDescription":6,"updatedAt":60,"install":61,"resources":74},"01M71P4770D5ZX48P38VMDNF48","stride-analysis-patterns",null,"Use when running a STRIDE threat modeling session to identify spoofing, tampering, repudiation, disclosure, DoS and privilege threats in a design. Includes a threat analysis matrix and templates for threat documentation. For mapping threats to controls see threat-mitigation-mapping.","monoes\u002Fmonomind","monoes","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F276744696?v=4","01M71KWF37AJ2NJBP3KWBVSDGT","01M71KWF4CSF8ADH0M6HA09VD2",23,"MIT","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fstride-analysis-patterns\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fstride-analysis-patterns\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"stride","stride analysis patterns","patterns","analysis","https","scanning","privilege","github","documentation","architecture","dos","query","when","use","controls","design","session","for","security-scanning","running","2026-11-10 10:56:23",false,"---\nname: stride-analysis-patterns\ndescription: \"Use when running a STRIDE threat modeling session to identify spoofing, tampering, repudiation, disclosure, DoS and privilege threats in a design. Includes a threat analysis matrix and templates for threat documentation. For mapping threats to controls see threat-mitigation-mapping.\"\ntags: [\"security\",\"architecture\",\"documentation\"]\ntools: [\"monograph_query\",\"monograph_context\"]\nlicense: MIT\nsource: https:\u002F\u002Fgithub.com\u002Fwshobson\u002Fagents\nsource_path: \"plugins\u002Fsecurity-scanning\u002Fskills\u002Fstride-analysis-patterns\"\nsource_commit: 4236bb91f8395b0435f1d8b8baf9e8e4c69a8620\n---\n# STRIDE Analysis Patterns\n\nSystematic threat identification using the STRIDE methodology.\n\n## When to Use This Skill\n\n- Starting new threat modeling sessions\n- Analyzing existing system architecture\n- Reviewing security design decisions\n- Creating threat documentation\n- Training teams on threat identification\n- Compliance and audit preparation\n\n## Core Concepts\n\n### 1. STRIDE Categories\n\n```\nS - Spoofing       → Authentication threats\nT - Tampering      → Integrity threats\nR - Repudiation    → Non-repudiation threats\nI - Information    → Confidentiality threats\n    Disclosure\nD - Denial of      → Availability threats\n    Service\nE - Elevation of   → Authorization threats\n    Privilege\n```\n\n### 2. Threat Analysis Matrix\n\n| Category            | Question                                  | Control Family |\n| ------------------- | ----------------------------------------- | -------------- |\n| **Spoofing**        | Can attacker pretend to be someone else?  | Authentication |\n| **Tampering**       | Can attacker modify data in transit\u002Frest? | Integrity      |\n| **Repudiation**     | Can attacker deny actions?                | Logging\u002FAudit  |\n| **Info Disclosure** | Can attacker access unauthorized data?    | Encryption     |\n| **DoS**             | Can attacker disrupt availability?        | Rate limiting  |\n| **Elevation**       | Can attacker gain higher privileges?      | Authorization  |\n\n## Templates and detailed worked examples\n\nFull template library lives in `references\u002Fdetails.md`. Read that file when you need concrete templates for this skill.\n\n## Best Practices\n\n### Do's\n\n- **Involve stakeholders** - Security, dev, and ops perspectives\n- **Be systematic** - Cover all STRIDE categories\n- **Prioritize realistically** - Focus on high-impact threats\n- **Update regularly** - Threat models are living documents\n- **Use visual aids** - DFDs help communication\n\n### Don'ts\n\n- **Don't skip categories** - Each reveals different threats\n- **Don't assume security** - Question every component\n- **Don't work in isolation** - Collaborative modeling is better\n- **Don't ignore low-probability** - High-impact threats matter\n- **Don't stop at identification** - Follow through with mitigations\n","# STRIDE Analysis Patterns\n\nSystematic threat identification using the STRIDE methodology.\n\n## When to Use This Skill\n\n- Starting new threat modeling sessions\n- Analyzing existing system architecture\n- Reviewing security design decisions\n- Creating threat documentation\n- Training teams on threat identification\n- Compliance and audit preparation\n\n## Core Concepts\n\n### 1. STRIDE Categories\n\n```\nS - Spoofing       → Authentication threats\nT - Tampering      → Integrity threats\nR - Repudiation    → Non-repudiation threats\nI - Information    → Confidentiality threats\n    Disclosure\nD - Denial of      → Availability threats\n    Service\nE - Elevation of   → Authorization threats\n    Privilege\n```\n\n### 2. Threat Analysis Matrix\n\n| Category            | Question                                  | Control Family |\n| ------------------- | ----------------------------------------- | -------------- |\n| **Spoofing**        | Can attacker pretend to be someone else?  | Authentication |\n| **Tampering**       | Can attacker modify data in transit\u002Frest? | Integrity      |\n| **Repudiation**     | Can attacker deny actions?                | Logging\u002FAudit  |\n| **Info Disclosure** | Can attacker access unauthorized data?    | Encryption     |\n| **DoS**             | Can attacker disrupt availability?        | Rate limiting  |\n| **Elevation**       | Can attacker gain higher privileges?      | Authorization  |\n\n## Templates and detailed worked examples\n\nFull template library lives in `references\u002Fdetails.md`. Read that file when you need concrete templates for this skill.\n\n## Best Practices\n\n### Do's\n\n- **Involve stakeholders** - Security, dev, and ops perspectives\n- **Be systematic** - Cover all STRIDE categories\n- **Prioritize realistically** - Focus on high-impact threats\n- **Update regularly** - Threat models are living documents\n- **Use visual aids** - DFDs help communication\n\n### Don'ts\n\n- **Don't skip categories** - Each reveals different threats\n- **Don't assume security** - Question every component\n- **Don't work in isolation** - Collaborative modeling is better\n- **Don't ignore low-probability** - High-impact threats matter\n- **Don't stop at identification** - Follow through with mitigations\n",{"name":5,"tags":44,"tools":46,"source":49,"license":14,"description":7,"source_path":50,"source_commit":51},[45,28,27],"security",[47,48],"monograph_query","monograph_context","https:\u002F\u002Fgithub.com\u002Fwshobson\u002Fagents","plugins\u002Fsecurity-scanning\u002Fskills\u002Fstride-analysis-patterns","4236bb91f8395b0435f1d8b8baf9e8e4c69a8620","main","f7cd4595d0f8959822163e14f9787117765c931a","packages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fstride-analysis-patterns",2,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind","https:\u002F\u002Fmonoes.github.io\u002Fmonomind\u002F","https:\u002F\u002Fgithub.com\u002Fmonoes","https:\u002F\u002Fmonoes.me","2026-11-10 01:53:48",{"source":8,"skillName":5,"commands":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add monoes\u002Fmonomind --skill stride-analysis-patterns",{"tool":67,"command":68},"bunx","bunx skills add monoes\u002Fmonomind --skill stride-analysis-patterns",{"tool":70,"command":71},"pnpm","pnpm dlx skills add monoes\u002Fmonomind --skill stride-analysis-patterns","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fstride-analysis-patterns\u002FSKILL.md",true,[75,80],{"path":76,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":15},"LICENSE.txt","LICENSE","许可证",1068,{"path":81,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Fdetails.md","REFERENCE","参考文档",18499,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fstride-analysis-patterns\u002Freferences\u002Fdetails.md",[87,113,148,174,196,223],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":91,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":112},"01M71PB3SHWKMNJM6MD65VX8D6","zk-steward","Org role guidance for a ZK steward: engineer zero-knowledge proof systems with circuit design, SNARK vs STARK choice and security review. This is zero-knowledge cryptography, not Zettelkasten note-taking.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fzk-steward\u002FSKILL.md",[],[95,96,97,98,99,100,34,101,102,30,103,104,105,106,107,108,109,45,110,111],"zk","zk steward","steward","zero-knowledge","engineer","choice","knowledge","impact","snark","review","monomind","security review","stark","zettelkasten","cryptography","org","blockchain","2026-11-10 13:02:02",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":117,"sourceHtmlUrl":118,"categories":119,"keywords":130,"publishedAt":112},"01M71PB18SDG28WBKPKJNB814K","writing-plans","Use when you have a spec or requirements for a multi-step coding task and must write an implementation plan before touching code. Produces bite-sized TDD tasks with exact file paths, code and commands for an engineer with zero context.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwriting-plans\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwriting-plans\u002FSKILL.md",[120,125],{"categoryNo":121,"categoryName":122,"taxonomyType":123,"taxonomyTypeDesc":124},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":126,"categoryName":127,"taxonomyType":128,"taxonomyTypeDesc":129},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[131,132,133,99,134,135,31,136,30,137,138,139,140,141,142,143,144,145,146,147],"writing","writing plans","plans","superpowers","implementation plan","you","code","tasks","plan","product","write","commands","paths","suggest","coding","context","ZeRO",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":91,"licenseFileUrl":152,"sourceHtmlUrl":153,"categories":154,"keywords":158,"publishedAt":112},"01M71PAXFM488X9ARXK0T04TF5","write-spec","Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-spec\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-spec\u002FSKILL.md",[155],{"categoryNo":156,"categoryName":157,"taxonomyType":128,"taxonomyTypeDesc":129},"01JBSEEDCAT000000000000031","产品经理",[141,159,160,161,162,101,163,31,164,165,166,140,167,168,169,170,171,172,32,173],"write spec","spec","user request","problem","acceptance","ask","vague","work","request","scoping","idea","metrics","feature","problem statement","document",{"skillNo":175,"name":176,"nameZh":6,"description":177,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":91,"licenseFileUrl":178,"sourceHtmlUrl":179,"categories":180,"keywords":184,"publishedAt":112},"01M71PASSZY800C0RPEARBS918","write-query","Write optimized SQL for your dialect with best practices. Use when translating a natural-language data need into SQL, building a multi-CTE query with joins and aggregations, optimizing a query against a large partitioned table, or getting dialect-specific syntax for Snowflake, BigQuery, Postgres, etc.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-query\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-query\u002FSKILL.md",[181],{"categoryNo":182,"categoryName":183,"taxonomyType":128,"taxonomyTypeDesc":129},"01JBSEEDCAT000000000000033","数据分析师",[30,141,185,186,36,187,101,32,31,188,189,190,191,166,26,192,23,193,194,195],"write query","postgres","snowflake","best practices","natural-language","with","multi","sql","syntax","plugins","data",{"skillNo":197,"name":198,"nameZh":6,"description":199,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":91,"licenseFileUrl":6,"sourceHtmlUrl":200,"categories":201,"keywords":208,"publishedAt":112},"01M71PAPTX0T3PF6ETFVR96SJJ","workflow-automation","Org role guidance for workflow automation: build and maintain CI\u002FCD definitions in GitHub Actions or equivalent: triggers, jobs, matrices, caching. Covers path filters, dependency caching, parallel jobs, timeouts and fail-fast ordering.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-automation\u002FSKILL.md",[202,205],{"categoryNo":203,"categoryName":204,"taxonomyType":123,"taxonomyTypeDesc":124},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":206,"categoryName":207,"taxonomyType":123,"taxonomyTypeDesc":124},"01JBSEEDCAT000000000000023","Skill与智能体开发",[209,210,211,212,36,213,214,215,216,102,217,218,219,30,105,26,220,221,222,23],"Workflow Automation","automation","workflow","parallel","actions","ci","triggers","github actions","maintain","filters","caching","build","dependency","devops",{"skillNo":224,"name":225,"nameZh":6,"description":226,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":91,"licenseFileUrl":6,"sourceHtmlUrl":227,"categories":228,"keywords":230,"publishedAt":112},"01M71PAM19Z1XTV9NPCFSE2MY8","workflow-architect","Org role guidance for a workflow architect: map full workflow trees for systems, user journeys and agents, covering every branch and failure. Covers discovering workflows from code, handoff contracts, timeouts, recovery paths and observable state.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-architect\u002FSKILL.md",[229],{"categoryNo":206,"categoryName":207,"taxonomyType":123,"taxonomyTypeDesc":124},[211,231,232,233,234,235,236,36,237,238,137,28,239,240,105,26,241,242,23,243],"workflow architect","architect","trees","user journeys","branch","planning","map","workflows","state","leadership","recovery","operations","systems"]