[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73G2MNJDXDX9QP9FAWM7XKK":3,"skill-same:01M73G2MNJDXDX9QP9FAWM7XKK":67},{"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":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":6,"ownerHtmlUrl":51,"ownerBlogUrl":6,"ownerDescription":52,"updatedAt":53,"install":54,"resources":66},"01M73G2MNJDXDX9QP9FAWM7XKK","finding-reconciliation",null,"Merges duplicate and overlapping security findings from multiple scan passes and tools into one deduplicated finding set keyed by code location and rule identity, ready for reporting and SARIF export.","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.claude\u002Fskills\u002Ffinding-reconciliation\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: finding-reconciliation\ndescription: >\n  Merges duplicate and overlapping security findings from multiple scan passes and tools into one\n  deduplicated finding set keyed by code location and rule identity, ready for reporting and SARIF export.\nversion: 1.1.0\nstatus: active\nowner: security-expert\nlast_reviewed: 2026-11-01\nprerequisites: Finding documents in docs\u002Ffindings\u002F (FIND-NNNN) and\u002For scanner outputs covering the same code from two or more passes or tools\nrelates_to:\n  - skill: spdx-sbom\n    type: follows\n  - skill: sarif-exporter\n    type: composes_with\nscope: co-security\nl2_propagate: true\nmetadata:\n  type: security-reporting\n  triggers:\n    - finding-reconciliation\n    - \u002Ffinding-reconciliation\n    - deduplicate findings\n    - merge duplicate findings\n    - finding reconciliation\n    - reconcile scan results\n---\n\n# 🧩 Skill: finding-reconciliation\n\n## Context\n\nDeduplication is the central value of professional finding-management platforms such as DefectDojo: when multiple scanners or multiple scan passes cover the same code, the same true defect arrives as several separate hits. An unreconciled finding set inflates finding counts, distorts severity rollups, and produces multiple report entries per defect.\n\nIn a `co-security` engagement, the {{PROJECT_ROLE}} documents each discovery at `docs\u002Ffindings\u002FFIND-NNNN.md`, scanner outputs (`security-scan`, SAST, secret detection) describe overlapping ground, and Phase 6 re-tests re-encounter findings already documented in Phase 3. {{PROJECT_ROLE_REPORTER}} and `sarif-exporter` both consume the finding set downstream, so duplicates propagate straight into the pentest report and the SARIF export.\n\n`finding-reconciliation` runs between finding creation and downstream synthesis\u002Fexport. It merges duplicate and overlapping findings into one canonical finding per true defect and emits a reconciliation table that downstream agents consume as the single source of truth.\n\n## When to Use\n\n- After multiple scan passes or tools (e.g. SAST plus secret detection plus manual pentest findings) have produced hits covering the same code.\n- Before {{PROJECT_ROLE_REPORTER}} synthesizes `docs\u002Ffindings\u002F` into the pentest report (Phase 5).\n- Before `sarif-exporter` serializes findings, so the exported report contains one result per true finding.\n- After {{PROJECT_PHASE_GATES}}, to fold re-discovered findings back into their original FIND-NNNN instead of spawning new IDs.\n- When two finding documents reference the same rule (CWE, scanner rule) or the same CVE from different locations.\n\n## Reconciliation Key\n\n**Primary key - location equivalence.** Two findings are the same finding when both hold:\n\n1. **Code location**: the same file plus an overlapping line\u002Fline-range.\n2. **Finding category**: the same class of issue (e.g. SQL injection, hardcoded secret, XSS).\n\nTwo hits at the same location describing the same class of issue are the same finding - merge them.\n\n**Secondary key - rule\u002FCVE equivalence.** Findings that reference the same rule ID (CWE identifier, scanner rule) or the same CVE from different locations are merged as one finding with multiple locations listed. Do not merge findings that merely share a category but hit unrelated code paths.\n\n**Merge rules.** When findings merge:\n\n- **Severity**: keep the MAXIMUM severity among merged members (Critical > High > Medium > Low > Informational).\n- **Provenance**: list all source findings - FIND-NNNN IDs and\u002For scanner sources.\n- **Discovery date**: keep the earliest discovery date among merged members.\n- **Evidence**: concatenate distinct evidence entries and drop exact duplicates.\n- **Surviving ID**: the lowest FIND-NNNN among merged members survives; the others close with status `Merged into FIND-XXXX`.\n\n## Execution Steps\n\n1. **Collect the Working Set**\n   - Read every finding document in `docs\u002Ffindings\u002FFIND-NNNN.md` plus raw scanner outputs not yet documented.\n   - Register each hit with: code location, category, severity, rule\u002FCVE, discovery date, evidence, source.\n\n2. **Normalize Locations**\n   - Resolve file paths to repository-relative paths with forward slashes.\n   - Expand single-line hits to the smallest line-range the finding actually describes.\n\n3. **Group by Primary Key**\n   - Cluster findings that share the same file, an overlapping line-range, and the same category.\n\n4. **Group by Secondary Key**\n   - From the remaining unclustered findings, cluster those that share the same rule ID (CWE, scanner rule) or the same CVE across different locations.\n\n5. **Merge Each Cluster**\n   - Apply the merge rules: maximum severity, all sources listed, earliest discovery date, distinct evidence concatenated, lowest FIND-NNNN survives.\n\n6. **Update Finding Documents**\n   - Mark merged-away findings with status `Merged into FIND-XXXX` in their document and in `docs\u002Ffindings\u002FINDEX.md`.\n   - Update the surviving finding with merged members, final severity, all code locations, and sources.\n\n7. **Emit the Reconciliation Table**\n   - Write the reconciliation table (below) to `docs\u002Ffindings\u002FRECONCILIATION.md` for the engagement.\n\n8. **Hand Off the Reconciled Set**\n   - Confirm {{PROJECT_ROLE_REPORTER}} ({{PROJECT_PHASE_GATES_REPORT}}) and `sarif-exporter` consume only the reconciled finding set.\n\n## Output Format\n\n```markdown\n## Finding Reconciliation - [Engagement Name]\n\n| Surviving FIND | Merged Members | Final Severity | Code Location(s) | Rule\u002FCVE | Sources |\n|----------------|----------------|----------------|-------------------|----------|---------|\n| FIND-0007 | FIND-0012, FIND-0019 | High | src\u002Fapi\u002Fdispatch.ts:45-52 | CWE-89 | {{PROJECT_ROLE}}, semgrep |\n| FIND-0021 | FIND-0023 | Critical | src\u002Fauth\u002Fsession.ts:110; src\u002Fauth\u002Fjwt.ts:34 | CVE-2024-XXXX | {{PROJECT_ROLE}}, security-scan |\n```\n\n## Out of Scope\n\n- This skill does not re-score severity beyond the merge rule (maximum severity wins) - severity reclassification with CVSS justification stays with the threat model and report synthesis.\n- This skill does not export SARIF - serialization stays with `sarif-exporter`.\n- This skill does not triage business-risk acceptance - `Accepted-Risk` decisions stay with the {{PROJECT_ROLE_RISK}} and client sign-off.\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: security-expert` stays single-valued here, and the\nco-develop ownership binding 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_ROLE}} | Context, documenting seat; Output Format, `Sources` column (2 rows) | pentester | security-monitor |\n| {{PROJECT_ROLE_REPORTER}} | Context and When to Use, synthesis seat; Execution step 8 | `report-writer` | the PM |\n| {{PROJECT_PHASE_GATES}} | When to Use, re-test bullet | Phase 6 re-tests | Phase 4 test-runner verification and the Phase 6 QA gate |\n| {{PROJECT_PHASE_GATES_REPORT}} | Execution step 8, parenthetical | Phase 5 | Phase 5 lifecycle finalization |\n| {{PROJECT_ROLE_RISK}} | Out of Scope, `Accepted-Risk` seat | Red Team Lead | PM |\n\nCo-develop bindings beyond placeholders (its whole-engagement-model reading of\nthe Context paragraph): \"In a `co-develop` engagement, the `security-monitor`\ndocuments each discovery at `docs\u002Ffindings\u002FFIND-NNNN.md`, scanner outputs\n(`security-scan`, SAST, secret detection) describe overlapping ground, and Phase\n4 test-runner verification and the Phase 6 QA gate re-encounter findings already\ndocumented in Phase 0\u002F5 security-monitor scans. The PM (Phase 5 lifecycle\nfinalization) and `sarif-exporter` both consume the finding set downstream, so\nduplicates propagate straight into the final report and the SARIF export.\"\nThe remaining prose divergences it carries: \"manual pentest findings\" reads as\n\"manual security-review findings\"; \"pentest report\" reads as \"security report\";\n\"client sign-off\" reads as \"user sign-off\". Related Skills: co-develop omits\nthe `verify-authorization` entry (that pre-flight gate is a co-security\nengagement skill not adopted in the co-develop pipeline). Delivery: the\nco-develop fork carries `scope: common`; this canonical keeps\n`scope: co-security`.\n\n## Related Skills\n\n- `sarif-exporter` - serializes the reconciled finding set into SARIF v2.1.0.\n- `stride-threat-matrix` - produces DREAD-scored threat findings that enter the reconciliation set.\n- `verify-authorization` - mandatory pre-flight gate for the engagement.\n","# 🧩 Skill: finding-reconciliation\n\n## Context\n\nDeduplication is the central value of professional finding-management platforms such as DefectDojo: when multiple scanners or multiple scan passes cover the same code, the same true defect arrives as several separate hits. An unreconciled finding set inflates finding counts, distorts severity rollups, and produces multiple report entries per defect.\n\nIn a `co-security` engagement, the {{PROJECT_ROLE}} documents each discovery at `docs\u002Ffindings\u002FFIND-NNNN.md`, scanner outputs (`security-scan`, SAST, secret detection) describe overlapping ground, and Phase 6 re-tests re-encounter findings already documented in Phase 3. {{PROJECT_ROLE_REPORTER}} and `sarif-exporter` both consume the finding set downstream, so duplicates propagate straight into the pentest report and the SARIF export.\n\n`finding-reconciliation` runs between finding creation and downstream synthesis\u002Fexport. It merges duplicate and overlapping findings into one canonical finding per true defect and emits a reconciliation table that downstream agents consume as the single source of truth.\n\n## When to Use\n\n- After multiple scan passes or tools (e.g. SAST plus secret detection plus manual pentest findings) have produced hits covering the same code.\n- Before {{PROJECT_ROLE_REPORTER}} synthesizes `docs\u002Ffindings\u002F` into the pentest report (Phase 5).\n- Before `sarif-exporter` serializes findings, so the exported report contains one result per true finding.\n- After {{PROJECT_PHASE_GATES}}, to fold re-discovered findings back into their original FIND-NNNN instead of spawning new IDs.\n- When two finding documents reference the same rule (CWE, scanner rule) or the same CVE from different locations.\n\n## Reconciliation Key\n\n**Primary key - location equivalence.** Two findings are the same finding when both hold:\n\n1. **Code location**: the same file plus an overlapping line\u002Fline-range.\n2. **Finding category**: the same class of issue (e.g. SQL injection, hardcoded secret, XSS).\n\nTwo hits at the same location describing the same class of issue are the same finding - merge them.\n\n**Secondary key - rule\u002FCVE equivalence.** Findings that reference the same rule ID (CWE identifier, scanner rule) or the same CVE from different locations are merged as one finding with multiple locations listed. Do not merge findings that merely share a category but hit unrelated code paths.\n\n**Merge rules.** When findings merge:\n\n- **Severity**: keep the MAXIMUM severity among merged members (Critical > High > Medium > Low > Informational).\n- **Provenance**: list all source findings - FIND-NNNN IDs and\u002For scanner sources.\n- **Discovery date**: keep the earliest discovery date among merged members.\n- **Evidence**: concatenate distinct evidence entries and drop exact duplicates.\n- **Surviving ID**: the lowest FIND-NNNN among merged members survives; the others close with status `Merged into FIND-XXXX`.\n\n## Execution Steps\n\n1. **Collect the Working Set**\n   - Read every finding document in `docs\u002Ffindings\u002FFIND-NNNN.md` plus raw scanner outputs not yet documented.\n   - Register each hit with: code location, category, severity, rule\u002FCVE, discovery date, evidence, source.\n\n2. **Normalize Locations**\n   - Resolve file paths to repository-relative paths with forward slashes.\n   - Expand single-line hits to the smallest line-range the finding actually describes.\n\n3. **Group by Primary Key**\n   - Cluster findings that share the same file, an overlapping line-range, and the same category.\n\n4. **Group by Secondary Key**\n   - From the remaining unclustered findings, cluster those that share the same rule ID (CWE, scanner rule) or the same CVE across different locations.\n\n5. **Merge Each Cluster**\n   - Apply the merge rules: maximum severity, all sources listed, earliest discovery date, distinct evidence concatenated, lowest FIND-NNNN survives.\n\n6. **Update Finding Documents**\n   - Mark merged-away findings with status `Merged into FIND-XXXX` in their document and in `docs\u002Ffindings\u002FINDEX.md`.\n   - Update the surviving finding with merged members, final severity, all code locations, and sources.\n\n7. **Emit the Reconciliation Table**\n   - Write the reconciliation table (below) to `docs\u002Ffindings\u002FRECONCILIATION.md` for the engagement.\n\n8. **Hand Off the Reconciled Set**\n   - Confirm {{PROJECT_ROLE_REPORTER}} ({{PROJECT_PHASE_GATES_REPORT}}) and `sarif-exporter` consume only the reconciled finding set.\n\n## Output Format\n\n```markdown\n## Finding Reconciliation - [Engagement Name]\n\n| Surviving FIND | Merged Members | Final Severity | Code Location(s) | Rule\u002FCVE | Sources |\n|----------------|----------------|----------------|-------------------|----------|---------|\n| FIND-0007 | FIND-0012, FIND-0019 | High | src\u002Fapi\u002Fdispatch.ts:45-52 | CWE-89 | {{PROJECT_ROLE}}, semgrep |\n| FIND-0021 | FIND-0023 | Critical | src\u002Fauth\u002Fsession.ts:110; src\u002Fauth\u002Fjwt.ts:34 | CVE-2024-XXXX | {{PROJECT_ROLE}}, security-scan |\n```\n\n## Out of Scope\n\n- This skill does not re-score severity beyond the merge rule (maximum severity wins) - severity reclassification with CVSS justification stays with the threat model and report synthesis.\n- This skill does not export SARIF - serialization stays with `sarif-exporter`.\n- This skill does not triage business-risk acceptance - `Accepted-Risk` decisions stay with the {{PROJECT_ROLE_RISK}} and client sign-off.\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: security-expert` stays single-valued here, and the\nco-develop ownership binding 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_ROLE}} | Context, documenting seat; Output Format, `Sources` column (2 rows) | pentester | security-monitor |\n| {{PROJECT_ROLE_REPORTER}} | Context and When to Use, synthesis seat; Execution step 8 | `report-writer` | the PM |\n| {{PROJECT_PHASE_GATES}} | When to Use, re-test bullet | Phase 6 re-tests | Phase 4 test-runner verification and the Phase 6 QA gate |\n| {{PROJECT_PHASE_GATES_REPORT}} | Execution step 8, parenthetical | Phase 5 | Phase 5 lifecycle finalization |\n| {{PROJECT_ROLE_RISK}} | Out of Scope, `Accepted-Risk` seat | Red Team Lead | PM |\n\nCo-develop bindings beyond placeholders (its whole-engagement-model reading of\nthe Context paragraph): \"In a `co-develop` engagement, the `security-monitor`\ndocuments each discovery at `docs\u002Ffindings\u002FFIND-NNNN.md`, scanner outputs\n(`security-scan`, SAST, secret detection) describe overlapping ground, and Phase\n4 test-runner verification and the Phase 6 QA gate re-encounter findings already\ndocumented in Phase 0\u002F5 security-monitor scans. The PM (Phase 5 lifecycle\nfinalization) and `sarif-exporter` both consume the finding set downstream, so\nduplicates propagate straight into the final report and the SARIF export.\"\nThe remaining prose divergences it carries: \"manual pentest findings\" reads as\n\"manual security-review findings\"; \"pentest report\" reads as \"security report\";\n\"client sign-off\" reads as \"user sign-off\". Related Skills: co-develop omits\nthe `verify-authorization` entry (that pre-flight gate is a co-security\nengagement skill not adopted in the co-develop pipeline). Delivery: the\nco-develop fork carries `scope: common`; this canonical keeps\n`scope: co-security`.\n\n## Related Skills\n\n- `sarif-exporter` - serializes the reconciled finding set into SARIF v2.1.0.\n- `stride-threat-matrix` - produces DREAD-scored threat findings that enter the reconciliation set.\n- `verify-authorization` - mandatory pre-flight gate for the engagement.\n",{"name":5,"owner":23,"scope":24,"status":25,"version":26,"metadata":27,"relates_to":35,"description":42,"l2_propagate":43,"last_reviewed":44,"prerequisites":45},"security-expert","co-security","active","1.1.0",{"type":28,"triggers":29},"security-reporting",[5,30,31,32,33,34],"\u002Ffinding-reconciliation","deduplicate findings","merge duplicate findings","finding reconciliation","reconcile scan results",[36,39],{"type":37,"skill":38},"follows","spdx-sbom",{"type":40,"skill":41},"composes_with","sarif-exporter","Merges duplicate and overlapping security findings from multiple scan passes and tools into one deduplicated finding set keyed by code location and rule identity, ready for reporting and SARIF export.\n",true,1793491200000,"Finding documents in docs\u002Ffindings\u002F (FIND-NNNN) and\u002For scanner outputs covering the same code from two or more passes or tools","main","1162ccc568cf90c01b3886d6143cbfd851a37883","templates\u002Fco-security\u002F.claude\u002Fskills\u002Ffinding-reconciliation",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":55,"prompt":65,"zipAvailable":43},[56,59,62],{"tool":57,"command":58},"npx","npx skills add 5throck\u002Fai-workspace-standards --skill finding-reconciliation",{"tool":60,"command":61},"bunx","bunx skills add 5throck\u002Fai-workspace-standards --skill finding-reconciliation",{"tool":63,"command":64},"pnpm","pnpm dlx skills add 5throck\u002Fai-workspace-standards --skill finding-reconciliation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-security\u002F.claude\u002Fskills\u002Ffinding-reconciliation\u002FSKILL.md",[],[68,76,81,86,91,96],{"skillNo":69,"name":70,"nameZh":6,"description":71,"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":75},"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":77,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":75},"01M7BBJ9XHAAS1AVGKZZ841VBZ","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.hermes\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":82,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":75},"01M7BBJ5C3X8TKFKG5R9P9P49W","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.gemini\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":87,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":75},"01M7BBJ1B52X0QMJ2QVBMPJB37","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.codex\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":92,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":75},"01M7BBHX91BW2Q2R276MRX5AW3","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.claude\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":97,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":75},"01M7BBHQWGXPSFRWN1PRC2NMMV","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.agents\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[]]