[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73G2H9P2D7AXEJP4J61R2AP":3,"skill-same:01M73G2H9P2D7AXEJP4J61R2AP":56},{"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":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":34,"commitSha":35,"skillDirectory":36,"forksCount":37,"repositoryHtmlUrl":38,"repositoryHomepageUrl":6,"ownerHtmlUrl":39,"ownerBlogUrl":6,"ownerDescription":40,"updatedAt":41,"install":42,"resources":55},"01M73G2H9P2D7AXEJP4J61R2AP","verify-authorization",null,"Hard gate: confirms a signed authorization document exists and contains all required fields before allowing any Phase 1+ (recon, exploitation, patching) activity to proceed. BLOCKS work if authorization is missing or incomplete.","5throck\u002Fai-workspace-standards","5throck","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F10958964?v=4","01M73BFEH0V0VS483TW4JD49JW","01M73BFEJ5VQZJHJSFTVPAZGDM",25,"AGPL-3.0","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-security\u002F.agents\u002Fskills\u002Fverify-authorization\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: verify-authorization\nscope: co-security\ndescription: >\n  Hard gate: confirms a signed authorization document exists and contains all required fields\n  before allowing any Phase 1+ (recon, exploitation, patching) activity to proceed.\n  BLOCKS work if authorization is missing or incomplete.\nversion: 1.1.0\nlast_reviewed: 2026-11-02\nstatus: active\nowner: pm\nprerequisites: engagement scoping complete — docs\u002Fscope.md must exist\nrelates_to:\n  - skill: stride-threat-matrix\n    type: follows\n---\n\n# 🔒 Skill: verify-authorization\n\n## Context\n\nThis skill is the mandatory pre-flight gate for all offensive and remediation activity.\nIt is invoked automatically by the PM before dispatching any Phase 1+ agent.\nNo PoC, recon, or patch activity may begin until this skill returns PASS.\n\n## When to Use\n\n- PM Agent dispatches automatically before any Phase 1+ agent (recon, exploitation, patching)\n- User attempts to start penetration testing activity without confirmed authorization\n- Re-check required after authorization documents are updated or engagement window changes\n\n## Execution Steps\n\n1. **Check for authorization document**\n   Look for `docs\u002Fauthorization.md` or `docs\u002Fauth\u002Fauthorization.md`.\n   If neither exists → **BLOCKED ❌** — \"No authorization document found. Run engagement-scoping first.\"\n\n2. **Validate required fields**\n   Read the authorization document and confirm ALL of the following fields are present and non-empty:\n   - `Authorizing Party` (name, title, organization)\n   - `Engagement Start Date` and `End Date`\n   - `In-Scope Targets` (at least one IP\u002FCIDR\u002Fdomain\u002Fapplication listed)\n   - `Out-of-Scope Items` (explicit list or \"None — all targets in scope\")\n   - `Rules of Engagement` (approved and prohibited techniques)\n   - `Emergency Contact` (name and contact method)\n   - `Authorized Signature` or `Authorization Reference Number`\n\n   **M-03 Requirement (2nd review meeting)**: Additionally validate:\n   - Signature date must be ≤ engagement start date\n   - Signatory title must carry authorization authority\n\n   If any field is missing → **BLOCKED ❌** — list the specific missing fields.\n\n3. **Check scope document**\n   Confirm `docs\u002Fscope.md` exists.\n   If missing → **BLOCKED ❌** — \"Scope document not found. Run engagement-scoping to generate docs\u002Fscope.md.\"\n\n4. **Check engagement window**\n   If authorization document includes start\u002Fend dates, compare against today's date.\n   If today is outside the authorized window → **BLOCKED ❌** — state the authorization window and current date.\n\n5. **Return result**\n   - All checks pass → **PASS ✅** — \"Authorization confirmed. Engagement window active. Phase N may proceed.\"\n   - Any check fails → **BLOCKED ❌** — list all failures. Do NOT proceed to Phase 1+.\n\n## Authorization Registry Check (Hub-Delegated Engagements)\n\nNormative for hub-delegated security work (design: `docs\u002Fdesigns\u002F2026-11-01-hub-consolidation-design.md` §3.2 — the hub is AVAILABLE only when the authorization registry is valid). Before any delegated engagement begins, this skill MUST resolve the `AUTH-YYYY-NNN` row cited by the delegation ticket in the hub's `docs\u002Fauthorization-registry.md` and enforce ALL three rules:\n\n1. **Expiry check**: the row's window end MUST be ≥ today's date. If the window is expired → **FAIL ❌** — show the row's window AND today's date side by side.\n2. **Requesting-project match**: the delegation ticket's requesting project MUST match the row's Requesting-project column. If it does not → **FAIL ❌** — state both the ticket's project and the row's project.\n3. **No-registry-row refusal**: if the cited row does not exist (or the ticket cites no row at all) → **FAIL ❌** — the delegation is refused outright. A missing row is NEVER remediated by drafting one: row addition is USER-only (the hub PM cannot self-attest). Direct the requester to the user to add the row.\n\nA row that fails any of the three rules blocks Phase 1+ dispatch exactly like a failed document check — registry failure and document failure are both hard BLOCKED outcomes.\n\n## Output Format\n\n```\n## Authorization Gate Result\n\n**Status**: PASS ✅ | BLOCKED ❌\n\n**Authorizing Party**: [name]\n**Engagement Window**: [start] – [end]\n**In-Scope**: [summary]\n\n**Checks**:\n- [x] Authorization document found\n- [x] All required fields present\n- [x] Signature date ≤ engagement start date (M-03)\n- [x] Signatory title carries authorization authority (M-03)\n- [x] Scope document exists\n- [x] Engagement window active\n- [x] Authorization registry row resolved (hub-delegated engagements): window-current, project-matched\n\n**Decision**: Phase [N] MAY proceed | HALT — do not dispatch any Phase 1+ agents\n```\n\n## Related Skills\n\n- `stride-threat-matrix` — threat model that defines what verify-authorization checks\n- `security-scan` — downstream verification after authorization passes\n\nThe original engagement pipeline (scoping, recon surface, finding tracker, patch\nautomation) never shipped as skills; this skill validates `docs\u002Fscope.md` and\n`docs\u002Fauthorization.md` produced by the PM workflow instead.\n","# 🔒 Skill: verify-authorization\n\n## Context\n\nThis skill is the mandatory pre-flight gate for all offensive and remediation activity.\nIt is invoked automatically by the PM before dispatching any Phase 1+ agent.\nNo PoC, recon, or patch activity may begin until this skill returns PASS.\n\n## When to Use\n\n- PM Agent dispatches automatically before any Phase 1+ agent (recon, exploitation, patching)\n- User attempts to start penetration testing activity without confirmed authorization\n- Re-check required after authorization documents are updated or engagement window changes\n\n## Execution Steps\n\n1. **Check for authorization document**\n   Look for `docs\u002Fauthorization.md` or `docs\u002Fauth\u002Fauthorization.md`.\n   If neither exists → **BLOCKED ❌** — \"No authorization document found. Run engagement-scoping first.\"\n\n2. **Validate required fields**\n   Read the authorization document and confirm ALL of the following fields are present and non-empty:\n   - `Authorizing Party` (name, title, organization)\n   - `Engagement Start Date` and `End Date`\n   - `In-Scope Targets` (at least one IP\u002FCIDR\u002Fdomain\u002Fapplication listed)\n   - `Out-of-Scope Items` (explicit list or \"None — all targets in scope\")\n   - `Rules of Engagement` (approved and prohibited techniques)\n   - `Emergency Contact` (name and contact method)\n   - `Authorized Signature` or `Authorization Reference Number`\n\n   **M-03 Requirement (2nd review meeting)**: Additionally validate:\n   - Signature date must be ≤ engagement start date\n   - Signatory title must carry authorization authority\n\n   If any field is missing → **BLOCKED ❌** — list the specific missing fields.\n\n3. **Check scope document**\n   Confirm `docs\u002Fscope.md` exists.\n   If missing → **BLOCKED ❌** — \"Scope document not found. Run engagement-scoping to generate docs\u002Fscope.md.\"\n\n4. **Check engagement window**\n   If authorization document includes start\u002Fend dates, compare against today's date.\n   If today is outside the authorized window → **BLOCKED ❌** — state the authorization window and current date.\n\n5. **Return result**\n   - All checks pass → **PASS ✅** — \"Authorization confirmed. Engagement window active. Phase N may proceed.\"\n   - Any check fails → **BLOCKED ❌** — list all failures. Do NOT proceed to Phase 1+.\n\n## Authorization Registry Check (Hub-Delegated Engagements)\n\nNormative for hub-delegated security work (design: `docs\u002Fdesigns\u002F2026-11-01-hub-consolidation-design.md` §3.2 — the hub is AVAILABLE only when the authorization registry is valid). Before any delegated engagement begins, this skill MUST resolve the `AUTH-YYYY-NNN` row cited by the delegation ticket in the hub's `docs\u002Fauthorization-registry.md` and enforce ALL three rules:\n\n1. **Expiry check**: the row's window end MUST be ≥ today's date. If the window is expired → **FAIL ❌** — show the row's window AND today's date side by side.\n2. **Requesting-project match**: the delegation ticket's requesting project MUST match the row's Requesting-project column. If it does not → **FAIL ❌** — state both the ticket's project and the row's project.\n3. **No-registry-row refusal**: if the cited row does not exist (or the ticket cites no row at all) → **FAIL ❌** — the delegation is refused outright. A missing row is NEVER remediated by drafting one: row addition is USER-only (the hub PM cannot self-attest). Direct the requester to the user to add the row.\n\nA row that fails any of the three rules blocks Phase 1+ dispatch exactly like a failed document check — registry failure and document failure are both hard BLOCKED outcomes.\n\n## Output Format\n\n```\n## Authorization Gate Result\n\n**Status**: PASS ✅ | BLOCKED ❌\n\n**Authorizing Party**: [name]\n**Engagement Window**: [start] – [end]\n**In-Scope**: [summary]\n\n**Checks**:\n- [x] Authorization document found\n- [x] All required fields present\n- [x] Signature date ≤ engagement start date (M-03)\n- [x] Signatory title carries authorization authority (M-03)\n- [x] Scope document exists\n- [x] Engagement window active\n- [x] Authorization registry row resolved (hub-delegated engagements): window-current, project-matched\n\n**Decision**: Phase [N] MAY proceed | HALT — do not dispatch any Phase 1+ agents\n```\n\n## Related Skills\n\n- `stride-threat-matrix` — threat model that defines what verify-authorization checks\n- `security-scan` — downstream verification after authorization passes\n\nThe original engagement pipeline (scoping, recon surface, finding tracker, patch\nautomation) never shipped as skills; this skill validates `docs\u002Fscope.md` and\n`docs\u002Fauthorization.md` produced by the PM workflow instead.\n",{"name":5,"owner":23,"scope":24,"status":25,"version":26,"relates_to":27,"description":31,"last_reviewed":32,"prerequisites":33},"pm","co-security","active","1.1.0",[28],{"type":29,"skill":30},"follows","stride-threat-matrix","Hard gate: confirms a signed authorization document exists and contains all required fields before allowing any Phase 1+ (recon, exploitation, patching) activity to proceed. BLOCKS work if authorization is missing or incomplete.\n",1793577600000,"engagement scoping complete — docs\u002Fscope.md must exist","main","1162ccc568cf90c01b3886d6143cbfd851a37883","templates\u002Fco-security\u002F.agents\u002Fskills\u002Fverify-authorization",9,"https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards","https:\u002F\u002Fgithub.com\u002F5throck","Experienced in digital transformation, enterprise IT, startup acceleration, and business strategy. Focused on building practical systems that connect technolo","2026-11-14 21:22:34",{"source":8,"skillName":5,"commands":43,"prompt":53,"zipAvailable":54},[44,47,50],{"tool":45,"command":46},"npx","npx skills add 5throck\u002Fai-workspace-standards --skill verify-authorization",{"tool":48,"command":49},"bunx","bunx skills add 5throck\u002Fai-workspace-standards --skill verify-authorization",{"tool":51,"command":52},"pnpm","pnpm dlx skills add 5throck\u002Fai-workspace-standards --skill verify-authorization","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-security\u002F.agents\u002Fskills\u002Fverify-authorization\u002FSKILL.md",true,[],[57,65,70,75,80,85],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":64},"01M7BBJDYHJMGTJYSC37JVWY8S","i18n-layout","Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL\u002Fbidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF\u002FBOM issues surface.","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":66,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":64},"01M7BBJ9XHAAS1AVGKZZ841VBZ","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.hermes\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":71,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":64},"01M7BBJ5C3X8TKFKG5R9P9P49W","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.gemini\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":76,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":64},"01M7BBJ1B52X0QMJ2QVBMPJB37","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.codex\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":81,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":64},"01M7BBHX91BW2Q2R276MRX5AW3","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.claude\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":86,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":64},"01M7BBHQWGXPSFRWN1PRC2NMMV","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.agents\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[]]