[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70FM9Z1SEGKHTY7NA4ZVRTS":3,"skill-same:01M70FM9Z1SEGKHTY7NA4ZVRTS":47},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M70FM9Z1SEGKHTY7NA4ZVRTS","skill-template",null,"jmlozano1990\u002FCowork-Starter-Kit","jmlozano1990","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F212240889?v=4","01M70FFEFRFH4C54MRVST1ZZFW","JmLozano","01M70FFEGEGDMH4RS95JKWH95M",6,"MIT","https:\u002F\u002Fgithub.com\u002Fjmlozano1990\u002FCowork-Starter-Kit\u002Fblob\u002Fmain\u002Ftemplates\u002Fskill-template\u002FSKILL.md",[],[18,19],"template","skill template","2026-11-10 10:12:30",false,"---\nname: [skill-slug]\n\u003C!-- Replace: folder name in snake-case, e.g. flashcard-generation — must match the parent folder name exactly -->\ndescription: [one sentence describing what this skill enables Cowork to do]\n\u003C!-- Replace: ≤160 characters. Start with a verb: \"Generate…\", \"Summarise…\", \"Draft…\", \"Extract…\" -->\n# trigger_examples is optional but recommended. Uncomment and fill in 3–6 trigger phrases.\n# These allow global-instructions.md proactive rules to pattern-match without parsing the ## Triggers body.\n# trigger_examples:\n#   - \"[phrase that reliably signals this skill should fire]\"\n#   - \"[another signal phrase for the same skill]\"\n#   - \"[a third trigger phrasing — vary the wording]\"\n---\n\u003C!-- CONTRIBUTOR NOTICE: Before editing the placeholder text in this template, read\n     `CONTRIBUTING.md § Placeholder authoring rules`.\n     The 5 rules govern how placeholders must be written to avoid shipping\n     unintended runtime instructions to Cowork. Key: use bracketed nouns, never\n     imperatives; never include Ignore\u002FDisregard\u002FOverride\u002FInstead\u002FAlways;\n     use HTML comments for guidance text; no safety-rule patterns; Example\n     placeholders must read as contributor-guidance, not Cowork instructions.\n\n     This 9-section structure is the kit's open substrate contribution format\n     (v2.18.0) — see docs\u002Fsubstrate-contribution-format.md for the full spec,\n     the adapter-isolation boundary, and the external consumer contract both\n     a future push and a future pull flow are built on. -->\n\n\u003C!-- ══════════════════════════════════════════════════════════════════════════\n     SECTION 1 — WHEN TO USE\n     Purpose: Cowork reads this section first to decide whether to invoke this\n     skill at all. Write 2–3 declarative sentences: the normal use case (1–2\n     sentences) + one edge condition (1 sentence). Do NOT write imperatives\n     (\"You should…\", \"Always do…\"). Target: 3–6 lines.\n     ══════════════════════════════════════════════════════════════════════════ -->\n## When to use\n\n[One sentence — the primary scenario where this skill applies.]\n[One sentence — a second situation or variation where it also applies.]\n[One sentence — an edge condition or boundary: when a lighter approach is more appropriate.]\n\n\u003C!-- ══════════════════════════════════════════════════════════════════════════\n     SECTION 2 — TRIGGERS\n     Purpose: Bullet list of phrases or situations that signal Cowork should\n     offer or auto-invoke this skill. Must stay consistent with the proactive\n     rules in the preset's global-instructions.md (v1.1 three-layer trigger\n     architecture). Target: 4–8 bullets.\n     ══════════════════════════════════════════════════════════════════════════ -->\n## Triggers\n\n- [A direct user phrase that reliably signals this skill, e.g. \"user says X\"]\n- [A task-type signal, e.g. \"user shares a [document type] and asks for [output type]\"]\n- [A follow-up signal, e.g. \"user asks to refine or expand an earlier output\"]\n- [A context signal, e.g. \"a specific file type or folder is mentioned in the request\"]\n- [An implicit signal — what the user is trying to accomplish without naming the skill]\n\n\u003C!-- ══════════════════════════════════════════════════════════════════════════\n     SECTION 3 — INSTRUCTIONS\n     Purpose: Step-by-step execution guide for Cowork. Use numbered steps.\n     Each step: one verb + one outcome. No prose paragraphs. Decompose any\n     step that would exceed 2 lines into two steps.\n     Target: 5–10 numbered steps.\n     ══════════════════════════════════════════════════════════════════════════ -->\n## Instructions\n\n1. [First step — what Cowork reads or gathers before starting]\n2. [Second step — the core processing or analysis action]\n3. [Third step — how Cowork structures or organises the output]\n4. [Fourth step — quality check or refinement before delivering]\n5. [Fifth step — final delivery action or follow-up offer to the user]\n\n\u003C!-- ══════════════════════════════════════════════════════════════════════════\n     SECTION 4 — OUTPUT FORMAT\n     Purpose: Explicit structure Cowork must produce. Specify headings,\n     list shapes, table schemas, counts, and length targets. A reviewer\n     reading this section should be able to check the output without\n     re-reading the instructions. Target: 4–10 lines.\n     ══════════════════════════════════════════════════════════════════════════ -->\n## Output format\n\n[Opening line — the top-level structure, e.g. \"Numbered list of [N] items.\"]\n\nEach item follows this shape:\n\n- [Field 1 label]: [description of what goes here and its length target]\n- [Field 2 label]: [description of what goes here and its length target]\n\n[One line — any count constraint, e.g. \"Aim for [N]–[M] items unless the user specifies otherwise.\"]\n[One line — closing action Cowork takes after delivering, e.g. \"End with a note on which items seem most important.\"]\n\n\u003C!-- ══════════════════════════════════════════════════════════════════════════\n     SECTION 5 — QUALITY CRITERIA\n     Purpose: 3–5 checkable criteria a reviewer can evaluate as yes\u002Fno.\n     Each bullet is one line. If a criterion cannot be checked by reading\n     the output, rephrase it until it can. Target: 3–5 bullets.\n     ══════════════════════════════════════════════════════════════════════════ -->\n## Quality criteria\n\n- [Criterion 1 — a structural check, e.g. \"Output contains the required [element]\"]\n- [Criterion 2 — a content depth check, e.g. \"Each [item] includes [required detail]\"]\n- [Criterion 3 — a scope check, e.g. \"Output stays within [count\u002Flength] target\"]\n- [Criterion 4 — a user-value check, e.g. \"Output would be directly usable without editing\"]\n- [Criterion 5 — an edge-case check, optional; remove this bullet if 4 criteria are sufficient]\n\n\u003C!-- ══════════════════════════════════════════════════════════════════════════\n     SECTION 6 — ANTI-PATTERNS\n     Purpose: 3–5 common mistakes Cowork must not make. One line each.\n     Frame as \"what NOT to do.\" Do not repeat quality criteria negated —\n     anti-patterns should surface failure modes that a quality check would\n     miss. Target: 3–5 bullets.\n     ══════════════════════════════════════════════════════════════════════════ -->\n## Anti-patterns\n\n- [Anti-pattern 1 — a common structural mistake in this skill's output domain]\n- [Anti-pattern 2 — a scope or depth error, e.g. \"surface-level output that doesn't …\"]\n- [Anti-pattern 3 — a voice or format error, e.g. \"treating all [input types] as equivalent when …\"]\n- [Anti-pattern 4 — a process error, e.g. \"starting without reading [required input]\"]\n- [Anti-pattern 5 — optional; remove if 4 anti-patterns are sufficient]\n\n\u003C!-- ══════════════════════════════════════════════════════════════════════════\n     SECTION 7 — EXAMPLE\n     Purpose: ONE worked input→output pair. Use a real-looking, minimal\n     example — not a hypothetical. The input should be brief enough to\n     paste here (3–8 lines). The output should illustrate the full format\n     specified in §Output format (not a truncated sketch).\n     Contributor note: paste a real input and the ideal output you would\n     accept in a PR review. Do NOT write instructions to Cowork here.\n     Target: 15–40 lines total for this section.\n     ══════════════════════════════════════════════════════════════════════════ -->\n## Example\n\n**Input:**\n\n[Paste a real input here — e.g. a snippet of text, a user request, or a file excerpt\nthat represents the most common activation scenario for this skill.\nKeep it to 3–8 lines so the example remains scannable.]\n\n**Output:**\n\n[Paste the ideal output here — the response Cowork should produce for the input above.\nMatch the structure in §Output format exactly. Include all required fields\u002Fsections.\nAim for a complete output, not a \"...\" truncated sketch — reviewers need to see the\nreal shape, not a placeholder for it.\nRemove this parenthetical when you paste the actual example.]\n\n\u003C!-- ══════════════════════════════════════════════════════════════════════════\n     SECTION 8 — WRITING-PROFILE INTEGRATION\n     Purpose: One sentence stating WHEN this skill consults\n     context\u002Fwriting-profile.md, plus one concrete rule.\n     Per v1.2 ADR-013: if output ≥100 words, the skill must reference the\n     writing profile. If output is always \u003C100 words, say so explicitly.\n     Target: 1–4 lines.\n     ══════════════════════════════════════════════════════════════════════════ -->\n## Writing-profile integration\n\n[One sentence — when this skill reads context\u002Fwriting-profile.md, e.g.\n\"When output exceeds 100 words, Cowork consults context\u002Fwriting-profile.md\nand applies the user's stated tone, sentence-length preferences, and pet peeves.\"]\n[One concrete rule, e.g. \"If no writing profile exists, default to clear and direct prose.\" — or\n\"This skill produces structured data under 100 words; writing profile is not consulted.\"]\n\n\u003C!-- ══════════════════════════════════════════════════════════════════════════\n     SECTION 9 — EXAMPLE PROMPTS\n     Purpose: 3 realistic invocation phrases the user might type. These\n     appear in skills-as-prompts.md and inform global-instructions.md\n     trigger rules. Write prompts users actually say, not command syntax.\n     Target: exactly 3 bullets.\n     ══════════════════════════════════════════════════════════════════════════ -->\n## Example prompts\n\n- \"[A direct invocation phrase — the most common way a user requests this skill]\"\n- \"[A variation with a specific input — e.g. a file reference or a scope qualifier]\"\n- \"[A follow-up or edge-case invocation — a less obvious but valid request for this skill]\"\n\n\u003C!-- ADR-015 defines the canonical 9-section template and length budget.\n     CI (skill-depth-check, ADR-016) enforces a 60-line floor: SKILL.md files\n     in depth-enforced presets that fall below 60 lines will fail CI.\n     This template targets 80–120 lines; the soft cap is 150 lines.\n     Reference: docs\u002Farchitecture.md §ADR-015. -->\n","\u003C!-- CONTRIBUTOR NOTICE: Before editing the placeholder text in this template, read\n     `CONTRIBUTING.md § Placeholder authoring rules`.\n     The 5 rules govern how placeholders must be written to avoid shipping\n     unintended runtime instructions to Cowork. Key: use bracketed nouns, never\n     imperatives; never include Ignore\u002FDisregard\u002FOverride\u002FInstead\u002FAlways;\n     use HTML comments for guidance text; no safety-rule patterns; Example\n     placeholders must read as contributor-guidance, not Cowork instructions.\n\n     This 9-section structure is the kit's open substrate contribution format\n     (v2.18.0) — see docs\u002Fsubstrate-contribution-format.md for the full spec,\n     the adapter-isolation boundary, and the external consumer contract both\n     a future push and a future pull flow are built on. -->\n\n\u003C!-- ══════════════════════════════════════════════════════════════════════════\n     SECTION 1 — WHEN TO USE\n     Purpose: Cowork reads this section first to decide whether to invoke this\n     skill at all. Write 2–3 declarative sentences: the normal use case (1–2\n     sentences) + one edge condition (1 sentence). Do NOT write imperatives\n     (\"You should…\", \"Always do…\"). Target: 3–6 lines.\n     ══════════════════════════════════════════════════════════════════════════ -->\n## When to use\n\n[One sentence — the primary scenario where this skill applies.]\n[One sentence — a second situation or variation where it also applies.]\n[One sentence — an edge condition or boundary: when a lighter approach is more appropriate.]\n\n\u003C!-- ══════════════════════════════════════════════════════════════════════════\n     SECTION 2 — TRIGGERS\n     Purpose: Bullet list of phrases or situations that signal Cowork should\n     offer or auto-invoke this skill. Must stay consistent with the proactive\n     rules in the preset's global-instructions.md (v1.1 three-layer trigger\n     architecture). Target: 4–8 bullets.\n     ══════════════════════════════════════════════════════════════════════════ -->\n## Triggers\n\n- [A direct user phrase that reliably signals this skill, e.g. \"user says X\"]\n- [A task-type signal, e.g. \"user shares a [document type] and asks for [output type]\"]\n- [A follow-up signal, e.g. \"user asks to refine or expand an earlier output\"]\n- [A context signal, e.g. \"a specific file type or folder is mentioned in the request\"]\n- [An implicit signal — what the user is trying to accomplish without naming the skill]\n\n\u003C!-- ══════════════════════════════════════════════════════════════════════════\n     SECTION 3 — INSTRUCTIONS\n     Purpose: Step-by-step execution guide for Cowork. Use numbered steps.\n     Each step: one verb + one outcome. No prose paragraphs. Decompose any\n     step that would exceed 2 lines into two steps.\n     Target: 5–10 numbered steps.\n     ══════════════════════════════════════════════════════════════════════════ -->\n## Instructions\n\n1. [First step — what Cowork reads or gathers before starting]\n2. [Second step — the core processing or analysis action]\n3. [Third step — how Cowork structures or organises the output]\n4. [Fourth step — quality check or refinement before delivering]\n5. [Fifth step — final delivery action or follow-up offer to the user]\n\n\u003C!-- ══════════════════════════════════════════════════════════════════════════\n     SECTION 4 — OUTPUT FORMAT\n     Purpose: Explicit structure Cowork must produce. Specify headings,\n     list shapes, table schemas, counts, and length targets. A reviewer\n     reading this section should be able to check the output without\n     re-reading the instructions. Target: 4–10 lines.\n     ══════════════════════════════════════════════════════════════════════════ -->\n## Output format\n\n[Opening line — the top-level structure, e.g. \"Numbered list of [N] items.\"]\n\nEach item follows this shape:\n\n- [Field 1 label]: [description of what goes here and its length target]\n- [Field 2 label]: [description of what goes here and its length target]\n\n[One line — any count constraint, e.g. \"Aim for [N]–[M] items unless the user specifies otherwise.\"]\n[One line — closing action Cowork takes after delivering, e.g. \"End with a note on which items seem most important.\"]\n\n\u003C!-- ══════════════════════════════════════════════════════════════════════════\n     SECTION 5 — QUALITY CRITERIA\n     Purpose: 3–5 checkable criteria a reviewer can evaluate as yes\u002Fno.\n     Each bullet is one line. If a criterion cannot be checked by reading\n     the output, rephrase it until it can. Target: 3–5 bullets.\n     ══════════════════════════════════════════════════════════════════════════ -->\n## Quality criteria\n\n- [Criterion 1 — a structural check, e.g. \"Output contains the required [element]\"]\n- [Criterion 2 — a content depth check, e.g. \"Each [item] includes [required detail]\"]\n- [Criterion 3 — a scope check, e.g. \"Output stays within [count\u002Flength] target\"]\n- [Criterion 4 — a user-value check, e.g. \"Output would be directly usable without editing\"]\n- [Criterion 5 — an edge-case check, optional; remove this bullet if 4 criteria are sufficient]\n\n\u003C!-- ══════════════════════════════════════════════════════════════════════════\n     SECTION 6 — ANTI-PATTERNS\n     Purpose: 3–5 common mistakes Cowork must not make. One line each.\n     Frame as \"what NOT to do.\" Do not repeat quality criteria negated —\n     anti-patterns should surface failure modes that a quality check would\n     miss. Target: 3–5 bullets.\n     ══════════════════════════════════════════════════════════════════════════ -->\n## Anti-patterns\n\n- [Anti-pattern 1 — a common structural mistake in this skill's output domain]\n- [Anti-pattern 2 — a scope or depth error, e.g. \"surface-level output that doesn't …\"]\n- [Anti-pattern 3 — a voice or format error, e.g. \"treating all [input types] as equivalent when …\"]\n- [Anti-pattern 4 — a process error, e.g. \"starting without reading [required input]\"]\n- [Anti-pattern 5 — optional; remove if 4 anti-patterns are sufficient]\n\n\u003C!-- ══════════════════════════════════════════════════════════════════════════\n     SECTION 7 — EXAMPLE\n     Purpose: ONE worked input→output pair. Use a real-looking, minimal\n     example — not a hypothetical. The input should be brief enough to\n     paste here (3–8 lines). The output should illustrate the full format\n     specified in §Output format (not a truncated sketch).\n     Contributor note: paste a real input and the ideal output you would\n     accept in a PR review. Do NOT write instructions to Cowork here.\n     Target: 15–40 lines total for this section.\n     ══════════════════════════════════════════════════════════════════════════ -->\n## Example\n\n**Input:**\n\n[Paste a real input here — e.g. a snippet of text, a user request, or a file excerpt\nthat represents the most common activation scenario for this skill.\nKeep it to 3–8 lines so the example remains scannable.]\n\n**Output:**\n\n[Paste the ideal output here — the response Cowork should produce for the input above.\nMatch the structure in §Output format exactly. Include all required fields\u002Fsections.\nAim for a complete output, not a \"...\" truncated sketch — reviewers need to see the\nreal shape, not a placeholder for it.\nRemove this parenthetical when you paste the actual example.]\n\n\u003C!-- ══════════════════════════════════════════════════════════════════════════\n     SECTION 8 — WRITING-PROFILE INTEGRATION\n     Purpose: One sentence stating WHEN this skill consults\n     context\u002Fwriting-profile.md, plus one concrete rule.\n     Per v1.2 ADR-013: if output ≥100 words, the skill must reference the\n     writing profile. If output is always \u003C100 words, say so explicitly.\n     Target: 1–4 lines.\n     ══════════════════════════════════════════════════════════════════════════ -->\n## Writing-profile integration\n\n[One sentence — when this skill reads context\u002Fwriting-profile.md, e.g.\n\"When output exceeds 100 words, Cowork consults context\u002Fwriting-profile.md\nand applies the user's stated tone, sentence-length preferences, and pet peeves.\"]\n[One concrete rule, e.g. \"If no writing profile exists, default to clear and direct prose.\" — or\n\"This skill produces structured data under 100 words; writing profile is not consulted.\"]\n\n\u003C!-- ══════════════════════════════════════════════════════════════════════════\n     SECTION 9 — EXAMPLE PROMPTS\n     Purpose: 3 realistic invocation phrases the user might type. These\n     appear in skills-as-prompts.md and inform global-instructions.md\n     trigger rules. Write prompts users actually say, not command syntax.\n     Target: exactly 3 bullets.\n     ══════════════════════════════════════════════════════════════════════════ -->\n## Example prompts\n\n- \"[A direct invocation phrase — the most common way a user requests this skill]\"\n- \"[A variation with a specific input — e.g. a file reference or a scope qualifier]\"\n- \"[A follow-up or edge-case invocation — a less obvious but valid request for this skill]\"\n\n\u003C!-- ADR-015 defines the canonical 9-section template and length budget.\n     CI (skill-depth-check, ADR-016) enforces a 60-line floor: SKILL.md files\n     in depth-enforced presets that fall below 60 lines will fail CI.\n     This template targets 80–120 lines; the soft cap is 150 lines.\n     Reference: docs\u002Farchitecture.md §ADR-015. -->\n",{},"main","3b46ce1bf0dafc2b8ad69a72e13e73aa538fb297","templates\u002Fskill-template",1,"https:\u002F\u002Fgithub.com\u002Fjmlozano1990\u002FCowork-Starter-Kit","https:\u002F\u002Fgithub.com\u002Fjmlozano1990\u002FCowork-Starter-Kit\u002Freleases\u002Flatest","https:\u002F\u002Fgithub.com\u002Fjmlozano1990","2026-11-01 23:54:10",{"source":7,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add jmlozano1990\u002FCowork-Starter-Kit --skill skill-template",{"tool":39,"command":40},"bunx","bunx skills add jmlozano1990\u002FCowork-Starter-Kit --skill skill-template",{"tool":42,"command":43},"pnpm","pnpm dlx skills add jmlozano1990\u002FCowork-Starter-Kit --skill skill-template","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjmlozano1990\u002FCowork-Starter-Kit\u002Fblob\u002Fmain\u002Ftemplates\u002Fskill-template\u002FSKILL.md",true,[],[48,58,67,75,83,92],{"skillNo":49,"name":50,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":20},"01M70FMH5856SZTHFW424V3KKV","my-shopping-helper","https:\u002F\u002Fgithub.com\u002Fjmlozano1990\u002FCowork-Starter-Kit\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fbrownfield\u002Fstale-skills\u002F.claude\u002Fskills\u002Fmy-shopping-helper\u002FSKILL.md",[],[54,55,56,57],"my shopping helper","my","helper","shopping",{"skillNo":59,"name":60,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":20},"01M70FMGA74PSF54WDPJ6DW74F","self-upgrade","https:\u002F\u002Fgithub.com\u002Fjmlozano1990\u002FCowork-Starter-Kit\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fbrownfield\u002Fmode-b\u002F.claude\u002Fskills\u002Fself-upgrade\u002FSKILL.md",[],[64,65,66],"self upgrade","self","upgrade",{"skillNo":68,"name":69,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":20},"01M70FMFER555AGCQMMABCGVP4","self-archive","https:\u002F\u002Fgithub.com\u002Fjmlozano1990\u002FCowork-Starter-Kit\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fbrownfield\u002Fmode-b\u002F.claude\u002Fskills\u002Fself-archive\u002FSKILL.md",[],[73,74,65],"archive","self archive",{"skillNo":76,"name":77,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":20},"01M70FMEKRATA5GX89TW5GTB62","self-apply","https:\u002F\u002Fgithub.com\u002Fjmlozano1990\u002FCowork-Starter-Kit\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fbrownfield\u002Fmode-b\u002F.claude\u002Fskills\u002Fself-apply\u002FSKILL.md",[],[81,82,65],"self apply","apply",{"skillNo":84,"name":85,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":20},"01M70FMDB1Z8JDVC1645B4PJFP","pull-updates","https:\u002F\u002Fgithub.com\u002Fjmlozano1990\u002FCowork-Starter-Kit\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fbrownfield\u002Fmode-b\u002F.claude\u002Fskills\u002Fpull-updates\u002FSKILL.md",[],[89,90,91],"pull updates","updates","pull",{"skillNo":93,"name":94,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":102,"publishedAt":20},"01M70FMCEMGNPHHRDPH3DXAYSW","email-drafting","https:\u002F\u002Fgithub.com\u002Fjmlozano1990\u002FCowork-Starter-Kit\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fbrownfield\u002Fmode-b\u002F.claude\u002Fskills\u002Femail-drafting\u002FSKILL.md",[97],{"categoryNo":98,"categoryName":99,"taxonomyType":100,"taxonomyTypeDesc":101},"01JBSEEDCAT000000000000005","邮件与沟通","SCENARIO","使用场景",[103,104,105],"email","drafting","email drafting"]