[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79DMHH90D7FSKS3XJ54Q85X":3,"skill-same:01M79DMHH90D7FSKS3XJ54Q85X":52},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M79DMHH90D7FSKS3XJ54Q85X","evidence-capture",null,"Capture a real UI walkthrough, prepare screenshots or video evidence, or package existing media for acceptance. Use when a task requires recorded product behavior.","AO-HyS\u002Fdevelopment-system","AO-HyS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F286554351?v=4","01M79DCXZGC6076EH5QATNXCY2","AO HyS","01M79DCY06TSBCJ946VP0BT0RG",0,"MIT","https:\u002F\u002Fgithub.com\u002FAO-HyS\u002Fdevelopment-system\u002Fblob\u002Fmain\u002Fartifacts\u002F1.16.0\u002Fskills\u002Finternal\u002Fevidence-capture\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: evidence-capture\ndescription: Capture a real UI walkthrough, prepare screenshots or video evidence, or package existing media for acceptance. Use when a task requires recorded product behavior.\n---\n\nAstra owns live Computer Use, chooses acceptance and judges the result.\nDeterministic host tools capture and package it under Astra supervision. Use the `evidence-preparation` roster route (Luna) only when a\nbounded script or media correction needs a writer; a running recording needs\nno model agent. Keep one driver per browser session.\n\n1. For final delivery, require completed Impeccable work and independent Astra\n   visual critique with findings resolved on this candidate (`design-quality`).\n   Baselines and review screenshots are diagnostic and may precede that gate.\n   Read the project's existing verification skill. Bind the actual repository,\n   app, revision, authorized origin\u002Fpath, test state and viewport. Obtain a\n   baseline before editing; label any recovered old revision as a recapture.\n2. Select a representative walkthrough for the affected behavior, plus distinct\n   risk states. Honor an explicit request for exhaustive coverage. Reuse valid\n   captures while candidate, data and environment match; changing an unrelated\n   file does not itself require rerecording all flows.\n   Choose the viewport and populated\u002Fempty state that demonstrate the requested\n   task and match its reference. A portrait browser capture does not demonstrate\n   the desktop composition. Confirm authentication, organization and usable\n   sample data before recording; report a missing state instead of substituting\n   an unrelated flow. Preserve private data and use authorized fixtures only.\n3. Discover the active host's recording and interaction tools once. Keep its\n   authorization and browser mechanism. Read [host-execution.md](references\u002Fhost-execution.md)\n   before composing a batch. Use the existing host-authorized execution plan;\n   do not introduce a second plan schema or browser bridge.\n4. Start recording, perform the authorized flow, wait for the final visible\n   outcome, then stop; also stop in a finally path on failure. If the host only\n   supports fixed-duration clips, ensure the completed flow fits inside the clip\n   or use shorter meaningful segments. A later action cannot complete an earlier\n   recording. Trim idle time only when it preserves the demonstrated sequence.\n   Group stable dependent operations into code; return compact step results and\n   evidence references. Yield when navigation, state or permission changes need\n   judgment. Refresh stale element references; never replay a possibly committed\n   write to recover from a tool error.\n5. Check that the media decodes, has nonzero duration and shows actual actions.\n   Sample beginning, transition and the actual end of the file; verify that the\n   terminal outcome is present within the media, not just in a later screenshot\n   or tool log. Inspect more when anomalies\n   appear. Record exactly what was sampled. Capture existence, full playback,\n   functional success and visual quality are separate claims.\n\nReturn completed steps, tool failures, media references, candidate\u002Fviewport\u002Fstate\nand gaps. Keep raw frames, recordings and credentials out of model text output.\nThe executor reports complete\u002Fincomplete, never product PASS\u002FFAIL. Astra combines\nit with before\u002Fafter probes and visual review. Missing recording support remains\na gap; screenshots or generated video cannot impersonate a walkthrough.\n\nSee [host-execution.md](references\u002Fhost-execution.md) for limits and invocation.\n","Astra owns live Computer Use, chooses acceptance and judges the result.\nDeterministic host tools capture and package it under Astra supervision. Use the `evidence-preparation` roster route (Luna) only when a\nbounded script or media correction needs a writer; a running recording needs\nno model agent. Keep one driver per browser session.\n\n1. For final delivery, require completed Impeccable work and independent Astra\n   visual critique with findings resolved on this candidate (`design-quality`).\n   Baselines and review screenshots are diagnostic and may precede that gate.\n   Read the project's existing verification skill. Bind the actual repository,\n   app, revision, authorized origin\u002Fpath, test state and viewport. Obtain a\n   baseline before editing; label any recovered old revision as a recapture.\n2. Select a representative walkthrough for the affected behavior, plus distinct\n   risk states. Honor an explicit request for exhaustive coverage. Reuse valid\n   captures while candidate, data and environment match; changing an unrelated\n   file does not itself require rerecording all flows.\n   Choose the viewport and populated\u002Fempty state that demonstrate the requested\n   task and match its reference. A portrait browser capture does not demonstrate\n   the desktop composition. Confirm authentication, organization and usable\n   sample data before recording; report a missing state instead of substituting\n   an unrelated flow. Preserve private data and use authorized fixtures only.\n3. Discover the active host's recording and interaction tools once. Keep its\n   authorization and browser mechanism. Read [host-execution.md](references\u002Fhost-execution.md)\n   before composing a batch. Use the existing host-authorized execution plan;\n   do not introduce a second plan schema or browser bridge.\n4. Start recording, perform the authorized flow, wait for the final visible\n   outcome, then stop; also stop in a finally path on failure. If the host only\n   supports fixed-duration clips, ensure the completed flow fits inside the clip\n   or use shorter meaningful segments. A later action cannot complete an earlier\n   recording. Trim idle time only when it preserves the demonstrated sequence.\n   Group stable dependent operations into code; return compact step results and\n   evidence references. Yield when navigation, state or permission changes need\n   judgment. Refresh stale element references; never replay a possibly committed\n   write to recover from a tool error.\n5. Check that the media decodes, has nonzero duration and shows actual actions.\n   Sample beginning, transition and the actual end of the file; verify that the\n   terminal outcome is present within the media, not just in a later screenshot\n   or tool log. Inspect more when anomalies\n   appear. Record exactly what was sampled. Capture existence, full playback,\n   functional success and visual quality are separate claims.\n\nReturn completed steps, tool failures, media references, candidate\u002Fviewport\u002Fstate\nand gaps. Keep raw frames, recordings and credentials out of model text output.\nThe executor reports complete\u002Fincomplete, never product PASS\u002FFAIL. Astra combines\nit with before\u002Fafter probes and visual review. Missing recording support remains\na gap; screenshots or generated video cannot impersonate a walkthrough.\n\nSee [host-execution.md](references\u002Fhost-execution.md) for limits and invocation.\n",{"name":5,"description":7},"main","9f5b43aadb1a92441d65e9cb74a584cd6fca62bc","artifacts\u002F1.16.0\u002Fskills\u002Finternal\u002Fevidence-capture","https:\u002F\u002Fgithub.com\u002FAO-HyS\u002Fdevelopment-system","https:\u002F\u002Fgithub.com\u002FAO-HyS","https:\u002F\u002Faohys.net\u002F","Software Boutique, we make your projects come true live. ","2026-11-14 03:17:27",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add AO-HyS\u002Fdevelopment-system --skill evidence-capture",{"tool":38,"command":39},"bunx","bunx skills add AO-HyS\u002Fdevelopment-system --skill evidence-capture",{"tool":41,"command":42},"pnpm","pnpm dlx skills add AO-HyS\u002Fdevelopment-system --skill evidence-capture","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAO-HyS\u002Fdevelopment-system\u002Fblob\u002Fmain\u002Fartifacts\u002F1.16.0\u002Fskills\u002Finternal\u002Fevidence-capture\u002FSKILL.md",true,[46],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Fhost-execution.md","REFERENCE","参考文档",3081,"https:\u002F\u002Fgithub.com\u002FAO-HyS\u002Fdevelopment-system\u002Fblob\u002Fmain\u002Fartifacts\u002F1.16.0\u002Fskills\u002Finternal\u002Fevidence-capture\u002Freferences\u002Fhost-execution.md",[53,60,67,74,81,88],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M79EQ4BPYQTX8RWN1Y1J2K1F","working-backwards","Define a software feature through PRFAQ and staged documents when the user requests working backwards before coding.","https:\u002F\u002Fgithub.com\u002FAO-HyS\u002Fdevelopment-system\u002Fblob\u002Fmain\u002Fartifacts\u002F2.8.0\u002Fskills\u002Finternal\u002Fworking-backwards\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M79EQ2E8P85Y1Y7VNJZMNEJE","flow-implement","Implement a requested software change through verification, corrections, and its authorized delivery endpoint.","https:\u002F\u002Fgithub.com\u002FAO-HyS\u002Fdevelopment-system\u002Fblob\u002Fmain\u002Fartifacts\u002F2.8.0\u002Fskills\u002Finternal\u002Fflow-implement\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M79EQ0PNMKHPJ78F8WMNX06P","development-steward","Run the scheduled, read-only weekly maintenance review for the six explicitly opted-in repositories and prepare one concise private report for Check-in.","https:\u002F\u002Fgithub.com\u002FAO-HyS\u002Fdevelopment-system\u002Fblob\u002Fmain\u002Fartifacts\u002F2.8.0\u002Fskills\u002Finternal\u002Fdevelopment-steward\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M79EPXJ56MX7955GWP1HD4B0","grill-with-docs","Run one recoverable interview for functional, visual, or mixed software grills; reuse equivalent answers and offer the shared HTML questionnaire.","https:\u002F\u002Fgithub.com\u002FAO-HyS\u002Fdevelopment-system\u002Fblob\u002Fmain\u002Fartifacts\u002F2.7.0\u002Fskills\u002Finternal\u002Fgrill-with-docs\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M79EPTFPHYEV40ZG52Z0GVS2","global-agent-guardrails","Install, audit, test, or update the Development System's global destructive-command guard for Codex, Claude Code and T3 Code. Use when configuring agent safety hooks or investigating whether dangerous shell operations are blocked.","https:\u002F\u002Fgithub.com\u002FAO-HyS\u002Fdevelopment-system\u002Fblob\u002Fmain\u002Fartifacts\u002F2.7.0\u002Fskills\u002Finternal\u002Fglobal-agent-guardrails\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":92,"licenseFileUrl":93,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M79EPR0KPHKAFN7V6CEEDR0Y","impeccable","Design or refine frontend UI using project context and a focused design playbook; also handles visual critique and polish.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FAO-HyS\u002Fdevelopment-system\u002Fblob\u002Fmain\u002Fartifacts\u002F2.7.0\u002Fskills\u002Fexternal\u002Fimpeccable\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FAO-HyS\u002Fdevelopment-system\u002Fblob\u002Fmain\u002Fartifacts\u002F2.7.0\u002Fskills\u002Fexternal\u002Fimpeccable\u002FSKILL.md",[],[]]