[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75Q4J2XVBJB8SX5G88PRXDD":3,"skill-same:01M75Q4J2XVBJB8SX5G88PRXDD":67},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":6,"ownerHtmlUrl":27,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":28,"install":29,"resources":42},"01M75Q4J2XVBJB8SX5G88PRXDD","senior-security",null,"Use when the user asks for STRIDE threat modeling, DREAD risk scoring, data-flow-diagram threat analysis, or a quick secret scan — or when a security request needs routing to the right specialist skill (pen-testing, incident response, cloud posture, red team, AI security, threat hunting, secure code review). This skill owns threat modeling; everything else routes to a sibling.","TehutiRaEl\u002FTHEHIVE","TehutiRaEl","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F267495122?v=4","01M75N1QQQHT359S3XMYK7NPCB","01M75N1QRAW5P8P43HEHWMXCTE",0,"MIT","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fengineering-team\u002Fskills\u002Fsenior-security\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: \"senior-security\"\ndescription: Use when the user asks for STRIDE threat modeling, DREAD risk scoring, data-flow-diagram threat analysis, or a quick secret scan — or when a security request needs routing to the right specialist skill (pen-testing, incident response, cloud posture, red team, AI security, threat hunting, secure code review). This skill owns threat modeling; everything else routes to a sibling.\n---\n\n# Senior Security Engineer — Threat Modeling + Security Router\n\nThis skill does exactly one job itself — **STRIDE\u002FDREAD threat modeling** (plus a quick secret scan) — and routes every other security request to the specialist skill that owns that lane. Do not duplicate sibling content here; route instead.\n\n## Routing Table (read this first)\n\n| The user wants... | Route to | Why that skill owns it |\n|---|---|---|\n| Vulnerability assessment, pen-test methodology, OWASP Top 10 testing | `..\u002Fsecurity-pen-testing\u002F` | Ships `vulnerability_scanner.py` + `dependency_auditor.py` with exit-code contracts |\n| Incident triage, SEV classification, forensics, containment | `..\u002Fincident-response\u002F` | SEV1–SEV4 taxonomy, NIST SP 800-61 phases, `incident_triage.py` |\n| Production outage command (non-security incidents) | `..\u002Fincident-commander\u002F` | Severity classifier + timeline + postmortem tools |\n| Security monitoring, CVE triage SLAs, compliance checks (SOC 2 etc.), security headers | `..\u002Fsenior-secops\u002F` | `security_scanner.py` + `compliance_checker.py`, CVE SLA table |\n| Hostile\u002Fadversarial code review | `..\u002Fadversarial-reviewer\u002F` | 3-persona review with BLOCK\u002FCONCERNS\u002FCLEAN verdict |\n| Secure code review as part of general review | `..\u002Fcode-reviewer\u002F` | Language dispatch + regression fixtures |\n| Cloud IAM escalation paths, S3 exposure, security groups | `..\u002Fcloud-security\u002F` | `cloud_posture_check.py` with per-check exit codes |\n| Threat hunting, IOC sweeps, anomaly detection | `..\u002Fthreat-detection\u002F` | z-score anomaly + IOC staleness tooling |\n| Red-team engagement planning, ATT&CK kill chains | `..\u002Fred-team\u002F` | `engagement_planner.py` with authorization gate |\n| LLM\u002FAI attack surface (prompt injection, poisoning) | `..\u002Fai-security\u002F` | ATLAS-mapped `ai_threat_scanner.py` |\n\nIf the request spans lanes (e.g., \"secure this new architecture\"), do the threat model here first — its output (prioritized threats + mitigations) tells you which siblings to load next. Never bulk-load multiple security skills speculatively.\n\n## What This Skill Owns: STRIDE Threat Modeling\n\n### Workflow\n\n1. **Scope:** assets to protect, trust boundaries, data flows (external entities, processes, data stores, flows).\n2. **Generate the threat model** per component:\n   ```bash\n   python3 scripts\u002Fthreat_modeler.py --component \"User Authentication\" --assets \"credentials,sessions\" --json --output threats.json\n   ```\n   Output: per-threat STRIDE category, DREAD score (Damage, Reproducibility, Exploitability, Affected users, Discoverability — each 1–10), and suggested mitigations. Repeat per DFD element; `--interactive` walks scoping questions; `--list-threats` shows the threat database.\n3. **Consume the output:** sort `threats.json` by DREAD score descending; everything ≥ 7 average needs a named mitigation owner before the design ships. Map each mitigation to the responsible sibling lane (e.g., IAM threats → `cloud-security`, injection threats → `code-reviewer`).\n4. **Quick secret sweep** while you have the codebase open:\n   ```bash\n   python3 scripts\u002Fsecret_scanner.py \u002Fpath\u002Fto\u002Fproject --format json --severity high\n   ```\n   20+ patterns (AWS keys, GitHub tokens, private keys, generic credentials). Any critical\u002Fhigh finding blocks merge until rotated and moved to a secret manager.\n5. **Verification gate:** every DFD element has ≥ 1 STRIDE row considered, every threat with DREAD ≥ 7 has an owner + mitigation, and the secret scan exits with zero high\u002Fcritical findings. Re-run both tools after mitigations land — that re-run is the done signal, not the document.\n\n### STRIDE per Element Matrix\n\n| DFD Element | S | T | R | I | D | E |\n|-------------|---|---|---|---|---|---|\n| External Entity | X | | X | | | |\n| Process | X | X | X | X | X | X |\n| Data Store | | X | X | X | X | |\n| Data Flow | | X | | X | X | |\n\n(S=Spoofing→authn, T=Tampering→integrity, R=Repudiation→audit logs, I=Info Disclosure→encryption\u002Faccess control, D=DoS→rate limiting\u002Fredundancy, E=Elevation→least privilege.)\n\n## References (load on demand)\n\n| Document | Content |\n|----------|---------|\n| [references\u002Fthreat-modeling-guide.md](references\u002Fthreat-modeling-guide.md) | STRIDE methodology, attack trees, DREAD scoring, DFD creation |\n| [references\u002Fsecurity-architecture-patterns.md](references\u002Fsecurity-architecture-patterns.md) | Zero Trust, defense-in-depth, authentication patterns, API security |\n| [references\u002Fcryptography-implementation.md](references\u002Fcryptography-implementation.md) | AES-GCM, Ed25519, password hashing (Argon2id), key management |\n\nThe architecture and crypto references are kept because no sibling ships them; for *operating* those controls (scanning, compliance, monitoring) still route to `senior-secops`.\n","# Senior Security Engineer — Threat Modeling + Security Router\n\nThis skill does exactly one job itself — **STRIDE\u002FDREAD threat modeling** (plus a quick secret scan) — and routes every other security request to the specialist skill that owns that lane. Do not duplicate sibling content here; route instead.\n\n## Routing Table (read this first)\n\n| The user wants... | Route to | Why that skill owns it |\n|---|---|---|\n| Vulnerability assessment, pen-test methodology, OWASP Top 10 testing | `..\u002Fsecurity-pen-testing\u002F` | Ships `vulnerability_scanner.py` + `dependency_auditor.py` with exit-code contracts |\n| Incident triage, SEV classification, forensics, containment | `..\u002Fincident-response\u002F` | SEV1–SEV4 taxonomy, NIST SP 800-61 phases, `incident_triage.py` |\n| Production outage command (non-security incidents) | `..\u002Fincident-commander\u002F` | Severity classifier + timeline + postmortem tools |\n| Security monitoring, CVE triage SLAs, compliance checks (SOC 2 etc.), security headers | `..\u002Fsenior-secops\u002F` | `security_scanner.py` + `compliance_checker.py`, CVE SLA table |\n| Hostile\u002Fadversarial code review | `..\u002Fadversarial-reviewer\u002F` | 3-persona review with BLOCK\u002FCONCERNS\u002FCLEAN verdict |\n| Secure code review as part of general review | `..\u002Fcode-reviewer\u002F` | Language dispatch + regression fixtures |\n| Cloud IAM escalation paths, S3 exposure, security groups | `..\u002Fcloud-security\u002F` | `cloud_posture_check.py` with per-check exit codes |\n| Threat hunting, IOC sweeps, anomaly detection | `..\u002Fthreat-detection\u002F` | z-score anomaly + IOC staleness tooling |\n| Red-team engagement planning, ATT&CK kill chains | `..\u002Fred-team\u002F` | `engagement_planner.py` with authorization gate |\n| LLM\u002FAI attack surface (prompt injection, poisoning) | `..\u002Fai-security\u002F` | ATLAS-mapped `ai_threat_scanner.py` |\n\nIf the request spans lanes (e.g., \"secure this new architecture\"), do the threat model here first — its output (prioritized threats + mitigations) tells you which siblings to load next. Never bulk-load multiple security skills speculatively.\n\n## What This Skill Owns: STRIDE Threat Modeling\n\n### Workflow\n\n1. **Scope:** assets to protect, trust boundaries, data flows (external entities, processes, data stores, flows).\n2. **Generate the threat model** per component:\n   ```bash\n   python3 scripts\u002Fthreat_modeler.py --component \"User Authentication\" --assets \"credentials,sessions\" --json --output threats.json\n   ```\n   Output: per-threat STRIDE category, DREAD score (Damage, Reproducibility, Exploitability, Affected users, Discoverability — each 1–10), and suggested mitigations. Repeat per DFD element; `--interactive` walks scoping questions; `--list-threats` shows the threat database.\n3. **Consume the output:** sort `threats.json` by DREAD score descending; everything ≥ 7 average needs a named mitigation owner before the design ships. Map each mitigation to the responsible sibling lane (e.g., IAM threats → `cloud-security`, injection threats → `code-reviewer`).\n4. **Quick secret sweep** while you have the codebase open:\n   ```bash\n   python3 scripts\u002Fsecret_scanner.py \u002Fpath\u002Fto\u002Fproject --format json --severity high\n   ```\n   20+ patterns (AWS keys, GitHub tokens, private keys, generic credentials). Any critical\u002Fhigh finding blocks merge until rotated and moved to a secret manager.\n5. **Verification gate:** every DFD element has ≥ 1 STRIDE row considered, every threat with DREAD ≥ 7 has an owner + mitigation, and the secret scan exits with zero high\u002Fcritical findings. Re-run both tools after mitigations land — that re-run is the done signal, not the document.\n\n### STRIDE per Element Matrix\n\n| DFD Element | S | T | R | I | D | E |\n|-------------|---|---|---|---|---|---|\n| External Entity | X | | X | | | |\n| Process | X | X | X | X | X | X |\n| Data Store | | X | X | X | X | |\n| Data Flow | | X | | X | X | |\n\n(S=Spoofing→authn, T=Tampering→integrity, R=Repudiation→audit logs, I=Info Disclosure→encryption\u002Faccess control, D=DoS→rate limiting\u002Fredundancy, E=Elevation→least privilege.)\n\n## References (load on demand)\n\n| Document | Content |\n|----------|---------|\n| [references\u002Fthreat-modeling-guide.md](references\u002Fthreat-modeling-guide.md) | STRIDE methodology, attack trees, DREAD scoring, DFD creation |\n| [references\u002Fsecurity-architecture-patterns.md](references\u002Fsecurity-architecture-patterns.md) | Zero Trust, defense-in-depth, authentication patterns, API security |\n| [references\u002Fcryptography-implementation.md](references\u002Fcryptography-implementation.md) | AES-GCM, Ed25519, password hashing (Argon2id), key management |\n\nThe architecture and crypto references are kept because no sibling ships them; for *operating* those controls (scanning, compliance, monitoring) still route to `senior-secops`.\n",{"name":5,"description":7},"main","b4ebd6d8c3b36347a5d435bcb343a5fc1c6f08d1","skills-library\u002Fengineering-team\u002Fskills\u002Fsenior-security","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE","https:\u002F\u002Fgithub.com\u002FTehutiRaEl","2026-11-15 04:00:21",{"source":8,"skillName":5,"commands":30,"prompt":40,"zipAvailable":41},[31,34,37],{"tool":32,"command":33},"npx","npx skills add TehutiRaEl\u002FTHEHIVE --skill senior-security",{"tool":35,"command":36},"bunx","bunx skills add TehutiRaEl\u002FTHEHIVE --skill senior-security",{"tool":38,"command":39},"pnpm","pnpm dlx skills add TehutiRaEl\u002FTHEHIVE --skill senior-security","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fengineering-team\u002Fskills\u002Fsenior-security\u002FSKILL.md",true,[43,49,53,57,63],{"path":44,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":47,"sourceHtmlUrl":48},"references\u002Fcryptography-implementation.md","REFERENCE","参考文档",21912,"https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fengineering-team\u002Fskills\u002Fsenior-security\u002Freferences\u002Fcryptography-implementation.md",{"path":50,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fsecurity-architecture-patterns.md",22198,"https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fengineering-team\u002Fskills\u002Fsenior-security\u002Freferences\u002Fsecurity-architecture-patterns.md",{"path":54,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Fthreat-modeling-guide.md",22659,"https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fengineering-team\u002Fskills\u002Fsenior-security\u002Freferences\u002Fthreat-modeling-guide.md",{"path":58,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":61,"sourceHtmlUrl":62},"scripts\u002Fsecret_scanner.py","SCRIPT","脚本",18120,"https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fengineering-team\u002Fskills\u002Fsenior-security\u002Fscripts\u002Fsecret_scanner.py",{"path":64,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":65,"sourceHtmlUrl":66},"scripts\u002Fthreat_modeler.py",21325,"https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fengineering-team\u002Fskills\u002Fsenior-security\u002Fscripts\u002Fthreat_modeler.py",[68,75,81,88,95,102],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M76XP63XDM4PFPX8MMVYN9JX","preamble-gate","Use BEFORE doing any work in this repo — before the first file edit, commit, push, PR, branch operation, workflow dispatch, scheduled trigger or timer, agent\u002Fsubagent spawn, dependency install, or message sent to an outside service. Forces a plain-language preamble to the founder first: WHAT you are about to do, WHY, HOW, why it is NECESSARY, the PROJECTED IMPROVEMENT, and the COST and RISK — then, for consequential work (governance, security, money, CI\u002Ftriggers, rewriting history, multi-agent fan-out), waits for an explicit go-ahead. Read-only investigation (reading files, grep, git log\u002Fdiff, answering questions) is exempt. Applies to every AI that works in this repo, not just Claude. Founder rule, 2026-11-10, written after an unattended automation ran up cost and froze the hive. Not a substitute for wired-or-not (which governs how completion is CLAIMED); this governs what happens BEFORE work starts.","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fpreamble-gate\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M75RAYXC1W361YR9NBXD59AM","visionary-recommender","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills\u002Fvisionary-recommender\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M75RAQN9Q450RD57J2S6FSR4","syllabus","Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":18},"01M75RAG1XMCJMF30HFV5S79AK","research","Default entry point for any research request — a hybrid router that classifies the question deterministically and either delegates to a specialist research skill (pulse for trends\u002Fsentiment, grants for NIH funding, litreview for academic literature, syllabus for course reading, patent for prior-art + IP landscape, dossier for entity research) or runs its own plan-decompose-multi-source-search-synthesize-cite fallback workflow when no specialist matches. Always surfaces the routing decision so users can override. Use when the user makes any research request that doesn't obviously match a more-specific specialist skill (e.g., \"research [topic]\", \"look into [topic]\", \"what do we know about [topic]\", \"investigate [topic]\", \"find me information on [topic]\", \"do some research on [topic]\", \"I need to understand [topic]\"). Output is a markdown briefing (default) or .docx document (on request) with full citations and an audit log.","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fresearch\u002Fresearch\u002Fskills\u002Fresearch\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":18},"01M75RA8RK2JVWB8MYGRB65V75","pulse","Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X\u002FTwitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend\u002Fsentiment\u002Fproblems\u002Fopportunities\u002Fcomparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Use when the user requests multi-source recency intelligence on a topic (e.g., 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":18},"01M75RA08RXYRFSTNC6EEEX4ZD","patent","Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search \u002F freedom-to-operate \u002F competitive landscape \u002F acquisition diligence \u002F litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[]]