[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73G41S1JS3DTPJT7P7WG1BZ":3,"skill-same:01M73G41S1JS3DTPJT7P7WG1BZ":59},{"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":37,"commitSha":38,"skillDirectory":39,"forksCount":40,"repositoryHtmlUrl":41,"repositoryHomepageUrl":6,"ownerHtmlUrl":42,"ownerBlogUrl":6,"ownerDescription":43,"updatedAt":44,"install":45,"resources":58},"01M73G41S1JS3DTPJT7P7WG1BZ","samm-maturity",null,"OWASP SAMM maturity self-assessment producing a scored 15-stream posture roadmap across five business functions with three-level maturity rubric.","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.codex\u002Fskills\u002Fsamm-maturity\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: samm-maturity\ndescription: >\n  OWASP SAMM maturity self-assessment producing a scored 15-stream posture\n  roadmap across five business functions with three-level maturity rubric.\nversion: 1.1.0\nlast_reviewed: 2026-11-01\nstatus: active\nowner: pm\nprerequisites: Repository access, security artifacts (policies, scan results, incident logs)\nscope: co-security\nmetadata:\n  type: process\n  triggers:\n    - samm\n    - samm assessment\n    - maturity assessment\n    - security posture assessment\n---\n\n# 📊 Skill: samm-maturity\n\n## Context\n\nOWASP SAMM (Software Assurance Maturity Model) provides a structured framework for assessing software security practices across five business functions, each with three security practices, totaling 15 streams. Maturity is scored 0–3 per stream (Level 0 = ad-hoc\u002Fabsent, Level 1 = performed, Level 2 = quantified\u002Fmanaged, Level 3 = optimized).\n\n`samm-maturity` standardizes engagement-based security posture assessment by scoring all 15 streams against evidence, computing per-function and overall maturity, and generating a prioritized improvement roadmap.\n\n## When to Use\n\n- Performing baseline security posture assessment during {{PROJECT_PHASE_GATES}}.\n- Evaluating security program maturity before recommending tooling or process investments.\n- Tracking security improvement progress across multiple engagement cycles.\n- Generating stakeholder-ready maturity reports for governance, risk, and compliance (GRC) reviews.\n\n## Execution Steps\n\n1. **Scope the Engagement & Gather Evidence**\n   - Define assessment scope: organization, business unit, or product line.\n   - Collect evidence per stream: policy documents, architecture diagrams, CI\u002FCD configs, scan reports, incident logs, training records.\n   - Interview stakeholders: security leadership, engineering managers, DevOps owners, incident responders.\n\n2. **Score Each of the 15 Streams (0–3)**\n   For each stream, assign a maturity level with one-line evidence citation:\n\n   **Governance**\n   - **Strategy & Metrics** (G1): Security strategy, objectives, metrics program\n   - **Policy & Compliance** (G2): Security policies, regulatory compliance tracking\n   - **Education & Guidance** (G3): Security training, guidance docs, secure development resources\n\n   **Design**\n   - **Threat Assessment** (D1): Threat modeling, attack surface analysis\n   - **Secure Architecture** (D2): Secure design patterns, reference architectures\n   - **Security Requirements** (D3): Security requirements definition, acceptance criteria\n\n   **Implementation**\n   - **Secure Build** (I1): Secure build practices, dependency management, SAST\u002FDAST\n   - **Secure Deployment** (I2): Secure deployment automation, environment hardening\n   - **Defect Management** (I3): Vulnerability tracking, remediation SLAs\n\n   **Verification**\n   - **Implementation Verification** (V1): Code review, manual security testing\n   - **Security Testing** (V2): Automated security testing in CI\u002FCD\n   - **Requirements-driven Testing** (V3): Test coverage of security requirements\n\n   **Operations**\n   - **Incident Detection** (O1): Security monitoring, alerting, log analysis\n   - **Incident Response** (O2): Incident response playbook, forensics, communication\n   - **Operational Management** (O3): Configuration management, patch management, access control\n\n   **Maturity Level Rubric**:\n   - **Level 0**: Ad-hoc or absent (no documented process)\n   - **Level 1**: Performed (process exists but not consistent across org)\n   - **Level 2**: Quantified\u002Fmanaged (measured, tracked, some automation)\n   - **Level 3**: Optimized (fully automated, quantitative metrics, continuous improvement)\n\n3. **Compute Maturity Scores**\n   - Calculate per-function average: (sum of 3 stream scores) \u002F 3\n   - Calculate overall maturity score: (sum of all 15 stream scores) \u002F 15\n   - Round scores to one decimal place (e.g., 1.7, 2.3)\n\n4. **Build Target-State Roadmap**\n   For each stream below target maturity (typically Level 2 or 3):\n   - Identify current score and target score\n   - Define one concrete improvement action (S\u002FM\u002FL size)\n   - Tie action to the next maturity level step\n   - Prioritize by risk impact and implementation effort\n\n5. **Generate Output Artifact**\n   - Compile markdown assessment report with summary table and roadmap\n   - Save to `docs\u002Fsecurity\u002Fsamm-assessment-\u003CYYYY-MM-DD>.md`\n\n## Output Format\n\n```markdown\n# OWASP SAMM Maturity Assessment\n\n**Organization**: [Organization Name]\n**Assessment Date**: 2026-08-24\n**Evaluator**: [Evaluator Name]\n\n## Executive Summary\n\n**Overall Maturity**: 1.7 \u002F 3.0\n\n| Business Function | Stream Scores | Average |\n|---|---|---|\n| Governance | G1: 2, G2: 1, G3: 2 | 1.7 |\n| Design | D1: 1, D2: 1, D3: 1 | 1.0 |\n| Implementation | I1: 2, I2: 2, I3: 1 | 1.7 |\n| Verification | V1: 1, V2: 1, V3: 0 | 0.7 |\n| Operations | O1: 2, O2: 2, O3: 2 | 2.0 |\n\n## Detailed Stream Scores\n\n### Governance (1.7 \u002F 3.0)\n- **G1 Strategy & Metrics**: Level 2 — Metrics program established with quarterly KPI reviews (evidence: `docs\u002Fsecurity\u002Fmetrics-2026-Q2.md`)\n- **G2 Policy & Compliance**: Level 1 — Policies exist but compliance tracking is manual (evidence: `docs\u002Fpolicies\u002F`)\n- **G3 Education & Guidance**: Level 2 — Annual security training plus secure coding guidelines (evidence: `docs\u002Ftraining\u002F`)\n\n### Design (1.0 \u002F 3.0)\n- **D1 Threat Assessment**: Level 1 — Ad-hoc threat modeling, no standardized process\n- **D2 Secure Architecture**: Level 1 — Secure patterns documented but not enforced\n- **D3 Security Requirements**: Level 1 — Requirements defined per project, no standard catalog\n\n### Implementation (1.7 \u002F 3.0)\n- **I1 Secure Build**: Level 2 — SAST in CI\u002FCD, dependency scanning enabled (evidence: `.github\u002Fworkflows\u002F`)\n- **I2 Secure Deployment**: Level 2 — Infrastructure as code with security checks (evidence: `terraform\u002F`)\n- **I3 Defect Management**: Level 1 — Vulnerability tracking in Jira, inconsistent SLAs\n\n### Verification (0.7 \u002F 3.0)\n- **V1 Implementation Verification**: Level 1 — Manual code reviews, no standardized checklist\n- **V2 Security Testing**: Level 1 — DAST on production only, no pre-production testing\n- **V3 Requirements-driven Testing**: Level 0 — No security test coverage tracking\n\n### Operations (2.0 \u002F 3.0)\n- **O1 Incident Detection**: Level 2 — SIEM deployed with alert rules (evidence: `docs\u002Fsiem-rules.md`)\n- **O2 Incident Response**: Level 2 — Documented playbook, quarterly drills (evidence: `docs\u002Fir-playbook.md`)\n- **O3 Operational Management**: Level 2 — Automated patch management, quarterly access reviews\n\n## Prioritized Improvement Roadmap\n\n| Stream | Current | Target | Action | Size | Priority |\n|---|---|---|---|---|---|\n| V3 Requirements-driven Testing | 0 | 2 | Implement security test coverage tracking in CI\u002FCD | M | High |\n| D1 Threat Assessment | 1 | 2 | Standardize threat modeling process with template | S | High |\n| I3 Defect Management | 1 | 2 | Define vulnerability SLAs and automate tracking | M | High |\n| D2 Secure Architecture | 1 | 2 | Enforce secure patterns via architecture review gate | M | Medium |\n| V2 Security Testing | 1 | 2 | Integrate DAST into pre-production pipeline | M | Medium |\n\n**Size Legend**: S (1-2 weeks, \u003C5 person-days), M (3-8 weeks, 5-20 person-days), L (9+ weeks, >20 person-days)\n```\n\n## Co-develop Integration Note\n\nThis file is the hub-doctrine canonical for the co-security assurance suite\n(spec 2026-11-01-hub-consolidation-design, Phase 1 batch C). Co-security\nengagements run it as written. A co-develop pipeline instance derives from this\ndoctrine by substituting the bindings below — the derivation never edits\nfrontmatter: `owner: pm` stays single-valued here, and the co-develop ownership\nbinding lives in this note only.\n\nParameterization — unfilled placeholders resolve to the co-security doctrine\ndefaults; a co-develop derivation substitutes the bindings:\n\n| Placeholder | Instance | Unfilled default (co-security) | Co-develop binding |\n|---|---|---|---|\n| {{PROJECT_PHASE_GATES}} | When to Use, first bullet | Phase 1 security engagements | Phase 0 security baseline scans |\n\nCo-develop bindings beyond placeholders:\n\n- Ownership: co-develop renders this skill as co-owned `pm, security-monitor` — the Phase 0 security baseline scans it feeds are security-monitor scans. Frontmatter here stays `owner: pm`.\n- Delivery: the co-develop fork carries `scope: common`; this canonical keeps `scope: co-security` (the engagement label stays `co-security` for hub readers).\n\n## Related Skills\n\n- `stride-threat-matrix` — feeds Design\u002FVerification evidence (D1, D2, V1, V2) by identifying structural threats and risk ratings.\n- `sarif-exporter` — feeds Implementation\u002FVerification evidence (I1, I3, V2) by providing vulnerability findings and scan results in standardized format.\n- `security-scan` — produces SAST\u002FDAST\u002Fsecret detection results ingested into I1, I3, V2 scoring.\n","# 📊 Skill: samm-maturity\n\n## Context\n\nOWASP SAMM (Software Assurance Maturity Model) provides a structured framework for assessing software security practices across five business functions, each with three security practices, totaling 15 streams. Maturity is scored 0–3 per stream (Level 0 = ad-hoc\u002Fabsent, Level 1 = performed, Level 2 = quantified\u002Fmanaged, Level 3 = optimized).\n\n`samm-maturity` standardizes engagement-based security posture assessment by scoring all 15 streams against evidence, computing per-function and overall maturity, and generating a prioritized improvement roadmap.\n\n## When to Use\n\n- Performing baseline security posture assessment during {{PROJECT_PHASE_GATES}}.\n- Evaluating security program maturity before recommending tooling or process investments.\n- Tracking security improvement progress across multiple engagement cycles.\n- Generating stakeholder-ready maturity reports for governance, risk, and compliance (GRC) reviews.\n\n## Execution Steps\n\n1. **Scope the Engagement & Gather Evidence**\n   - Define assessment scope: organization, business unit, or product line.\n   - Collect evidence per stream: policy documents, architecture diagrams, CI\u002FCD configs, scan reports, incident logs, training records.\n   - Interview stakeholders: security leadership, engineering managers, DevOps owners, incident responders.\n\n2. **Score Each of the 15 Streams (0–3)**\n   For each stream, assign a maturity level with one-line evidence citation:\n\n   **Governance**\n   - **Strategy & Metrics** (G1): Security strategy, objectives, metrics program\n   - **Policy & Compliance** (G2): Security policies, regulatory compliance tracking\n   - **Education & Guidance** (G3): Security training, guidance docs, secure development resources\n\n   **Design**\n   - **Threat Assessment** (D1): Threat modeling, attack surface analysis\n   - **Secure Architecture** (D2): Secure design patterns, reference architectures\n   - **Security Requirements** (D3): Security requirements definition, acceptance criteria\n\n   **Implementation**\n   - **Secure Build** (I1): Secure build practices, dependency management, SAST\u002FDAST\n   - **Secure Deployment** (I2): Secure deployment automation, environment hardening\n   - **Defect Management** (I3): Vulnerability tracking, remediation SLAs\n\n   **Verification**\n   - **Implementation Verification** (V1): Code review, manual security testing\n   - **Security Testing** (V2): Automated security testing in CI\u002FCD\n   - **Requirements-driven Testing** (V3): Test coverage of security requirements\n\n   **Operations**\n   - **Incident Detection** (O1): Security monitoring, alerting, log analysis\n   - **Incident Response** (O2): Incident response playbook, forensics, communication\n   - **Operational Management** (O3): Configuration management, patch management, access control\n\n   **Maturity Level Rubric**:\n   - **Level 0**: Ad-hoc or absent (no documented process)\n   - **Level 1**: Performed (process exists but not consistent across org)\n   - **Level 2**: Quantified\u002Fmanaged (measured, tracked, some automation)\n   - **Level 3**: Optimized (fully automated, quantitative metrics, continuous improvement)\n\n3. **Compute Maturity Scores**\n   - Calculate per-function average: (sum of 3 stream scores) \u002F 3\n   - Calculate overall maturity score: (sum of all 15 stream scores) \u002F 15\n   - Round scores to one decimal place (e.g., 1.7, 2.3)\n\n4. **Build Target-State Roadmap**\n   For each stream below target maturity (typically Level 2 or 3):\n   - Identify current score and target score\n   - Define one concrete improvement action (S\u002FM\u002FL size)\n   - Tie action to the next maturity level step\n   - Prioritize by risk impact and implementation effort\n\n5. **Generate Output Artifact**\n   - Compile markdown assessment report with summary table and roadmap\n   - Save to `docs\u002Fsecurity\u002Fsamm-assessment-\u003CYYYY-MM-DD>.md`\n\n## Output Format\n\n```markdown\n# OWASP SAMM Maturity Assessment\n\n**Organization**: [Organization Name]\n**Assessment Date**: 2026-08-24\n**Evaluator**: [Evaluator Name]\n\n## Executive Summary\n\n**Overall Maturity**: 1.7 \u002F 3.0\n\n| Business Function | Stream Scores | Average |\n|---|---|---|\n| Governance | G1: 2, G2: 1, G3: 2 | 1.7 |\n| Design | D1: 1, D2: 1, D3: 1 | 1.0 |\n| Implementation | I1: 2, I2: 2, I3: 1 | 1.7 |\n| Verification | V1: 1, V2: 1, V3: 0 | 0.7 |\n| Operations | O1: 2, O2: 2, O3: 2 | 2.0 |\n\n## Detailed Stream Scores\n\n### Governance (1.7 \u002F 3.0)\n- **G1 Strategy & Metrics**: Level 2 — Metrics program established with quarterly KPI reviews (evidence: `docs\u002Fsecurity\u002Fmetrics-2026-Q2.md`)\n- **G2 Policy & Compliance**: Level 1 — Policies exist but compliance tracking is manual (evidence: `docs\u002Fpolicies\u002F`)\n- **G3 Education & Guidance**: Level 2 — Annual security training plus secure coding guidelines (evidence: `docs\u002Ftraining\u002F`)\n\n### Design (1.0 \u002F 3.0)\n- **D1 Threat Assessment**: Level 1 — Ad-hoc threat modeling, no standardized process\n- **D2 Secure Architecture**: Level 1 — Secure patterns documented but not enforced\n- **D3 Security Requirements**: Level 1 — Requirements defined per project, no standard catalog\n\n### Implementation (1.7 \u002F 3.0)\n- **I1 Secure Build**: Level 2 — SAST in CI\u002FCD, dependency scanning enabled (evidence: `.github\u002Fworkflows\u002F`)\n- **I2 Secure Deployment**: Level 2 — Infrastructure as code with security checks (evidence: `terraform\u002F`)\n- **I3 Defect Management**: Level 1 — Vulnerability tracking in Jira, inconsistent SLAs\n\n### Verification (0.7 \u002F 3.0)\n- **V1 Implementation Verification**: Level 1 — Manual code reviews, no standardized checklist\n- **V2 Security Testing**: Level 1 — DAST on production only, no pre-production testing\n- **V3 Requirements-driven Testing**: Level 0 — No security test coverage tracking\n\n### Operations (2.0 \u002F 3.0)\n- **O1 Incident Detection**: Level 2 — SIEM deployed with alert rules (evidence: `docs\u002Fsiem-rules.md`)\n- **O2 Incident Response**: Level 2 — Documented playbook, quarterly drills (evidence: `docs\u002Fir-playbook.md`)\n- **O3 Operational Management**: Level 2 — Automated patch management, quarterly access reviews\n\n## Prioritized Improvement Roadmap\n\n| Stream | Current | Target | Action | Size | Priority |\n|---|---|---|---|---|---|\n| V3 Requirements-driven Testing | 0 | 2 | Implement security test coverage tracking in CI\u002FCD | M | High |\n| D1 Threat Assessment | 1 | 2 | Standardize threat modeling process with template | S | High |\n| I3 Defect Management | 1 | 2 | Define vulnerability SLAs and automate tracking | M | High |\n| D2 Secure Architecture | 1 | 2 | Enforce secure patterns via architecture review gate | M | Medium |\n| V2 Security Testing | 1 | 2 | Integrate DAST into pre-production pipeline | M | Medium |\n\n**Size Legend**: S (1-2 weeks, \u003C5 person-days), M (3-8 weeks, 5-20 person-days), L (9+ weeks, >20 person-days)\n```\n\n## Co-develop Integration Note\n\nThis file is the hub-doctrine canonical for the co-security assurance suite\n(spec 2026-11-01-hub-consolidation-design, Phase 1 batch C). Co-security\nengagements run it as written. A co-develop pipeline instance derives from this\ndoctrine by substituting the bindings below — the derivation never edits\nfrontmatter: `owner: pm` stays single-valued here, and the co-develop ownership\nbinding lives in this note only.\n\nParameterization — unfilled placeholders resolve to the co-security doctrine\ndefaults; a co-develop derivation substitutes the bindings:\n\n| Placeholder | Instance | Unfilled default (co-security) | Co-develop binding |\n|---|---|---|---|\n| {{PROJECT_PHASE_GATES}} | When to Use, first bullet | Phase 1 security engagements | Phase 0 security baseline scans |\n\nCo-develop bindings beyond placeholders:\n\n- Ownership: co-develop renders this skill as co-owned `pm, security-monitor` — the Phase 0 security baseline scans it feeds are security-monitor scans. Frontmatter here stays `owner: pm`.\n- Delivery: the co-develop fork carries `scope: common`; this canonical keeps `scope: co-security` (the engagement label stays `co-security` for hub readers).\n\n## Related Skills\n\n- `stride-threat-matrix` — feeds Design\u002FVerification evidence (D1, D2, V1, V2) by identifying structural threats and risk ratings.\n- `sarif-exporter` — feeds Implementation\u002FVerification evidence (I1, I3, V2) by providing vulnerability findings and scan results in standardized format.\n- `security-scan` — produces SAST\u002FDAST\u002Fsecret detection results ingested into I1, I3, V2 scoring.\n",{"name":5,"owner":23,"scope":24,"status":25,"version":26,"metadata":27,"description":34,"last_reviewed":35,"prerequisites":36},"pm","co-security","active","1.1.0",{"type":28,"triggers":29},"process",[30,31,32,33],"samm","samm assessment","maturity assessment","security posture assessment","OWASP SAMM maturity self-assessment producing a scored 15-stream posture roadmap across five business functions with three-level maturity rubric.\n",1793491200000,"Repository access, security artifacts (policies, scan results, incident logs)","main","1162ccc568cf90c01b3886d6143cbfd851a37883","templates\u002Fco-security\u002F.codex\u002Fskills\u002Fsamm-maturity",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":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add 5throck\u002Fai-workspace-standards --skill samm-maturity",{"tool":51,"command":52},"bunx","bunx skills add 5throck\u002Fai-workspace-standards --skill samm-maturity",{"tool":54,"command":55},"pnpm","pnpm dlx skills add 5throck\u002Fai-workspace-standards --skill samm-maturity","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-security\u002F.codex\u002Fskills\u002Fsamm-maturity\u002FSKILL.md",true,[],[60,68,73,78,83,88],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":67},"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":69,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":67},"01M7BBJ9XHAAS1AVGKZZ841VBZ","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.hermes\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":74,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":67},"01M7BBJ5C3X8TKFKG5R9P9P49W","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.gemini\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":79,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":67},"01M7BBJ1B52X0QMJ2QVBMPJB37","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.codex\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":84,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":67},"01M7BBHX91BW2Q2R276MRX5AW3","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.claude\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":89,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":67},"01M7BBHQWGXPSFRWN1PRC2NMMV","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.agents\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[]]