[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73DEM6KG09DX4J1HH2EBJDD":3,"skill-same:01M73DEM6KG09DX4J1HH2EBJDD":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},"01M73DEM6KG09DX4J1HH2EBJDD","sample-driven-report-writing",null,"Analyzes a deliverable sample (PDF\u002FDOCX\u002FMarkdown) to extract its table-of-contents structure AND, for each section, whether tables and\u002For charts are mandatory — then researches and drafts report content that matches the sample's exact structure and visual-element requirements. Use when: writing any consulting deliverable that must conform to a supplied sample or government\u002Finstitutional template format.","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-consult\u002F.claude\u002Fskills\u002Fsample-driven-report-writing\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: sample-driven-report-writing\nstatus: active\nscope: co-consult\ndescription: >\n  Analyzes a deliverable sample (PDF\u002FDOCX\u002FMarkdown) to extract its table-of-contents\n  structure AND, for each section, whether tables and\u002For charts are mandatory —\n  then researches and drafts report content that matches the sample's exact\n  structure and visual-element requirements. Use when: writing any consulting\n  deliverable that must conform to a supplied sample or government\u002Finstitutional\n  template format.\nowner: communications-lead\nversion: 1.1.0\nlast_reviewed: 2026-11-06\nprerequisites: consulting-report-writing\nmetadata:\n  type: domain\n  triggers:\n    - sample-driven report\n    - deliverable template\n    - match sample structure\n    - write to sample format\n---\n\n## Context\n\nThis skill generalizes the \"write-to-sample\" discipline: given a finished reference deliverable (a sample) or an official template form, produce a new deliverable whose chapter structure, section composition, and visual-element usage (tables\u002Fcharts) match the sample exactly — not approximately.\n\nIt replaces engagement-specific hardcoding (a fixed chapter table, a fixed page budget, a fixed team roster) with a **sample-analysis procedure** that derives all of those from the actual sample on disk. Always re-extract from the real attached sample; never trust a cached or previously-known structure, because template forms are revised (e.g. annual `2026형` → `2027형` editions change chapter counts and required tables).\n\n**PM Gateway applies**: PM displays an execution plan table before dispatching any specialist at each phase transition. PM may Write\u002FEdit only `memory\u002F*.md` and `CHANGELOG.md` directly; deliverable files are produced by dispatched specialists.\n\n## When to Use\n\n- A client or engagement lead supplies a reference deliverable (or a government\u002Finstitutional form template) and the new report must match its structure and format\n- A public-sector submission (a results\u002Freport template that specifies chapter count, mandatory tables, and page budget) must be filled in\n- A completed past deliverable should serve as the structural model for a new engagement\n- Do NOT use for free-form reports with no required structure — use `consulting-report-writing` alone\n\n## Execution Steps\n\n1. **Phase 1 — Sample Analysis**: Ingest the reference deliverable, extract its structure (TOC, mandatory tables\u002Fcharts per section, placeholder slots, page budget), and produce a Writing Spec artifact. Confirm the spec with the engagement lead before proceeding.\n2. **Phase 2 — Research**: Dispatch analytical inputs (financial, legal, industry) mapped to each chapter per the Writing Spec.\n3. **Phase 3 — Draft**: Assign chapter owners by content type, draft in parallel against the Writing Spec, replace all placeholders, enforce table-to-narrative ratio and mandatory visual elements.\n4. **Phase 4 — Validate & Render**: Structural validation, visual-element audit, render the draft as `.docx` \u002F `.pdf`; any other client-required format is produced outside the workspace from the Markdown draft. Max 2 revision cycles before PM escalation.\n\nDetailed instructions for each phase are below.\n\n## Phase 1 — Sample Analysis (the differentiator)\n\nIngest the actual sample and produce a **Writing Spec** artifact (`memory\u002F\u003Cengagement>-writing-spec-\u003Cdate>.md`). This is the single source of truth for the rest of the workflow.\n\n### 1.1 Ingest the sample\n\n| Sample format | Tool | Notes |\n|---|---|---|\n| `.pdf` | `md-to-ooxml` text extraction \u002F WebFetch \u002F manual read | If image-only PDF, OCR first |\n| `.docx` | `md-to-ooxml` \u002F `md-to-report` reader | |\n| Other formats (e.g. Korean office formats) | Not processed in the workspace — convert to PDF\u002FDOCX\u002FMarkdown outside the workspace first | |\n\nIf only a paper\u002FPDF scan exists, ask the engagement lead for the editable source — analysis fidelity drops sharply on scans.\n\n### 1.2 Extract the structure and the per-section visual-element requirements\n\nFor each chapter\u002Fsection visible in the sample, record in the Writing Spec:\n\n1. **Chapter\u002Fsection number and title** (English + original-language).\n2. **Table-of-contents position** and approximate page span in the sample.\n3. **Table mandatory-flag**: count table markers in that section (`표 N-N`, `\u003Ctable>`, pipe-tables). If the sample contains one or more tables in this section, mark it `requires-table`. Record the typical column structure.\n4. **Chart\u002Ffigure mandatory-flag**: count figure\u002Fchart markers (`그림 N-N`, `차트`, `그래프`, embedded images). Mark `requires-chart` where present. Record the chart type (trend line, bar, pie, etc.).\n5. **Narrative-only sections**: sections with neither table nor chart markers — prose is the expected output.\n6. **Placeholder\u002Fguideline slots**: every guideline-instruction block (`[작성 가이드라인]`, `[기재 방향]`, `예시N)`) and example block that the sample\u002Ftemplate uses to instruct the author. These MUST be replaced with real content in the draft — list them so none survive.\n7. **Page-budget target**: from the sample's completed length (or the template's stated budget), derive a per-chapter page target.\n\n**Critical**: the table\u002Fchart mandatory-flags are not decorative — a section marked `requires-table` is incomplete without a table, and `requires-chart` is incomplete without a chart. The draft cannot be considered done until every mandatory visual element is present.\n\n### 1.3 Confirm the spec with the engagement lead\n\nBefore research begins, confirm the Writing Spec (structure + mandatory visual elements + page budget) with the engagement lead. Template editions drift; a wrong spec wastes an entire drafting cycle.\n\n## Phase 2 — Research\n\nDispatch analytical inputs against the Writing Spec's section list:\n\n- **Company financials \u002F industry data** → `k-dart`, `financial-statement-analysis` pipeline (`bun scripts\u002Fco-consult\u002Ffinancial-pipeline.ts`), `company-intelligence`, `competitive-intelligence`\n- **Legal \u002F regulatory environment** → `k-law`\n- **Disclosure fallback** (non-disclosing \u002F unlisted target companies with no KR-profile DART filing): use company-provided source documents (`세무조정계산서`, `결산서`, `시산표`), explicitly labeled `기업 제공 비공식 자료` with document name and date — these are not independently verifiable the way a DART filing is.\n- Each research output is mapped to the specific chapter(s) it feeds, per the Writing Spec.\n\n## Phase 3 — Draft (parallel, against the Writing Spec)\n\n- PM\u002FCommunications Lead assigns chapters per the ownership implied by content type (financial → `data-analyst`; narrative → `communications-lead`; domain → `sme`; strategy → `strategy-analyst`). Dispatch chapter owners in parallel — disjoint chapters with Phase-1 research already in hand can be drafted concurrently.\n- Each owner drafts their chapters in Markdown, **replacing every guideline\u002Fplaceholder slot listed in the Writing Spec with real content**.\n- Enforce the **table-to-narrative ratio**: every data table is followed by at least half a page of interpretation. A table alone does not satisfy a section.\n- For every section marked `requires-table` \u002F `requires-chart`, the drafted section MUST contain that visual element (Markdown table \u002F Mermaid or chart-spec block).\n- Communications Lead assembles the full draft, edits for voice\u002Fterminology\u002FMECE consistency, and confirms chapter order matches the Writing Spec's TOC exactly.\n\n## Phase 4 — Validate & Render\n\n1. **Structural validation**: chapter order matches the sample TOC; no guideline\u002Fexample placeholder leftovers survive; per-chapter page count is within ±15% of the Writing Spec page budget.\n2. **Visual-element audit**: re-scan the draft for each section's mandatory-flag — every `requires-table` \u002F `requires-chart` section must contain its element. This is the check most likely to fail; iterate.\n3. **Render the final format**:\n   - Deliverables are drafted in Markdown. `.docx` \u002F `.pdf` (internal\u002Fclient review) → `bun scripts\u002Fco-consult\u002Fmd-to-report.ts \u003Cdraft.md>` (LibreOffice-backed PDF).\n   - If the client requires another format (e.g. a Korean office format), the Markdown draft is converted to that format outside the workspace; the workspace does not produce or validate it.\n4. Max 2 revision cycles before PM escalation.\n\n## Writing Principles (preserved)\n\n1. **No placeholder leftovers** — every guideline\u002Fexample block in the sample must become real narrative.\n2. **Expand through argument density, not appendices** — meet page targets by deepening tables\u002Fcharts\u002Finterpretation, never by padding with raw source documents.\n3. **Table-to-narrative ratio** — every table earns at least half a page of interpretation.\n4. **Disclosure fallback (KR profile: DART)** — explicitly label company-provided unofficial materials.\n5. **Client-data handling** — drafts contain financials and PII; review for sensitive data before any `git add`\u002Fcommit.\n6. **File naming** — `{company}-{report-type}-{YYYY-MM-DD}_ko.md` (draft) → `.docx` \u002F `.pdf` (or client format converted outside the workspace), in `deliverables\u002Freports\u002F`.\n\n## Output Format\n\n- **Writing Spec** (`memory\u002F\u003Cengagement>-writing-spec-\u003Cdate>.md`) — TOC + per-section table\u002Fchart flags + page budget + placeholder-slot list\n- Full deliverable draft (Markdown, chapter order matching the Writing Spec exactly)\n- Chapter-by-chapter page count vs. target\n- Final deliverable as `.docx` \u002F `.pdf` (or the Markdown draft for conversion to the client's required format outside the workspace), validated\n- `memory\u002FYYYY-MM-DD.md` engagement summary entry\n\n## Related Skills\n\n- `consulting-report-writing` — prerequisite; general report-writing standards\n- `k-dart`, `financial-statement-analysis` — financial research inputs (with DART-fallback procedure)\n- `k-law` — legal \u002F regulatory research input\n- `company-intelligence`, `competitive-intelligence` — company \u002F industry research inputs\n- `insight-synthesis` — cross-source synthesis for narrative chapters\n","## Context\n\nThis skill generalizes the \"write-to-sample\" discipline: given a finished reference deliverable (a sample) or an official template form, produce a new deliverable whose chapter structure, section composition, and visual-element usage (tables\u002Fcharts) match the sample exactly — not approximately.\n\nIt replaces engagement-specific hardcoding (a fixed chapter table, a fixed page budget, a fixed team roster) with a **sample-analysis procedure** that derives all of those from the actual sample on disk. Always re-extract from the real attached sample; never trust a cached or previously-known structure, because template forms are revised (e.g. annual `2026형` → `2027형` editions change chapter counts and required tables).\n\n**PM Gateway applies**: PM displays an execution plan table before dispatching any specialist at each phase transition. PM may Write\u002FEdit only `memory\u002F*.md` and `CHANGELOG.md` directly; deliverable files are produced by dispatched specialists.\n\n## When to Use\n\n- A client or engagement lead supplies a reference deliverable (or a government\u002Finstitutional form template) and the new report must match its structure and format\n- A public-sector submission (a results\u002Freport template that specifies chapter count, mandatory tables, and page budget) must be filled in\n- A completed past deliverable should serve as the structural model for a new engagement\n- Do NOT use for free-form reports with no required structure — use `consulting-report-writing` alone\n\n## Execution Steps\n\n1. **Phase 1 — Sample Analysis**: Ingest the reference deliverable, extract its structure (TOC, mandatory tables\u002Fcharts per section, placeholder slots, page budget), and produce a Writing Spec artifact. Confirm the spec with the engagement lead before proceeding.\n2. **Phase 2 — Research**: Dispatch analytical inputs (financial, legal, industry) mapped to each chapter per the Writing Spec.\n3. **Phase 3 — Draft**: Assign chapter owners by content type, draft in parallel against the Writing Spec, replace all placeholders, enforce table-to-narrative ratio and mandatory visual elements.\n4. **Phase 4 — Validate & Render**: Structural validation, visual-element audit, render the draft as `.docx` \u002F `.pdf`; any other client-required format is produced outside the workspace from the Markdown draft. Max 2 revision cycles before PM escalation.\n\nDetailed instructions for each phase are below.\n\n## Phase 1 — Sample Analysis (the differentiator)\n\nIngest the actual sample and produce a **Writing Spec** artifact (`memory\u002F\u003Cengagement>-writing-spec-\u003Cdate>.md`). This is the single source of truth for the rest of the workflow.\n\n### 1.1 Ingest the sample\n\n| Sample format | Tool | Notes |\n|---|---|---|\n| `.pdf` | `md-to-ooxml` text extraction \u002F WebFetch \u002F manual read | If image-only PDF, OCR first |\n| `.docx` | `md-to-ooxml` \u002F `md-to-report` reader | |\n| Other formats (e.g. Korean office formats) | Not processed in the workspace — convert to PDF\u002FDOCX\u002FMarkdown outside the workspace first | |\n\nIf only a paper\u002FPDF scan exists, ask the engagement lead for the editable source — analysis fidelity drops sharply on scans.\n\n### 1.2 Extract the structure and the per-section visual-element requirements\n\nFor each chapter\u002Fsection visible in the sample, record in the Writing Spec:\n\n1. **Chapter\u002Fsection number and title** (English + original-language).\n2. **Table-of-contents position** and approximate page span in the sample.\n3. **Table mandatory-flag**: count table markers in that section (`표 N-N`, `\u003Ctable>`, pipe-tables). If the sample contains one or more tables in this section, mark it `requires-table`. Record the typical column structure.\n4. **Chart\u002Ffigure mandatory-flag**: count figure\u002Fchart markers (`그림 N-N`, `차트`, `그래프`, embedded images). Mark `requires-chart` where present. Record the chart type (trend line, bar, pie, etc.).\n5. **Narrative-only sections**: sections with neither table nor chart markers — prose is the expected output.\n6. **Placeholder\u002Fguideline slots**: every guideline-instruction block (`[작성 가이드라인]`, `[기재 방향]`, `예시N)`) and example block that the sample\u002Ftemplate uses to instruct the author. These MUST be replaced with real content in the draft — list them so none survive.\n7. **Page-budget target**: from the sample's completed length (or the template's stated budget), derive a per-chapter page target.\n\n**Critical**: the table\u002Fchart mandatory-flags are not decorative — a section marked `requires-table` is incomplete without a table, and `requires-chart` is incomplete without a chart. The draft cannot be considered done until every mandatory visual element is present.\n\n### 1.3 Confirm the spec with the engagement lead\n\nBefore research begins, confirm the Writing Spec (structure + mandatory visual elements + page budget) with the engagement lead. Template editions drift; a wrong spec wastes an entire drafting cycle.\n\n## Phase 2 — Research\n\nDispatch analytical inputs against the Writing Spec's section list:\n\n- **Company financials \u002F industry data** → `k-dart`, `financial-statement-analysis` pipeline (`bun scripts\u002Fco-consult\u002Ffinancial-pipeline.ts`), `company-intelligence`, `competitive-intelligence`\n- **Legal \u002F regulatory environment** → `k-law`\n- **Disclosure fallback** (non-disclosing \u002F unlisted target companies with no KR-profile DART filing): use company-provided source documents (`세무조정계산서`, `결산서`, `시산표`), explicitly labeled `기업 제공 비공식 자료` with document name and date — these are not independently verifiable the way a DART filing is.\n- Each research output is mapped to the specific chapter(s) it feeds, per the Writing Spec.\n\n## Phase 3 — Draft (parallel, against the Writing Spec)\n\n- PM\u002FCommunications Lead assigns chapters per the ownership implied by content type (financial → `data-analyst`; narrative → `communications-lead`; domain → `sme`; strategy → `strategy-analyst`). Dispatch chapter owners in parallel — disjoint chapters with Phase-1 research already in hand can be drafted concurrently.\n- Each owner drafts their chapters in Markdown, **replacing every guideline\u002Fplaceholder slot listed in the Writing Spec with real content**.\n- Enforce the **table-to-narrative ratio**: every data table is followed by at least half a page of interpretation. A table alone does not satisfy a section.\n- For every section marked `requires-table` \u002F `requires-chart`, the drafted section MUST contain that visual element (Markdown table \u002F Mermaid or chart-spec block).\n- Communications Lead assembles the full draft, edits for voice\u002Fterminology\u002FMECE consistency, and confirms chapter order matches the Writing Spec's TOC exactly.\n\n## Phase 4 — Validate & Render\n\n1. **Structural validation**: chapter order matches the sample TOC; no guideline\u002Fexample placeholder leftovers survive; per-chapter page count is within ±15% of the Writing Spec page budget.\n2. **Visual-element audit**: re-scan the draft for each section's mandatory-flag — every `requires-table` \u002F `requires-chart` section must contain its element. This is the check most likely to fail; iterate.\n3. **Render the final format**:\n   - Deliverables are drafted in Markdown. `.docx` \u002F `.pdf` (internal\u002Fclient review) → `bun scripts\u002Fco-consult\u002Fmd-to-report.ts \u003Cdraft.md>` (LibreOffice-backed PDF).\n   - If the client requires another format (e.g. a Korean office format), the Markdown draft is converted to that format outside the workspace; the workspace does not produce or validate it.\n4. Max 2 revision cycles before PM escalation.\n\n## Writing Principles (preserved)\n\n1. **No placeholder leftovers** — every guideline\u002Fexample block in the sample must become real narrative.\n2. **Expand through argument density, not appendices** — meet page targets by deepening tables\u002Fcharts\u002Finterpretation, never by padding with raw source documents.\n3. **Table-to-narrative ratio** — every table earns at least half a page of interpretation.\n4. **Disclosure fallback (KR profile: DART)** — explicitly label company-provided unofficial materials.\n5. **Client-data handling** — drafts contain financials and PII; review for sensitive data before any `git add`\u002Fcommit.\n6. **File naming** — `{company}-{report-type}-{YYYY-MM-DD}_ko.md` (draft) → `.docx` \u002F `.pdf` (or client format converted outside the workspace), in `deliverables\u002Freports\u002F`.\n\n## Output Format\n\n- **Writing Spec** (`memory\u002F\u003Cengagement>-writing-spec-\u003Cdate>.md`) — TOC + per-section table\u002Fchart flags + page budget + placeholder-slot list\n- Full deliverable draft (Markdown, chapter order matching the Writing Spec exactly)\n- Chapter-by-chapter page count vs. target\n- Final deliverable as `.docx` \u002F `.pdf` (or the Markdown draft for conversion to the client's required format outside the workspace), validated\n- `memory\u002FYYYY-MM-DD.md` engagement summary entry\n\n## Related Skills\n\n- `consulting-report-writing` — prerequisite; general report-writing standards\n- `k-dart`, `financial-statement-analysis` — financial research inputs (with DART-fallback procedure)\n- `k-law` — legal \u002F regulatory research input\n- `company-intelligence`, `competitive-intelligence` — company \u002F industry research inputs\n- `insight-synthesis` — cross-source synthesis for narrative chapters\n",{"name":5,"owner":23,"scope":24,"status":25,"version":26,"metadata":27,"description":34,"last_reviewed":35,"prerequisites":36},"communications-lead","co-consult","active","1.1.0",{"type":28,"triggers":29},"domain",[30,31,32,33],"sample-driven report","deliverable template","match sample structure","write to sample format","Analyzes a deliverable sample (PDF\u002FDOCX\u002FMarkdown) to extract its table-of-contents structure AND, for each section, whether tables and\u002For charts are mandatory — then researches and drafts report content that matches the sample's exact structure and visual-element requirements. Use when: writing any consulting deliverable that must conform to a supplied sample or government\u002Finstitutional template format.\n",1793923200000,"consulting-report-writing","main","1162ccc568cf90c01b3886d6143cbfd851a37883","templates\u002Fco-consult\u002F.claude\u002Fskills\u002Fsample-driven-report-writing",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 sample-driven-report-writing",{"tool":51,"command":52},"bunx","bunx skills add 5throck\u002Fai-workspace-standards --skill sample-driven-report-writing",{"tool":54,"command":55},"pnpm","pnpm dlx skills add 5throck\u002Fai-workspace-standards --skill sample-driven-report-writing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-consult\u002F.claude\u002Fskills\u002Fsample-driven-report-writing\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",[],[]]