[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6J19Q42KW26AGS4TRJCFSWK":3,"skill-same:01M6J19Q42KW26AGS4TRJCFSWK":75},{"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":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":53,"commitSha":54,"skillDirectory":55,"forksCount":56,"repositoryHtmlUrl":57,"repositoryHomepageUrl":6,"ownerHtmlUrl":58,"ownerBlogUrl":59,"ownerDescription":6,"updatedAt":60,"install":61,"resources":74},"01M6J19Q42KW26AGS4TRJCFSWK","cli-e2e-testcase-writer",null,"Use when adding or updating Go CLI E2E coverage for one `tests\u002Fcli_e2e\u002F{domain}` domain of the compiled `lark-cli`, especially when the work requires live `--help` or `schema` exploration, scenario-based `clie2e.RunCmd` workflows, and per-domain `coverage.md` maintenance.","larksuite\u002Fcli","larksuite","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F54944174?v=4","01M6J14VT8GJAN67PYPEJG4B7W","Lark Technologies Pte. Ltd.","01M6J14VYWNDEHZTM1T14EN0XD",18111,"MIT","https:\u002F\u002Fgithub.com\u002Flarksuite\u002Fcli\u002Fblob\u002Fmain\u002Ftests\u002Fcli_e2e\u002Fcli-e2e-testcase-writer\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"cli e2e testcase writer","e2e","cli","writer","exploration","when","for","scenario","tests","live","domain","lark","maintenance","schema","use","coverage","work","help","workflows","go","2026-11-10 10:12:30",false,"---\nname: cli-e2e-testcase-writer\ndescription: Use when adding or updating Go CLI E2E coverage for one `tests\u002Fcli_e2e\u002F{domain}` domain of the compiled `lark-cli`, especially when the work requires live `--help` or `schema` exploration, scenario-based `clie2e.RunCmd` workflows, and per-domain `coverage.md` maintenance.\nmetadata:\n  requires:\n    bins: [\"lark-cli\"]\n---\n\n# CLI E2E Testcase Writer\n\nWork on one domain per run. Produce exactly two artifacts for that domain:\n- workflow testcase files under `tests\u002Fcli_e2e\u002F{domain}\u002F`\n- `tests\u002Fcli_e2e\u002F{domain}\u002Fcoverage.md`\n\nFocus on domain testcase files. Do not change shared E2E support code such as `tests\u002Fcli_e2e\u002Fcore.go` unless the user explicitly asks. Treat `tests\u002Fcli_e2e\u002Fdemo\u002F` as reference only.\n\n## Core standard\n\n- Make the testcase scenario-based and self-contained.\n- Prove one workflow end to end: create plus follow-up read, or mutate plus teardown.\n- Prefer one file per workflow or one closely related feature.\n- For mutable flows, prove persisted state with read-after-write assertions, not just exit code.\n- Leave prerequisite-heavy paths uncovered when they cannot be proven, and explain why in `coverage.md`.\n\n## Workflow\n\n### 1. Explore the live CLI before writing code\n\n```bash\nlark-cli --help\nlark-cli \u003Cdomain> --help\nlark-cli \u003Cdomain> +\u003Cshortcut> -h\nlark-cli \u003Cdomain> \u003Cgroup> --help\nlark-cli \u003Cdomain> \u003Cgroup> \u003Cmethod> -h\nlark-cli schema \u003Cdomain>.\u003Cgroup>.\u003Cmethod>\n```\n\n### 2. Count leaf commands for the denominator\n\n- A leaf command is one that executes an action — it has no further subcommands.\n- If `lark-cli \u003Cdomain> \u003Cgroup> --help` lists no subcommands, `\u003Cgroup>` itself is the leaf.\n- Count `task +create` as one leaf and `task tasks get` as one leaf.\n- Do not count parameter combinations.\n- Reuse coverage already present under `tests\u002Fcli_e2e\u002F{domain}\u002F`. Do not count `tests\u002Fcli_e2e\u002Fdemo\u002F`.\n\n### 3. Choose the proof surface before editing\n\nIdentify the provable risks for the touched workflow: invalid input, missing prerequisite, identity or permission, state transition, output shape, cleanup safety. If only the happy path is testable, document the blocked risk areas in `coverage.md`.\n\n### 4. Add or update the workflow testcase\n\n- Use `clie2e.RunCmd(ctx, clie2e.Request{...})`.\n- Put command path and plain flags in `Args`; put JSON in `Params` (URL\u002Fpath parameters) and `Data` (request body).\n- Prefer one top-level test per workflow with `t.Run` substeps.\n- Register teardown on `parentT.Cleanup` so it survives subtest failures.\n- When touching an existing command, verify the JSON response shape is stable: assert status type, field paths, and identifiers consumed by later steps before changing assertions.\n\n### 5. Run and iterate\n\nRun `go test .\u002Ftests\u002Fcli_e2e\u002F{domain} -count=1` while iterating and before finishing. If command shape or behavior is unclear, re-check help or schema (step 1) before changing assertions.\n\n### 6. Refresh the domain outputs\n\n- Update the workflow testcase files.\n- Update `coverage.md`: recompute the denominator from live help output, mark each command as `shortcut` or `api`, and keep one command table for the whole domain.\n\n## Testcase rules\n\n- Override `BinaryPath`, `DefaultAs`, or `Format` on `clie2e.Request` only when the testcase truly needs it.\n- Use `require.NoError`, `result.AssertExitCode`, `result.AssertStdoutStatus`, `assert`, and `gjson`.\n- Shortcut responses (`{ok: bool}`) assert `true`; API responses (`{code: int}`) assert `0`.\n- Use `t.Helper()` only for setup or assertion helpers that are called from multiple tests.\n- Use table-driven tests only when the scenario shape repeats across inputs.\n- For expected failures, assert stderr content and exit code when the environment makes them deterministic.\n- If identity or external fixtures cannot be proven, leave the command uncovered and document the prerequisite rather than faking confidence.\n\n## coverage.md\n\nKeep `coverage.md` brief and mechanical. Include:\n- a domain-specific H1 title\n- a metrics section with denominator, covered count, and coverage rate\n- a summary section restating each `Test...` workflow, key `t.Run(...)` proof points, and main blockers\n- one command table for all commands\n\nRecommended structure:\n\n```markdown\n# \u003CDomain> CLI E2E Coverage\n\n## Metrics\n- Denominator: N leaf commands\n- Covered: N\n- Coverage: N%\n\n## Summary\n- TestXxx: ... key `t.Run(...)` proof points ...\n- Blocked area: ...\n\n## Command Table\n| Status | Cmd | Type | Testcase | Key parameter shapes | Notes \u002F uncovered reason |\n| --- | --- | --- | --- | --- | --- |\n| ✓ | task +create | shortcut | task_status_workflow_test.go::TestTask_StatusWorkflow | basic create; create with due | |\n| ✕ | task +assign | shortcut |  | none | requires real user open_id |\n```\n\n- Mark each command `shortcut` or `api`.\n- Write testcase entries in `go test -run` friendly form.\n- Commands only exercised in `parentT.Cleanup` teardown are not counted as covered.\n- Do not split covered and uncovered commands into separate sections.\n\n## Guardrails\n\n- Run as bot identity only; do not assume `--as user` works.\n- Do not place new real coverage under `tests\u002Fcli_e2e\u002Fdemo\u002F`.\n- Do not depend on preexisting remote data.\n- Do not fabricate open_ids, chats, docs, or other remote fixtures.\n- Prefer deterministic negative cases over tenant-dependent assertions.\n- Do not guess `Params` or `Data` fields when help or schema can tell you the exact shape.\n- Do not hardcode obvious defaults unless the command truly requires explicit flags.\n- Do not put agent, model, or vendor brand names in visible remote test data; use neutral prefixes such as `lark-cli-e2e-` or `\u003Cdomain>-e2e-`.\n- A command is covered only when the testcase asserts returned fields or persisted state, not just exit code.\n- Cleanup-only execution is not primary coverage, except `delete` in the same workflow that created the resource.\n","# CLI E2E Testcase Writer\n\nWork on one domain per run. Produce exactly two artifacts for that domain:\n- workflow testcase files under `tests\u002Fcli_e2e\u002F{domain}\u002F`\n- `tests\u002Fcli_e2e\u002F{domain}\u002Fcoverage.md`\n\nFocus on domain testcase files. Do not change shared E2E support code such as `tests\u002Fcli_e2e\u002Fcore.go` unless the user explicitly asks. Treat `tests\u002Fcli_e2e\u002Fdemo\u002F` as reference only.\n\n## Core standard\n\n- Make the testcase scenario-based and self-contained.\n- Prove one workflow end to end: create plus follow-up read, or mutate plus teardown.\n- Prefer one file per workflow or one closely related feature.\n- For mutable flows, prove persisted state with read-after-write assertions, not just exit code.\n- Leave prerequisite-heavy paths uncovered when they cannot be proven, and explain why in `coverage.md`.\n\n## Workflow\n\n### 1. Explore the live CLI before writing code\n\n```bash\nlark-cli --help\nlark-cli \u003Cdomain> --help\nlark-cli \u003Cdomain> +\u003Cshortcut> -h\nlark-cli \u003Cdomain> \u003Cgroup> --help\nlark-cli \u003Cdomain> \u003Cgroup> \u003Cmethod> -h\nlark-cli schema \u003Cdomain>.\u003Cgroup>.\u003Cmethod>\n```\n\n### 2. Count leaf commands for the denominator\n\n- A leaf command is one that executes an action — it has no further subcommands.\n- If `lark-cli \u003Cdomain> \u003Cgroup> --help` lists no subcommands, `\u003Cgroup>` itself is the leaf.\n- Count `task +create` as one leaf and `task tasks get` as one leaf.\n- Do not count parameter combinations.\n- Reuse coverage already present under `tests\u002Fcli_e2e\u002F{domain}\u002F`. Do not count `tests\u002Fcli_e2e\u002Fdemo\u002F`.\n\n### 3. Choose the proof surface before editing\n\nIdentify the provable risks for the touched workflow: invalid input, missing prerequisite, identity or permission, state transition, output shape, cleanup safety. If only the happy path is testable, document the blocked risk areas in `coverage.md`.\n\n### 4. Add or update the workflow testcase\n\n- Use `clie2e.RunCmd(ctx, clie2e.Request{...})`.\n- Put command path and plain flags in `Args`; put JSON in `Params` (URL\u002Fpath parameters) and `Data` (request body).\n- Prefer one top-level test per workflow with `t.Run` substeps.\n- Register teardown on `parentT.Cleanup` so it survives subtest failures.\n- When touching an existing command, verify the JSON response shape is stable: assert status type, field paths, and identifiers consumed by later steps before changing assertions.\n\n### 5. Run and iterate\n\nRun `go test .\u002Ftests\u002Fcli_e2e\u002F{domain} -count=1` while iterating and before finishing. If command shape or behavior is unclear, re-check help or schema (step 1) before changing assertions.\n\n### 6. Refresh the domain outputs\n\n- Update the workflow testcase files.\n- Update `coverage.md`: recompute the denominator from live help output, mark each command as `shortcut` or `api`, and keep one command table for the whole domain.\n\n## Testcase rules\n\n- Override `BinaryPath`, `DefaultAs`, or `Format` on `clie2e.Request` only when the testcase truly needs it.\n- Use `require.NoError`, `result.AssertExitCode`, `result.AssertStdoutStatus`, `assert`, and `gjson`.\n- Shortcut responses (`{ok: bool}`) assert `true`; API responses (`{code: int}`) assert `0`.\n- Use `t.Helper()` only for setup or assertion helpers that are called from multiple tests.\n- Use table-driven tests only when the scenario shape repeats across inputs.\n- For expected failures, assert stderr content and exit code when the environment makes them deterministic.\n- If identity or external fixtures cannot be proven, leave the command uncovered and document the prerequisite rather than faking confidence.\n\n## coverage.md\n\nKeep `coverage.md` brief and mechanical. Include:\n- a domain-specific H1 title\n- a metrics section with denominator, covered count, and coverage rate\n- a summary section restating each `Test...` workflow, key `t.Run(...)` proof points, and main blockers\n- one command table for all commands\n\nRecommended structure:\n\n```markdown\n# \u003CDomain> CLI E2E Coverage\n\n## Metrics\n- Denominator: N leaf commands\n- Covered: N\n- Coverage: N%\n\n## Summary\n- TestXxx: ... key `t.Run(...)` proof points ...\n- Blocked area: ...\n\n## Command Table\n| Status | Cmd | Type | Testcase | Key parameter shapes | Notes \u002F uncovered reason |\n| --- | --- | --- | --- | --- | --- |\n| ✓ | task +create | shortcut | task_status_workflow_test.go::TestTask_StatusWorkflow | basic create; create with due | |\n| ✕ | task +assign | shortcut |  | none | requires real user open_id |\n```\n\n- Mark each command `shortcut` or `api`.\n- Write testcase entries in `go test -run` friendly form.\n- Commands only exercised in `parentT.Cleanup` teardown are not counted as covered.\n- Do not split covered and uncovered commands into separate sections.\n\n## Guardrails\n\n- Run as bot identity only; do not assume `--as user` works.\n- Do not place new real coverage under `tests\u002Fcli_e2e\u002Fdemo\u002F`.\n- Do not depend on preexisting remote data.\n- Do not fabricate open_ids, chats, docs, or other remote fixtures.\n- Prefer deterministic negative cases over tenant-dependent assertions.\n- Do not guess `Params` or `Data` fields when help or schema can tell you the exact shape.\n- Do not hardcode obvious defaults unless the command truly requires explicit flags.\n- Do not put agent, model, or vendor brand names in visible remote test data; use neutral prefixes such as `lark-cli-e2e-` or `\u003Cdomain>-e2e-`.\n- A command is covered only when the testcase asserts returned fields or persisted state, not just exit code.\n- Cleanup-only execution is not primary coverage, except `delete` in the same workflow that created the resource.\n",{"name":5,"metadata":49,"description":7},{"requires":50},{"bins":51},[52],"lark-cli","main","f31194b461afbd75479d12850b0f9cb9427cb762","tests\u002Fcli_e2e\u002Fcli-e2e-testcase-writer",1377,"https:\u002F\u002Fgithub.com\u002Flarksuite\u002Fcli","https:\u002F\u002Fgithub.com\u002Flarksuite","https:\u002F\u002Fwww.larksuite.com","2026-11-13 17:28:43",{"source":8,"skillName":5,"commands":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add larksuite\u002Fcli --skill cli-e2e-testcase-writer",{"tool":67,"command":68},"bunx","bunx skills add larksuite\u002Fcli --skill cli-e2e-testcase-writer",{"tool":70,"command":71},"pnpm","pnpm dlx skills add larksuite\u002Fcli --skill cli-e2e-testcase-writer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flarksuite\u002Fcli\u002Fblob\u002Fmain\u002Ftests\u002Fcli_e2e\u002Fcli-e2e-testcase-writer\u002FSKILL.md",true,[],[76,94,113,132,146,159],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":44},"01M6J19MNSEQ2WHAJWS9WDXEYC","lark-workflow-standup-report","日程待办摘要：编排 calendar +agenda 和 task +get-my-tasks，生成指定日期的日程与未完成任务摘要。适用于了解今天\u002F明天\u002F本周的安排。","https:\u002F\u002Fgithub.com\u002Flarksuite\u002Fcli\u002Fblob\u002Fmain\u002Fskills\u002Flark-workflow-standup-report\u002FSKILL.md",[],[83,84,85,86,35,26,87,88,89,90,91,92,93],"workflow","report","standup","lark workflow standup report","tasks","生成","calendar","task","get","agenda","my",{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":105,"publishedAt":44},"01M6J19JDF05PZ4WMAWKYSMPFP","lark-workflow-meeting-summary","会议纪要整理工作流：汇总指定时间范围内的会议纪要并生成结构化报告。当用户需要整理会议纪要、生成会议周报、回顾一段时间内的会议内容时使用。","https:\u002F\u002Fgithub.com\u002Flarksuite\u002Fcli\u002Fblob\u002Fmain\u002Fskills\u002Flark-workflow-meeting-summary\u002FSKILL.md",[100],{"categoryNo":101,"categoryName":102,"taxonomyType":103,"taxonomyTypeDesc":104},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[83,106,107,35,108,109,26,88,110,111,112],"lark workflow meeting summary","summary","meeting summary","meeting","定时","整理","报告",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":44},"01M6J19E0H30T9JRKFXYPDPMTQ","lark-wiki","飞书知识库：管理知识空间、空间成员和文档节点。创建和查询知识空间、查看和管理空间成员、管理节点层级结构、在知识库中组织文档和快捷方式。当用户需要在知识库中查找或创建文档、浏览知识空间结构、查看或管理空间成员、移动或复制节点时使用。当用户给出 doubao.com 的 \u002Fwiki\u002F URL\u002Ftoken 时，也应直接使用本 skill，不要因为域名不是飞书而回退到 WebFetch；路由依据是 URL 路径模式和 token，而不是域名。不负责：上传文件到知识库节点下（走 lark-drive）、编辑文档\u002F表格\u002FBase 内容（走 lark-doc \u002F lark-sheets \u002F lark-base）。","https:\u002F\u002Fgithub.com\u002Flarksuite\u002Fcli\u002Fblob\u002Fmain\u002Fskills\u002Flark-wiki\u002FSKILL.md",[],[120,35,121,41,122,123,124,125,126,127,128,26,129,130,131],"lark wiki","wiki","base","sheets","token","文件","drive","URL","webfetch","doc","文档","表格",{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":141,"publishedAt":44},"01M6J198ST9SG3QYYR0HQJGT8M","lark-whiteboard","飞书画板：查询和编辑飞书云文档中的画板。支持导出画板为预览图片、导出原始节点结构、使用多种格式更新画板内容。 当用户需要查看画板内容、导出画板图片、编辑画板时使用此 skill。不负责：飞书云文档内容编辑（lark-doc）、文档内嵌电子表格\u002FBase（lark-sheets \u002F lark-base）。","https:\u002F\u002Fgithub.com\u002Flarksuite\u002Fcli\u002Fblob\u002Fmain\u002Fskills\u002Flark-whiteboard\u002FSKILL.md",[138],{"categoryNo":139,"categoryName":140,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",[142,35,143,144,145,26,41,129,130,131,122,123],"lark whiteboard","whiteboard","xlsx","image",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":155,"publishedAt":44},"01M6J191B8WT4V6CCDPXJKPE1N","lark-task","飞书任务：管理任务、清单和任务智能体。创建待办任务、查看和更新任务状态、拆分子任务、组织任务清单、分配协作成员、上传任务附件、注册或注销任务智能体、更新任务智能体的主页数据、写入智能体任务记录。当用户需要创建待办事项、查看任务列表、跟踪任务进度、管理项目清单或给他人分配任务、为任务上传附件文件、注册注销任务智能体、更新智能体主页数据、写入任务记录时使用。","https:\u002F\u002Fgithub.com\u002Flarksuite\u002Fcli\u002Fblob\u002Fmain\u002Fskills\u002Flark-task\u002FSKILL.md",[152],{"categoryNo":153,"categoryName":154,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[35,90,156,125,26,41,157,158],"lark task","协作","数据",{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":171,"publishedAt":44},"01M6J18RT6WZN71TBQEZ1MMX34","lark-slides","飞书幻灯片：创建和编辑幻灯片。创建演示文稿、读取幻灯片内容、管理幻灯片页面（创建、删除、读取、局部替换）。当用户需要创建或编辑幻灯片、读取或修改单个页面时使用。当用户给出 doubao.com 的 \u002Fslides\u002F URL\u002Ftoken 时，也应直接使用本 skill，不要因为域名不是飞书而回退到 WebFetch；路由依据是 URL 路径模式和 token，而不是域名。不负责：云文档内容编辑（走 lark-doc）、云文档里的独立画板对象（走 lark-whiteboard）、上传或下载普通文件（走 lark-drive）。","https:\u002F\u002Fgithub.com\u002Flarksuite\u002Fcli\u002Fblob\u002Fmain\u002Fskills\u002Flark-slides\u002FSKILL.md",[165,168],{"categoryNo":166,"categoryName":167,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":169,"categoryName":170,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",[35,172,173,26,41,129,130,174,175,128,126,124,127,125,143,176],"lark slides","slides","下载","演示","pptx"]