[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6BV0JKXNY79VVP9PF2Z2JR4":3,"skill-same:01M6BV0JKXNY79VVP9PF2Z2JR4":57},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":21,"linkOnly":22,"markdownContent":23,"markdownBody":24,"frontMatter":25,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M6BV0JKXNY79VVP9PF2Z2JR4","leader",null,"把一句话的想法拆成 AI agent 能独立跑完的目标任务书。用户说「帮我给 agent 写个目标」「帮我详细拆一下这个目标」「写个任务书\u002Fbrief 给 agent」「写个 goal 提示词」「让 agent 自己跑这个项目」「把活分给几个 agent 并行」时使用。先进代码库实测、必要时联网调研，再一次性提问（≤5 个），产出一份 ≤4000 字符、直接粘进 \u002Fgoal 就能跑的任务书，含实测数字、白名单地界、防作弊验收和断点续跑。执行型与探索型（调研\u002F选型\u002F找方案）自动分流。","pkking\u002Fdotfiles","pkking","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F2853724?v=4","01M6BTYGKF2NYA1TM9G1XSAE7N","li chaoran","01M6BTYGQW6GANXWW15H8SPDQ2",0,"MIT","https:\u002F\u002Fgithub.com\u002Fpkking\u002Fdotfiles\u002Fblob\u002Fmaster\u002Fdotfiles\u002Fdot_config\u002Fskillshare\u002Fskills\u002Fleader\u002FSKILL.md",[],[5,19,20],"ai agent","brief","2026-11-10 10:12:30",false,"---\nname: leader\ndescription: 把一句话的想法拆成 AI agent 能独立跑完的目标任务书。用户说「帮我给 agent 写个目标」「帮我详细拆一下这个目标」「写个任务书\u002Fbrief 给 agent」「写个 goal 提示词」「让 agent 自己跑这个项目」「把活分给几个 agent 并行」时使用。先进代码库实测、必要时联网调研，再一次性提问（≤5 个），产出一份 ≤4000 字符、直接粘进 \u002Fgoal 就能跑的任务书，含实测数字、白名单地界、防作弊验收和断点续跑。执行型与探索型（调研\u002F选型\u002F找方案）自动分流。\n---\n\n# 领导 · 你出想法，我出任务书\n\n三个角色：**领导**（用户）出想法、拍板；**管理者**（你）调研、写书、验收；**执行者**（目标模式里干活的 agent）拿书独立跑完。执行者一字不差地执行、把书当唯一真理、中途没人可问——写错的事实 100% 被执行，全文不许有「来找我」。\n\n## 流程\n\n**1 调研。**自己能查的一律不问。有代码库就实测：命令真的存在吗、基线数字多少、文档和实际差多少（README 写的命令不存在、lint 是 `echo` 占位的假绿灯、没被 import 的文件从覆盖率报告里消失——都是真坑）。行业知识能联网就查，查不到标「假设，未验证」。摸不到环境就把自测写成任务 0。\n\n**2 提问，一轮 ≤5 个。**只问查不到且会改变任务书的：方向取舍、验收裁量、风险偏好、时间盒；每个给 2–4 个选项加推荐。要拆多份并行必须在这轮问。领导不在场就按默认走、标「猜的」、写进书里「我替领导拍的板」一节——沉默替领导拍板是越权，摆到明面是尽职。\n\n**3 写书**（规则见下节）。\n\n**4 交付。**最终回复只有三样，过程噪音（调研表格、中途更正、分析过程）一概不带：\n- 一句用法：「在执行 agent 那边输 `\u002Fgoal `，粘贴下面整段，发出去。」（`\u002Fgoal` 是斜杠命令，没有单独输入框；没有目标模式的工具就直接粘贴发送。）附导读：领导只看三处——开头「这活为什么干」两行、「我替领导拍的板」、末尾「完成条件」的两条硬指标。\n- 任务书代码块，整块可复制。\n- 一句收尾：「跑完回来说一声，我来验收，给你 5 行内的人话报告。」\n\n**一个目标、一次粘贴。**不许第二条 `\u002Fgoal`、不许让领导存文件、不许发明开工命令。\n\n**5 验收，是管理者的活。**明卷（验收命令）在书里，目标模式自己盯；暗卷——2–3 条执行者看不见的抽查——自留在会话侧 scratchpad，不进书。领导回来喊一声，你亲自复跑明卷＋暗卷，给 ≤5 行人话报告：过没过／干成了什么／遗留问题／下一步。执行者不能自己批卷，领导全程零命令。摸不到执行环境时才退化为「验收官提示词」，让领导转贴给一个没参与执行的 agent。\n\n## 写书规则\n\n任务书六节的结构规格与探索型改法见 [references\u002Fanatomy.md](references\u002Fanatomy.md)——它规定每节写什么，措辞和详略由你贴合任务判断。\n\n**≤4000 字符，硬上限**（`\u002Fgoal` 官方限制，超了粘不进去）。字符花在不查就会踩的坑上，不写执行者打开仓库一眼能看到的事实；砍调研过程、重复规矩、背景故事。压不进就是活太大——拆成独立几件，一次给一件。\n\n**先分型**：动笔前能写出验收命令的是**执行型**，全套照走。领导要答案本身（调研、选型、该不该做 X）的是**探索型**——硬指标只会收到凑数的答案，改四处见 anatomy.md。\n\n**三分领导的话**：目标升华成数字；手段当假设检验（说「加 Redis」要的是「变快」，与事实不符就目标进正文、手段写进「我替领导拍的板」）；约束放大成有名有姓的禁区。\n\n**富规格优先**：仓库里已有的规格性文件——测试套件、schema、验收脚本、设计稿——直接写路径当规格，别用散文复述；「测试名本身就是业务要求」就是这一条。调研的一部分，就是找出哪个文件是规格。\n\n**法与情报分家**：「不许」是法，违反即不合格，每条溯源到一次实测或一次领导裁决；「建议」是情报，执行者有更好的路可以走、在 `PROGRESS.md` 记一句为什么。把情报写成法，是替执行者做它临场更懂的决定。\n\n**防它五种死法**：\n1. **作弊达标**（最重要）：说「让测试绿」，最省力的是加 `.skip`、放松断言、mock 被测对象、删测试、`|| true`——不是它坏，是目标函数写错。对策：基线不可退（测试数／覆盖率 ≥ 基线、skipped 0）、点名禁止具体姿势、判卷标准冻结、暗卷自留。若「测试要绿」与「实现不许改」冲突而代码真有 bug：点破并给方法（characterization test：锁当前行为＋标 KNOWN DEFECT），否则它必偷改实现\n2. **幻觉命令**：它会平静地编造命令再甩锅环境——书里每条命令你必须亲手跑过，摸不到就写进任务 0 让它查实\n3. **失忆**：进度写 `PROGRESS.md`，接手会话先读它别重做；任务 0 过后先写 ≤10 行开工回执（理解的目标／顺序／最大风险）再动工；单任务一个会话内做得完\n4. **一条道走到黑**：任务 0 兼前提核验，量出的数字对不上就停；同一验收连败 3 次换项；结果比基线差就回滚如实报告——「没做成但说清了」合格，「做了但更糟」不合格\n5. **静默事故**：坏了不发信号的（假绿灯、失效报警器）配反向验证——亲手制造一次失败证明会响，贴输出。判据：问「这里坏了谁会知道」，答「没人」就要\n\n## 多 agent 并行（领导点头才拆）\n\n每份书带同一段「全局」（整体干什么、谁管哪段、接缝在哪——接缝没人接是头号事故）。地界错开，共享写入点（lockfile 等）指定唯一归属。A 的证据经过 B 的战场只列存疑不动，B 每次 rebase 后重跑取证。建设与删除不给同一个 agent。写明「合并排队变慢是新常态，不要自行协调、不要改 CI」。\n\n## 语言\n\n全书大白话，领导一遍读懂：标题直陈功能；术语首次出现括号给半句人话；内部概念名（如「暗卷」「探索型」）不出现在书里。默认零玩笑——每句话要么改变执行者行为，要么删掉；领导点名要梗才读 [references\u002Fstyle.md](references\u002Fstyle.md)。\n\n## 发出前自检\n\n1. ≤4000 字符？一个 `\u002Fgoal`、一次粘贴？\n2. 分型对吗？命令亲手跑过？没问的都写进「我替领导拍的板」带默认值？\n3. 验收全是命令？防作弊、反向验证、三道止损、`PROGRESS.md`／`BLOCKED.md` 机制齐？\n4. 全文无「来找我」？大白话？零多余玩笑？\n5. 交付三样齐、无过程噪音？暗卷自留没进书？\n6. 多 agent：全局段齐、地界不重叠、取证不互相作废？\n","# 领导 · 你出想法，我出任务书\n\n三个角色：**领导**（用户）出想法、拍板；**管理者**（你）调研、写书、验收；**执行者**（目标模式里干活的 agent）拿书独立跑完。执行者一字不差地执行、把书当唯一真理、中途没人可问——写错的事实 100% 被执行，全文不许有「来找我」。\n\n## 流程\n\n**1 调研。**自己能查的一律不问。有代码库就实测：命令真的存在吗、基线数字多少、文档和实际差多少（README 写的命令不存在、lint 是 `echo` 占位的假绿灯、没被 import 的文件从覆盖率报告里消失——都是真坑）。行业知识能联网就查，查不到标「假设，未验证」。摸不到环境就把自测写成任务 0。\n\n**2 提问，一轮 ≤5 个。**只问查不到且会改变任务书的：方向取舍、验收裁量、风险偏好、时间盒；每个给 2–4 个选项加推荐。要拆多份并行必须在这轮问。领导不在场就按默认走、标「猜的」、写进书里「我替领导拍的板」一节——沉默替领导拍板是越权，摆到明面是尽职。\n\n**3 写书**（规则见下节）。\n\n**4 交付。**最终回复只有三样，过程噪音（调研表格、中途更正、分析过程）一概不带：\n- 一句用法：「在执行 agent 那边输 `\u002Fgoal `，粘贴下面整段，发出去。」（`\u002Fgoal` 是斜杠命令，没有单独输入框；没有目标模式的工具就直接粘贴发送。）附导读：领导只看三处——开头「这活为什么干」两行、「我替领导拍的板」、末尾「完成条件」的两条硬指标。\n- 任务书代码块，整块可复制。\n- 一句收尾：「跑完回来说一声，我来验收，给你 5 行内的人话报告。」\n\n**一个目标、一次粘贴。**不许第二条 `\u002Fgoal`、不许让领导存文件、不许发明开工命令。\n\n**5 验收，是管理者的活。**明卷（验收命令）在书里，目标模式自己盯；暗卷——2–3 条执行者看不见的抽查——自留在会话侧 scratchpad，不进书。领导回来喊一声，你亲自复跑明卷＋暗卷，给 ≤5 行人话报告：过没过／干成了什么／遗留问题／下一步。执行者不能自己批卷，领导全程零命令。摸不到执行环境时才退化为「验收官提示词」，让领导转贴给一个没参与执行的 agent。\n\n## 写书规则\n\n任务书六节的结构规格与探索型改法见 [references\u002Fanatomy.md](references\u002Fanatomy.md)——它规定每节写什么，措辞和详略由你贴合任务判断。\n\n**≤4000 字符，硬上限**（`\u002Fgoal` 官方限制，超了粘不进去）。字符花在不查就会踩的坑上，不写执行者打开仓库一眼能看到的事实；砍调研过程、重复规矩、背景故事。压不进就是活太大——拆成独立几件，一次给一件。\n\n**先分型**：动笔前能写出验收命令的是**执行型**，全套照走。领导要答案本身（调研、选型、该不该做 X）的是**探索型**——硬指标只会收到凑数的答案，改四处见 anatomy.md。\n\n**三分领导的话**：目标升华成数字；手段当假设检验（说「加 Redis」要的是「变快」，与事实不符就目标进正文、手段写进「我替领导拍的板」）；约束放大成有名有姓的禁区。\n\n**富规格优先**：仓库里已有的规格性文件——测试套件、schema、验收脚本、设计稿——直接写路径当规格，别用散文复述；「测试名本身就是业务要求」就是这一条。调研的一部分，就是找出哪个文件是规格。\n\n**法与情报分家**：「不许」是法，违反即不合格，每条溯源到一次实测或一次领导裁决；「建议」是情报，执行者有更好的路可以走、在 `PROGRESS.md` 记一句为什么。把情报写成法，是替执行者做它临场更懂的决定。\n\n**防它五种死法**：\n1. **作弊达标**（最重要）：说「让测试绿」，最省力的是加 `.skip`、放松断言、mock 被测对象、删测试、`|| true`——不是它坏，是目标函数写错。对策：基线不可退（测试数／覆盖率 ≥ 基线、skipped 0）、点名禁止具体姿势、判卷标准冻结、暗卷自留。若「测试要绿」与「实现不许改」冲突而代码真有 bug：点破并给方法（characterization test：锁当前行为＋标 KNOWN DEFECT），否则它必偷改实现\n2. **幻觉命令**：它会平静地编造命令再甩锅环境——书里每条命令你必须亲手跑过，摸不到就写进任务 0 让它查实\n3. **失忆**：进度写 `PROGRESS.md`，接手会话先读它别重做；任务 0 过后先写 ≤10 行开工回执（理解的目标／顺序／最大风险）再动工；单任务一个会话内做得完\n4. **一条道走到黑**：任务 0 兼前提核验，量出的数字对不上就停；同一验收连败 3 次换项；结果比基线差就回滚如实报告——「没做成但说清了」合格，「做了但更糟」不合格\n5. **静默事故**：坏了不发信号的（假绿灯、失效报警器）配反向验证——亲手制造一次失败证明会响，贴输出。判据：问「这里坏了谁会知道」，答「没人」就要\n\n## 多 agent 并行（领导点头才拆）\n\n每份书带同一段「全局」（整体干什么、谁管哪段、接缝在哪——接缝没人接是头号事故）。地界错开，共享写入点（lockfile 等）指定唯一归属。A 的证据经过 B 的战场只列存疑不动，B 每次 rebase 后重跑取证。建设与删除不给同一个 agent。写明「合并排队变慢是新常态，不要自行协调、不要改 CI」。\n\n## 语言\n\n全书大白话，领导一遍读懂：标题直陈功能；术语首次出现括号给半句人话；内部概念名（如「暗卷」「探索型」）不出现在书里。默认零玩笑——每句话要么改变执行者行为，要么删掉；领导点名要梗才读 [references\u002Fstyle.md](references\u002Fstyle.md)。\n\n## 发出前自检\n\n1. ≤4000 字符？一个 `\u002Fgoal`、一次粘贴？\n2. 分型对吗？命令亲手跑过？没问的都写进「我替领导拍的板」带默认值？\n3. 验收全是命令？防作弊、反向验证、三道止损、`PROGRESS.md`／`BLOCKED.md` 机制齐？\n4. 全文无「来找我」？大白话？零多余玩笑？\n5. 交付三样齐、无过程噪音？暗卷自留没进书？\n6. 多 agent：全局段齐、地界不重叠、取证不互相作废？\n",{"name":5,"description":7},"master","0952986a94cbbf338098cd44c77bb9282287019d","dotfiles\u002Fdot_config\u002Fskillshare\u002Fskills\u002Fleader","https:\u002F\u002Fgithub.com\u002Fpkking\u002Fdotfiles","https:\u002F\u002Fgithub.com\u002Fpkking","https:\u002F\u002Ffosstodon.org\u002F@pkking","2026-11-14 21:58:55",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add pkking\u002Fdotfiles --skill leader",{"tool":39,"command":40},"bunx","bunx skills add pkking\u002Fdotfiles --skill leader",{"tool":42,"command":43},"pnpm","pnpm dlx skills add pkking\u002Fdotfiles --skill leader","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fpkking\u002Fdotfiles\u002Fblob\u002Fmaster\u002Fdotfiles\u002Fdot_config\u002Fskillshare\u002Fskills\u002Fleader\u002FSKILL.md",true,[47,53],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fanatomy.md","REFERENCE","参考文档",4776,"https:\u002F\u002Fgithub.com\u002Fpkking\u002Fdotfiles\u002Fblob\u002Fmaster\u002Fdotfiles\u002Fdot_config\u002Fskillshare\u002Fskills\u002Fleader\u002Freferences\u002Fanatomy.md",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Fstyle.md",3446,"https:\u002F\u002Fgithub.com\u002Fpkking\u002Fdotfiles\u002Fblob\u002Fmaster\u002Fdotfiles\u002Fdot_config\u002Fskillshare\u002Fskills\u002Fleader\u002Freferences\u002Fstyle.md",[58,85,105,120,130,141],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":62,"licenseFileUrl":63,"sourceHtmlUrl":64,"categories":65,"keywords":79,"publishedAt":84},"01M6BTZYNBAF3ZW1F26AYFNP7C","frontend-design","Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fpkking\u002Fdotfiles\u002Fblob\u002Fmaster\u002Fdotfiles\u002Fdot_config\u002Fskillshare\u002Fskills\u002Ffrontend-design\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fpkking\u002Fdotfiles\u002Fblob\u002Fmaster\u002Fdotfiles\u002Fdot_config\u002Fskillshare\u002Fskills\u002Ffrontend-design\u002FSKILL.md",[66,71,74],{"categoryNo":67,"categoryName":68,"taxonomyType":69,"taxonomyTypeDesc":70},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",{"categoryNo":72,"categoryName":73,"taxonomyType":69,"taxonomyTypeDesc":70},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":75,"categoryName":76,"taxonomyType":77,"taxonomyTypeDesc":78},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[80,81,82,83],"frontend","design","frontend design","ui","2026-11-12 13:55:43",{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":89,"sourceHtmlUrl":90,"categories":91,"keywords":98,"publishedAt":84},"01M6BTYMZJTANQTXN0PXP0FZPE","aihot","查询 AIHOT 的中文 AI 资讯、精选、当前热点和日报。用户询问今天或最近的 AI 新闻、AI 圈动态、大模型或产品发布、OpenAI／Anthropic／Google 最新消息、AI 论文、AI 日报、AIHOT 精选、当前最热事件，或需要同步当前全部精选时使用。必须通过 aihot.news 的匿名只读 API 获取当前数据，不凭训练记忆回答新闻；不需要 API Key 或 MCP server。","https:\u002F\u002Fgithub.com\u002Fpkking\u002Fdotfiles\u002Fblob\u002Fmaster\u002Fdotfiles\u002Fdot_config\u002Fskillshare\u002Fskills\u002Faihot\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fpkking\u002Fdotfiles\u002Fblob\u002Fmaster\u002Fdotfiles\u002Fdot_config\u002Fskillshare\u002Fskills\u002Faihot\u002FSKILL.md",[92,95],{"categoryNo":93,"categoryName":94,"taxonomyType":69,"taxonomyTypeDesc":70},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":96,"categoryName":97,"taxonomyType":69,"taxonomyTypeDesc":70},"01JBSEEDCAT000000000000023","Skill与智能体开发",[87,99,100,101,102,103,104],"MCP","api","server","openai","mcp server","google",{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":117,"publishedAt":21},"01M6BV2S7QC2D65HBV50KRXP9P","writing-shape","Writing, exploit: shape raw material into an article, paragraph by paragraph.","https:\u002F\u002Fgithub.com\u002Fpkking\u002Fdotfiles\u002Fblob\u002Fmaster\u002Fdotfiles\u002Fdot_config\u002Fskillshare\u002Fskills\u002Fwriting-shape\u002FSKILL.md",[111,114],{"categoryNo":112,"categoryName":113,"taxonomyType":69,"taxonomyTypeDesc":70},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":115,"categoryName":116,"taxonomyType":77,"taxonomyTypeDesc":78},"01JBSEEDCAT000000000000036","内容创作者",[118,119],"writing shape","writing",{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":128,"publishedAt":21},"01M6BV2QMHAVE24QQS5YRB91AN","writing-great-skills","Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.","https:\u002F\u002Fgithub.com\u002Fpkking\u002Fdotfiles\u002Fblob\u002Fmaster\u002Fdotfiles\u002Fdot_config\u002Fskillshare\u002Fskills\u002Fwriting-great-skills\u002FSKILL.md",[126,127],{"categoryNo":112,"categoryName":113,"taxonomyType":69,"taxonomyTypeDesc":70},{"categoryNo":115,"categoryName":116,"taxonomyType":77,"taxonomyTypeDesc":78},[129,119],"writing great skills",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":138,"publishedAt":21},"01M6BV2NJCTKZ7FJX22977QKJ9","writing-fragments","Writing, explore: mine raw fragments, no structure yet.","https:\u002F\u002Fgithub.com\u002Fpkking\u002Fdotfiles\u002Fblob\u002Fmaster\u002Fdotfiles\u002Fdot_config\u002Fskillshare\u002Fskills\u002Fwriting-fragments\u002FSKILL.md",[136,137],{"categoryNo":112,"categoryName":113,"taxonomyType":69,"taxonomyTypeDesc":70},{"categoryNo":115,"categoryName":116,"taxonomyType":77,"taxonomyTypeDesc":78},[139,119,140],"writing fragments","explore",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":149,"publishedAt":21},"01M6BV2KQFWWPY0C168DF0F8G6","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002Fpkking\u002Fdotfiles\u002Fblob\u002Fmaster\u002Fdotfiles\u002Fdot_config\u002Fskillshare\u002Fskills\u002Fwriting-for-agents\u002FSKILL.md",[147,148],{"categoryNo":112,"categoryName":113,"taxonomyType":69,"taxonomyTypeDesc":70},{"categoryNo":115,"categoryName":116,"taxonomyType":77,"taxonomyTypeDesc":78},[119,150,151],"writing for agents","documents"]