[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D4AZ56D81HBP08WKSNEJY7":3,"skill-same:01M7D4AZ56D81HBP08WKSNEJY7":54},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":47},"01M7D4AZ56D81HBP08WKSNEJY7","e2e-case-lifecycle",null,"Plan, maintain, replay, and promote ZCode desktop E2E cases and their fixtures, coverage matrices, and CI admission evidence.","zai-org\u002FZCode","zai-org","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F223098841?v=4","01M7D3Y10287Y0CNVHSNZ4GD03","Z.ai","01M7D3Y10SKN81G21P442YTCYP",8689,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fzai-org\u002FZCode\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fe2e-case-lifecycle\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: e2e-case-lifecycle\ndescription: Plan, maintain, replay, and promote ZCode desktop E2E cases and their fixtures, coverage matrices, and CI admission evidence.\ndisable-model-invocation: true\n---\n\n# E2E Case Lifecycle\n\nUse this skill for the z-code E2E lifecycle: manual-review automation, capture\u002Freplay evidence, formal fixture promotion, Docker admission, and CI. It is intentionally domain-neutral: use it for conversation flows, SSH, provider settings, UI workflows, filesystem behavior, remote runtimes, auth\u002Fconfig, and similar product surfaces. Work from the z-code repo root.\n\n目录分类遵循 `docs\u002Ftesting\u002Fe2e-business-scenarios.md`。转正保留业务场景目录，只移除 `manual-review\u002Fpending`；fixture 仍按 caseName 索引。\n\n## Required Reading\n\nBefore writing or moving an E2E spec, read the relevant sections of the domain's case catalog, coverage matrix, and workflow docs. For conversation-session work, the default sources are:\n\n- `docs\u002Fconversation-session-case-catalog.md`\n- `docs\u002Ftesting\u002Fconversation-session-e2e-coverage-matrix.md`\n- `docs\u002Ftesting\u002Fconversation-session-e2e-development-workflow.md`\n\nIf the request involves SSH, provider settings, auth\u002Fconfig, fork, goal, fault, model switch, or remote\u002Freplayable semantics, also read the matching matrix\u002Fspec document under `docs\u002Ftesting\u002F` or the nearest feature docs.\n\n## Coverage Planning\n\nFor open-ended feature changes or \"what should we cover?\" requests, use\n`feature-boundary-planner` first. Return here only after accepted cases\nexist in the catalog\u002Fmatrix.\n\nWhen asked what to test:\n\n1. Extract state dimensions from the feature spec, catalog, and matrix.\n2. Enumerate combinations, then prune invalid or duplicate cases with the user.\n3. Write accepted\u002Fundefined\u002Fpruned decisions into catalog or matrix docs before code.\n4. Only generate E2E code for accepted semantics. If product behavior is undefined, stop at a question or doc update.\n\nDo not claim coverage from a path that merely passes through a state; each covered case needs setup, action, and assertion.\n\nA matrix row may say `covered` only when it cites the artifact of a run in which that case passed, for example `packages\u002Fdesktop\u002F.e2e-artifacts\u002Fdesktop-e2e-\u003Crun-id>`. A new assertion that never ran does not count: if an earlier step or a known baseline failure stops the case first, keep the row `partial` or `failing`, write `blocked by \u003Cbaseline id or symptom>`, and list the assertions that did not run. Update the row again when a passing run exists.\n\n## Manual Review Case\n\nFor a new candidate case:\n\n1. Put the spec under the domain's `manual-review\u002Fpending\u002F` directory. For conversation-session this is `packages\u002Fdesktop\u002Ftest\u002Fe2e\u002Fconversation-session\u002F\u003Cscenario>\u002Fmanual-review\u002Fpending\u002F`.\n2. Use stable `E2E_*` markers in user prompts and provider matchers.\n3. Prefer existing helpers in `packages\u002Fdesktop\u002Ftest\u002Fe2e\u002Fhelpers\u002F`.\n4. Use `buildReadonlyToolPrompt(...)` for high\u002Fmedium priority completed-history setup unless timing makes tool history counterproductive.\n5. Run manual\u002Fcapture with:\n\n```bash\nZCODE_E2E_MANUAL_REVIEW=1 pnpm --filter @zcode\u002Fdesktop test:e2e -- --spec '.\u002Ftest\u002Fe2e\u002Fconversation-session\u002F\u003Cscenario>\u002Fmanual-review\u002Fpending\u002F\u003Ccase>.test.ts'\n```\n\nManual\u002Fcapture artifacts are review evidence, not the final test contract.\n\nWhen a feedback reproduction run needs a video artifact, record the Electron\nwindow from inside the app instead of using OS screen recording. Import\n`startElectronWindowRecording` and `ELECTRON_WINDOW_RECORDING_CAPTURE_MODE` from\n`#e2e\u002Fhelpers\u002Felectron-window-recorder` in conversation\n`manual-review\u002Fpending\u002F` specs, start recording before the user-visible path,\nstop it in `finally`, and write `video_capture_mode:\nELECTRON_WINDOW_RECORDING_CAPTURE_MODE` to the feedback manifest. Do not use\nmacOS Screen Recording, `screencapture`, QuickTime, or screenshot-only videos as\nthe normal evidence path.\n\n## Promotion\n\nAfter the user confirms human review, run the promotion dry run first:\n\n```bash\npnpm --filter @zcode\u002Fdesktop e2e:promote -- --spec .\u002Ftest\u002Fe2e\u002Fconversation-session\u002F\u003Cscenario>\u002Fmanual-review\u002Fpending\u002F\u003Ccase>.test.ts --reviewed\n```\n\nThen apply:\n\n```bash\npnpm --filter @zcode\u002Fdesktop e2e:promote -- --spec .\u002Ftest\u002Fe2e\u002Fconversation-session\u002F\u003Cscenario>\u002Fmanual-review\u002Fpending\u002F\u003Ccase>.test.ts --reviewed --apply\n```\n\nThe tool moves the spec, fixes common helper imports, creates fixture\u002Fmanifest scaffolds, and updates the coverage matrix path. It does not decide request semantics.\n\nOn `--apply`, promotion treats those writes as one filesystem transaction and runs\n`pnpm audit:conversation-session-coverage` against the tentative formal state. It\nkeeps the promotion only when the audit passes; audit failure or execution error\nrestores the pending spec, fixtures, manifest, and coverage matrix, then exits\nnonzero. Therefore complete and validate the canonical fixture contract while the\nspec is still pending instead of relying on post-promotion scaffolds.\n\n## Fixture Contract\n\nUse case-local data by default:\n\n- `packages\u002Fdesktop\u002Ftest\u002Fe2e\u002Ffixtures\u002Fupstream\u002Fcommon.json` for truly shared helper responses.\n- `packages\u002Fdesktop\u002Ftest\u002Fe2e\u002Ffixtures\u002Fupstream\u002F\u003Cdomain>\u002F\u003Ccase>.json` for case-specific provider responses.\n- `packages\u002Fdesktop\u002Ftest\u002Fe2e\u002Ffixtures\u002Fcases\u002F\u003Cdomain>\u002F\u003Ccase>.json` for manifest metadata.\n- `packages\u002Fdesktop\u002Ftest\u002Fe2e\u002Ffixtures\u002Ffs\u002F\u003Cdomain>\u002F\u003Ccase>\u002F` for file-system fixtures.\n\nClassify each request as `main`, `common`, `ignore`, or `synthetic`. Developers review uncertain classifications; tools handle mechanical checks. Do not add new case-specific responses to `provider-basic.json`.\n\nFor timing:\n\n- `fast-text`: ordinary functional assertions.\n- `controlled-stream`: stop, queue, interrupted, or running-window assertions.\n- `recorded-stream`: performance or stream cadence assertions.\n- `fault-stream`: socket, truncation, rate-limit, or error injection.\n\nEvery synthetic request needs a `syntheticReason` in fixture metadata and manifest requests.\n\n## Verification\n\nAfter filling fixtures:\n\nFor a pending case, validate the current spec against its canonical formal-target fixture metadata before promotion:\n\n```bash\npnpm --filter @zcode\u002Fdesktop e2e:fixture:check -- --spec .\u002Ftest\u002Fe2e\u002Fconversation-session\u002F\u003Cscenario>\u002Fmanual-review\u002Fpending\u002F\u003Ccase>.test.ts\n```\n\nThe `spec` field in both the case manifest and case-local provider fixture remains\n`.\u002Ftest\u002Fe2e\u002Fconversation-session\u002F\u003Cscenario>\u002F\u003Ccase>.test.ts` while the current spec is pending. It is the canonical formal target,\nnot the current physical path. Pending replay remains explicit: pass `E2E_PROVIDER_REPLAY_FIXTURE_PATH` so a normal\nmanual-review run still captures the live provider path.\n\nAfter promotion:\n\n```bash\npnpm --filter @zcode\u002Fdesktop e2e:fixture:check -- --spec .\u002Ftest\u002Fe2e\u002Fconversation-session\u002F\u003Cscenario>\u002F\u003Ccase>.test.ts\n```\n\nProve the case does not depend on legacy shared fixtures:\n\n```bash\nE2E_PROVIDER_REPLAY_FIXTURE_PATH=packages\u002Fdesktop\u002Ftest\u002Fe2e\u002Ffixtures\u002Fupstream\u002Fcommon.json,packages\u002Fdesktop\u002Ftest\u002Fe2e\u002Ffixtures\u002Fupstream\u002Fconversation-session\u002F\u003Ccase>.json \\\n  pnpm --filter @zcode\u002Fdesktop exec wdio run wdio.conf.ts --spec '.\u002Ftest\u002Fe2e\u002Fconversation-session\u002F\u003Cscenario>\u002F\u003Ccase>.test.ts'\n```\n\nThen run default replay:\n\n```bash\npnpm --filter @zcode\u002Fdesktop exec wdio run wdio.conf.ts --spec '.\u002Ftest\u002Fe2e\u002Fconversation-session\u002F\u003Cscenario>\u002F\u003Ccase>.test.ts'\n```\n\nBefore adding the case to the Docker suite, prove the formal case in isolated replay:\n\n```bash\nE2E_SPEC=.\u002Ftest\u002Fe2e\u002Fconversation-session\u002F\u003Cscenario>\u002F\u003Ccase>.test.ts pnpm run test:e2e:container\n```\n\nAfter that passes, admit it to the Docker conversation preset:\n\n```bash\npnpm --filter @zcode\u002Fdesktop e2e:docker:admit -- --spec .\u002Ftest\u002Fe2e\u002Fconversation-session\u002F\u003Cscenario>\u002F\u003Ccase>.test.ts --verified --artifact packages\u002Fdesktop\u002F.e2e-artifacts\u002F\u003Crun-id> --apply\npnpm run test:e2e:container:conversation\n```\n\nDocker runs are suite-oriented after admission. Use one isolated single-spec\nDocker run only as the admission proof or for failure localization. Once a case\nis admitted, batch stable compatible specs through the matching preset such as\n`pnpm run test:e2e:container:conversation`; this reuses the image, container\nstartup, WDIO entrypoint, desktop app build, and agent server build. Split a case\ninto a separate preset or container only when it needs real capture, fault\ninjection, performance\u002Ftiming-sensitive replay, global-state pollution, or\nspecial network\u002Ffile-system setup.\n\nFor E2E code changes, run the following required code checks once for the final change. Documentation-only edits use the documentation checks in [AGENTS.md](..\u002F..\u002F..\u002FAGENTS.md):\n\n```bash\npnpm --filter @zcode\u002Fdesktop typecheck:e2e\npnpm typecheck\npnpm lint\n```\n\nAfter the applicable lifecycle checks and code checks pass, finish; repeat or expand only after new edits, failures, or unresolved risks. Keep human review and promotion\u002Fadmission requirements above intact. If a required environment or check is blocked, finish the executable parts and report the remaining evidence; use the root AGENTS.md completion rules and do not automatically commit incomplete verification. Report existing warnings separately from new failures.\n","# E2E Case Lifecycle\n\nUse this skill for the z-code E2E lifecycle: manual-review automation, capture\u002Freplay evidence, formal fixture promotion, Docker admission, and CI. It is intentionally domain-neutral: use it for conversation flows, SSH, provider settings, UI workflows, filesystem behavior, remote runtimes, auth\u002Fconfig, and similar product surfaces. Work from the z-code repo root.\n\n目录分类遵循 `docs\u002Ftesting\u002Fe2e-business-scenarios.md`。转正保留业务场景目录，只移除 `manual-review\u002Fpending`；fixture 仍按 caseName 索引。\n\n## Required Reading\n\nBefore writing or moving an E2E spec, read the relevant sections of the domain's case catalog, coverage matrix, and workflow docs. For conversation-session work, the default sources are:\n\n- `docs\u002Fconversation-session-case-catalog.md`\n- `docs\u002Ftesting\u002Fconversation-session-e2e-coverage-matrix.md`\n- `docs\u002Ftesting\u002Fconversation-session-e2e-development-workflow.md`\n\nIf the request involves SSH, provider settings, auth\u002Fconfig, fork, goal, fault, model switch, or remote\u002Freplayable semantics, also read the matching matrix\u002Fspec document under `docs\u002Ftesting\u002F` or the nearest feature docs.\n\n## Coverage Planning\n\nFor open-ended feature changes or \"what should we cover?\" requests, use\n`feature-boundary-planner` first. Return here only after accepted cases\nexist in the catalog\u002Fmatrix.\n\nWhen asked what to test:\n\n1. Extract state dimensions from the feature spec, catalog, and matrix.\n2. Enumerate combinations, then prune invalid or duplicate cases with the user.\n3. Write accepted\u002Fundefined\u002Fpruned decisions into catalog or matrix docs before code.\n4. Only generate E2E code for accepted semantics. If product behavior is undefined, stop at a question or doc update.\n\nDo not claim coverage from a path that merely passes through a state; each covered case needs setup, action, and assertion.\n\nA matrix row may say `covered` only when it cites the artifact of a run in which that case passed, for example `packages\u002Fdesktop\u002F.e2e-artifacts\u002Fdesktop-e2e-\u003Crun-id>`. A new assertion that never ran does not count: if an earlier step or a known baseline failure stops the case first, keep the row `partial` or `failing`, write `blocked by \u003Cbaseline id or symptom>`, and list the assertions that did not run. Update the row again when a passing run exists.\n\n## Manual Review Case\n\nFor a new candidate case:\n\n1. Put the spec under the domain's `manual-review\u002Fpending\u002F` directory. For conversation-session this is `packages\u002Fdesktop\u002Ftest\u002Fe2e\u002Fconversation-session\u002F\u003Cscenario>\u002Fmanual-review\u002Fpending\u002F`.\n2. Use stable `E2E_*` markers in user prompts and provider matchers.\n3. Prefer existing helpers in `packages\u002Fdesktop\u002Ftest\u002Fe2e\u002Fhelpers\u002F`.\n4. Use `buildReadonlyToolPrompt(...)` for high\u002Fmedium priority completed-history setup unless timing makes tool history counterproductive.\n5. Run manual\u002Fcapture with:\n\n```bash\nZCODE_E2E_MANUAL_REVIEW=1 pnpm --filter @zcode\u002Fdesktop test:e2e -- --spec '.\u002Ftest\u002Fe2e\u002Fconversation-session\u002F\u003Cscenario>\u002Fmanual-review\u002Fpending\u002F\u003Ccase>.test.ts'\n```\n\nManual\u002Fcapture artifacts are review evidence, not the final test contract.\n\nWhen a feedback reproduction run needs a video artifact, record the Electron\nwindow from inside the app instead of using OS screen recording. Import\n`startElectronWindowRecording` and `ELECTRON_WINDOW_RECORDING_CAPTURE_MODE` from\n`#e2e\u002Fhelpers\u002Felectron-window-recorder` in conversation\n`manual-review\u002Fpending\u002F` specs, start recording before the user-visible path,\nstop it in `finally`, and write `video_capture_mode:\nELECTRON_WINDOW_RECORDING_CAPTURE_MODE` to the feedback manifest. Do not use\nmacOS Screen Recording, `screencapture`, QuickTime, or screenshot-only videos as\nthe normal evidence path.\n\n## Promotion\n\nAfter the user confirms human review, run the promotion dry run first:\n\n```bash\npnpm --filter @zcode\u002Fdesktop e2e:promote -- --spec .\u002Ftest\u002Fe2e\u002Fconversation-session\u002F\u003Cscenario>\u002Fmanual-review\u002Fpending\u002F\u003Ccase>.test.ts --reviewed\n```\n\nThen apply:\n\n```bash\npnpm --filter @zcode\u002Fdesktop e2e:promote -- --spec .\u002Ftest\u002Fe2e\u002Fconversation-session\u002F\u003Cscenario>\u002Fmanual-review\u002Fpending\u002F\u003Ccase>.test.ts --reviewed --apply\n```\n\nThe tool moves the spec, fixes common helper imports, creates fixture\u002Fmanifest scaffolds, and updates the coverage matrix path. It does not decide request semantics.\n\nOn `--apply`, promotion treats those writes as one filesystem transaction and runs\n`pnpm audit:conversation-session-coverage` against the tentative formal state. It\nkeeps the promotion only when the audit passes; audit failure or execution error\nrestores the pending spec, fixtures, manifest, and coverage matrix, then exits\nnonzero. Therefore complete and validate the canonical fixture contract while the\nspec is still pending instead of relying on post-promotion scaffolds.\n\n## Fixture Contract\n\nUse case-local data by default:\n\n- `packages\u002Fdesktop\u002Ftest\u002Fe2e\u002Ffixtures\u002Fupstream\u002Fcommon.json` for truly shared helper responses.\n- `packages\u002Fdesktop\u002Ftest\u002Fe2e\u002Ffixtures\u002Fupstream\u002F\u003Cdomain>\u002F\u003Ccase>.json` for case-specific provider responses.\n- `packages\u002Fdesktop\u002Ftest\u002Fe2e\u002Ffixtures\u002Fcases\u002F\u003Cdomain>\u002F\u003Ccase>.json` for manifest metadata.\n- `packages\u002Fdesktop\u002Ftest\u002Fe2e\u002Ffixtures\u002Ffs\u002F\u003Cdomain>\u002F\u003Ccase>\u002F` for file-system fixtures.\n\nClassify each request as `main`, `common`, `ignore`, or `synthetic`. Developers review uncertain classifications; tools handle mechanical checks. Do not add new case-specific responses to `provider-basic.json`.\n\nFor timing:\n\n- `fast-text`: ordinary functional assertions.\n- `controlled-stream`: stop, queue, interrupted, or running-window assertions.\n- `recorded-stream`: performance or stream cadence assertions.\n- `fault-stream`: socket, truncation, rate-limit, or error injection.\n\nEvery synthetic request needs a `syntheticReason` in fixture metadata and manifest requests.\n\n## Verification\n\nAfter filling fixtures:\n\nFor a pending case, validate the current spec against its canonical formal-target fixture metadata before promotion:\n\n```bash\npnpm --filter @zcode\u002Fdesktop e2e:fixture:check -- --spec .\u002Ftest\u002Fe2e\u002Fconversation-session\u002F\u003Cscenario>\u002Fmanual-review\u002Fpending\u002F\u003Ccase>.test.ts\n```\n\nThe `spec` field in both the case manifest and case-local provider fixture remains\n`.\u002Ftest\u002Fe2e\u002Fconversation-session\u002F\u003Cscenario>\u002F\u003Ccase>.test.ts` while the current spec is pending. It is the canonical formal target,\nnot the current physical path. Pending replay remains explicit: pass `E2E_PROVIDER_REPLAY_FIXTURE_PATH` so a normal\nmanual-review run still captures the live provider path.\n\nAfter promotion:\n\n```bash\npnpm --filter @zcode\u002Fdesktop e2e:fixture:check -- --spec .\u002Ftest\u002Fe2e\u002Fconversation-session\u002F\u003Cscenario>\u002F\u003Ccase>.test.ts\n```\n\nProve the case does not depend on legacy shared fixtures:\n\n```bash\nE2E_PROVIDER_REPLAY_FIXTURE_PATH=packages\u002Fdesktop\u002Ftest\u002Fe2e\u002Ffixtures\u002Fupstream\u002Fcommon.json,packages\u002Fdesktop\u002Ftest\u002Fe2e\u002Ffixtures\u002Fupstream\u002Fconversation-session\u002F\u003Ccase>.json \\\n  pnpm --filter @zcode\u002Fdesktop exec wdio run wdio.conf.ts --spec '.\u002Ftest\u002Fe2e\u002Fconversation-session\u002F\u003Cscenario>\u002F\u003Ccase>.test.ts'\n```\n\nThen run default replay:\n\n```bash\npnpm --filter @zcode\u002Fdesktop exec wdio run wdio.conf.ts --spec '.\u002Ftest\u002Fe2e\u002Fconversation-session\u002F\u003Cscenario>\u002F\u003Ccase>.test.ts'\n```\n\nBefore adding the case to the Docker suite, prove the formal case in isolated replay:\n\n```bash\nE2E_SPEC=.\u002Ftest\u002Fe2e\u002Fconversation-session\u002F\u003Cscenario>\u002F\u003Ccase>.test.ts pnpm run test:e2e:container\n```\n\nAfter that passes, admit it to the Docker conversation preset:\n\n```bash\npnpm --filter @zcode\u002Fdesktop e2e:docker:admit -- --spec .\u002Ftest\u002Fe2e\u002Fconversation-session\u002F\u003Cscenario>\u002F\u003Ccase>.test.ts --verified --artifact packages\u002Fdesktop\u002F.e2e-artifacts\u002F\u003Crun-id> --apply\npnpm run test:e2e:container:conversation\n```\n\nDocker runs are suite-oriented after admission. Use one isolated single-spec\nDocker run only as the admission proof or for failure localization. Once a case\nis admitted, batch stable compatible specs through the matching preset such as\n`pnpm run test:e2e:container:conversation`; this reuses the image, container\nstartup, WDIO entrypoint, desktop app build, and agent server build. Split a case\ninto a separate preset or container only when it needs real capture, fault\ninjection, performance\u002Ftiming-sensitive replay, global-state pollution, or\nspecial network\u002Ffile-system setup.\n\nFor E2E code changes, run the following required code checks once for the final change. Documentation-only edits use the documentation checks in [AGENTS.md](..\u002F..\u002F..\u002FAGENTS.md):\n\n```bash\npnpm --filter @zcode\u002Fdesktop typecheck:e2e\npnpm typecheck\npnpm lint\n```\n\nAfter the applicable lifecycle checks and code checks pass, finish; repeat or expand only after new edits, failures, or unresolved risks. Keep human review and promotion\u002Fadmission requirements above intact. If a required environment or check is blocked, finish the executable parts and report the remaining evidence; use the root AGENTS.md completion rules and do not automatically commit incomplete verification. Report existing warnings separately from new failures.\n",{"name":5,"description":7,"disable-model-invocation":24},true,"main","fec975905a2abd4c07e35c40d51fa097a2258ec9",".agents\u002Fskills\u002Fe2e-case-lifecycle",2710,"https:\u002F\u002Fgithub.com\u002Fzai-org\u002FZCode","https:\u002F\u002Fzcode.z.ai\u002F","https:\u002F\u002Fgithub.com\u002Fzai-org","https:\u002F\u002Fwww.zhipuai.cn\u002Fen","ChatGLM, GLM-4.5, CogVLM, CodeGeeX, CogView, CogVideoX | CogDL, AMiner | Zhipu.ai (Z.ai)","2026-11-13 16:21:40",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":24},[37,40,43],{"tool":38,"command":39},"npx","npx skills add zai-org\u002FZCode --skill e2e-case-lifecycle",{"tool":41,"command":42},"bunx","bunx skills add zai-org\u002FZCode --skill e2e-case-lifecycle",{"tool":44,"command":45},"pnpm","pnpm dlx skills add zai-org\u002FZCode --skill e2e-case-lifecycle","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzai-org\u002FZCode\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fe2e-case-lifecycle\u002FSKILL.md",[48],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"agents\u002Fopenai.yaml","REFERENCE","参考文档",185,"https:\u002F\u002Fgithub.com\u002Fzai-org\u002FZCode\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fe2e-case-lifecycle\u002Fagents\u002Fopenai.yaml",[55,62,69,76,83,90],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7D57RTFKZH4SFFWF6NXSQ62","plugin-mcp-ping","E2E workspace Plugin skill marker","https:\u002F\u002Fgithub.com\u002Fzai-org\u002FZCode\u002Fblob\u002Fmain\u002Fpackages\u002Fdesktop\u002Ftest\u002Fe2e\u002Ffixtures\u002Fplugin-mcp-skill\u002Fe2e-plugin-mcp-ping\u002Fskills\u002Fplugin-mcp-ping\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7D57NRW93T0ETX2QPQY3JCP","e2e-ext-compat-plain","PLM-EXT-STORE fixture skill for e2e-ext-compat-plain.","https:\u002F\u002Fgithub.com\u002Fzai-org\u002FZCode\u002Fblob\u002Fmain\u002Fpackages\u002Fdesktop\u002Ftest\u002Fe2e\u002Ffixtures\u002Ffs\u002Fplugins\u002Fplugin-store-extension-compat\u002Fstore-market\u002Fplugins\u002Fe2e-ext-compat-plain\u002Fskills\u002Fe2e-ext-compat-plain\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7D57JYKJK5A4VW7Y5MYEA7R","e2e-ext-compat-ok","PLM-EXT-STORE fixture skill for e2e-ext-compat-ok.","https:\u002F\u002Fgithub.com\u002Fzai-org\u002FZCode\u002Fblob\u002Fmain\u002Fpackages\u002Fdesktop\u002Ftest\u002Fe2e\u002Ffixtures\u002Ffs\u002Fplugins\u002Fplugin-store-extension-compat\u002Fstore-market\u002Fplugins\u002Fe2e-ext-compat-ok\u002Fskills\u002Fe2e-ext-compat-ok\u002FSKILL.md",[],[],{"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":19},"01M7D57FZQKN28QJJ0HVG93ACN","e2e-ext-compat-installed","PLM-EXT-STORE fixture skill for e2e-ext-compat-installed.","https:\u002F\u002Fgithub.com\u002Fzai-org\u002FZCode\u002Fblob\u002Fmain\u002Fpackages\u002Fdesktop\u002Ftest\u002Fe2e\u002Ffixtures\u002Ffs\u002Fplugins\u002Fplugin-store-extension-compat\u002Fstore-market\u002Fplugins\u002Fe2e-ext-compat-installed\u002Fskills\u002Fe2e-ext-compat-installed\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7D57C9W30WJ3NJDAYX2MN0J","e2e-ext-compat-future","PLM-EXT-STORE fixture skill for e2e-ext-compat-future.","https:\u002F\u002Fgithub.com\u002Fzai-org\u002FZCode\u002Fblob\u002Fmain\u002Fpackages\u002Fdesktop\u002Ftest\u002Fe2e\u002Ffixtures\u002Ffs\u002Fplugins\u002Fplugin-store-extension-compat\u002Fstore-market\u002Fplugins\u002Fe2e-ext-compat-future\u002Fskills\u002Fe2e-ext-compat-future\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M7D579KKRR6D2GPVW4J4QWVT","e2e-store-skill-b","E2E store fixture skill b","https:\u002F\u002Fgithub.com\u002Fzai-org\u002FZCode\u002Fblob\u002Fmain\u002Fpackages\u002Fdesktop\u002Ftest\u002Fe2e\u002Ffixtures\u002Ffs\u002Fplugins\u002Fplugin-extension-reads\u002Fstore-market\u002Fplugins\u002Fe2e-ext-store-b\u002Fskills\u002Fe2e-store-skill-b\u002FSKILL.md",[],[]]