[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71AYP4MJBSZFM4WKHGCWD5P":3,"skill-same:01M71AYP4MJBSZFM4WKHGCWD5P":84},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":40,"linkOnly":41,"markdownContent":42,"markdownBody":43,"frontMatter":44,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":6,"ownerHtmlUrl":54,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":55,"install":56,"resources":69},"01M71AYP4MJBSZFM4WKHGCWD5P","verification-loop-shell-status",null,"Verify a substantial code change against the repository's actual acceptance gates, preserving command exit status, complete failure accounting, tested input identity, and meaningful behavioral evidence before claiming completion.","strmt7\u002Fai_skills_collection_benchmarked","strmt7","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F28989754?v=4","01M71929P914SWKQ7QJV24NBBY","Stratos","01M71929Q9VGKQ7PWYR95VSQQQ",1,"MIT","https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fimproved\u002Fskills\u002Fverification-loop-shell-status\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fimproved\u002Fskills\u002Fverification-loop-shell-status\u002FSKILL.md",[],[20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39],"status","verification loop shell status","verification loop","loop","shell","verification","repository","verify","acceptance","code","command","evidence","accounting","exit","claude-code","gates","input","complete","code change","change","2026-11-10 10:12:30",false,"---\nname: verification-loop-shell-status\ndescription: Verify a substantial code change against the repository's actual acceptance gates, preserving command exit status, complete failure accounting, tested input identity, and meaningful behavioral evidence before claiming completion.\nlicense: MIT\nmetadata:\n  source: affaan-m\u002Feverything-claude-code\n  source-commit: 846ffb75da9a5f4e677d927af1ad4a1951652267\n  revision-status: experimental-unbenchmarked\n---\n\n# Verification tied to the actual change\n\nRead the repository instructions, manifests, lockfiles, CI and relevant tests.\nIdentify the requested behavior, supported environments and exact required gates.\nUse existing authorization. Preserve unrelated changes and determine the intended\nbase from current Git\u002Fremote state; do not assume `HEAD~1` represents the task.\n\n## Choose checks that can expose the failure\n\nWrite down observable acceptance conditions before implementing or revising tests.\nFor a bug, reproduce the failure where practical, then check the repair and related\nregressions. Test behavior, useful boundaries and plausible wrong outcomes.\nMultiple related assertions can establish one behavior. Tests that repeat an\nimplementation, placeholder bodies, package metadata and a success message do\nnot establish correctness.\n\nUse the project's actual test runner, scripts and configuration. A package manager\nor an installed Bun binary does not identify the runner. Resolve installed tool\nAPIs and current stable dependencies; preserve a reproducible environment.\nFollow repository coverage gates and inspect missing relevant coverage. Do not\ninvent an 80% universal requirement or equate coverage with a correct oracle.\n\nStart with checks affected by the change, then run required broader gates.\nRepeat checks when new edits, failures, input changes or unresolved concerns\njustify it. A timer or completing every function is not sufficient reason to\nrepeat an expensive unchanged suite. Reversible presentation-only edits do not\nneed tests that merely restate them.\n\n## Preserve real status and evidence\n\nCapture each command's exit status and complete bounded log before displaying\nexcerpts. A default POSIX pipeline reports the last program's status: piping a\nfailed build through `head`, `tail` or `grep` can report success and truncate\nerrors. Preserve the producer's status with the chosen shell's supported\nmechanism, or invoke it directly through a process API. In PowerShell,\n`$LASTEXITCODE` is not a record of every native process in a pipeline. To retain\na producer's status, run it separately and capture `$LASTEXITCODE` before another\nnative invocation; then inspect its output and propagate the saved status from a\nwrapper when needed. For cmdlets, inspect their own success or error behavior:\n`$LASTEXITCODE` can still contain an earlier native command's result.\n`$ErrorActionPreference = 'Stop'` alone does not universally stop on native\nnonzero exits; check the host and its native-command preference. Do not assume\nPOSIX and PowerShell pipeline behavior is identical.\n\nRecord the exact command, environment\u002Ftool versions, input revision\u002Fsignatures,\nstatus, diagnostics and artifact location. Distinguish failure, timeout, abort,\nskipped, unavailable and not-run from passed. Retain the first failure and its\ncause when a corrected invocation later passes. A harness error is not a test\nfailure or successful task outcome. Keep credential-bearing logs private and\npublish only suitable evidence.\n\nRead structured test reports and complete denominators. Check that the intended\ntests actually ran and that output-producing wrappers preserve failure. Explain\ngenuine platform skips and remaining coverage; do not disable required tests,\nhide retries or suppress findings to make a report green.\n\n## Verify security and scope\n\nRun the repository's configured secret, dependency and code-scanning checks at\ntheir intended scope. Two grep strings or checking console logging cannot prove\nthe repository clean. Include relevant languages, dependencies, generated files\nand history when required. Fix validated causes, retain unresolved findings and\nreport unavailable scanners explicitly. Never turn off checks or add exemptions\nto satisfy a count.\n\nReview all changed file groups, staged\u002Funstaged edits and relevant untracked\noutputs. Confirm generated artifacts and locks match their inputs. Check that\nthe patch stays within the task's authorized scope and preserves unrelated data.\nAfter a meaningful input change, invalidate affected verification evidence and\nrerun the appropriate gate. Hosted checks must match the exact delivered head.\n\n## Report the practical conclusion\n\nLead with the resulting behavior, then state the relevant tests and their scope.\nReport planned\u002Fexecuted\u002Fpassed\u002Ffailed\u002Fskipped\u002Fnot-run checks and material limits.\nUse a completion verdict only when the requested acceptance criteria and required\ngates are verified. Otherwise name the concrete remaining work and keep the task\nactive. Do not extrapolate a focused pass to untested platforms, remote security,\nall skill categories or coding-agent superiority.\n\nThis experimental overlay corrects the original verification guidance. Actual\nshell controls reproduce the lost-exit-status defect, but no independent matched\nagent trial has established this overlay's benefit over default behavior.\n","# Verification tied to the actual change\n\nRead the repository instructions, manifests, lockfiles, CI and relevant tests.\nIdentify the requested behavior, supported environments and exact required gates.\nUse existing authorization. Preserve unrelated changes and determine the intended\nbase from current Git\u002Fremote state; do not assume `HEAD~1` represents the task.\n\n## Choose checks that can expose the failure\n\nWrite down observable acceptance conditions before implementing or revising tests.\nFor a bug, reproduce the failure where practical, then check the repair and related\nregressions. Test behavior, useful boundaries and plausible wrong outcomes.\nMultiple related assertions can establish one behavior. Tests that repeat an\nimplementation, placeholder bodies, package metadata and a success message do\nnot establish correctness.\n\nUse the project's actual test runner, scripts and configuration. A package manager\nor an installed Bun binary does not identify the runner. Resolve installed tool\nAPIs and current stable dependencies; preserve a reproducible environment.\nFollow repository coverage gates and inspect missing relevant coverage. Do not\ninvent an 80% universal requirement or equate coverage with a correct oracle.\n\nStart with checks affected by the change, then run required broader gates.\nRepeat checks when new edits, failures, input changes or unresolved concerns\njustify it. A timer or completing every function is not sufficient reason to\nrepeat an expensive unchanged suite. Reversible presentation-only edits do not\nneed tests that merely restate them.\n\n## Preserve real status and evidence\n\nCapture each command's exit status and complete bounded log before displaying\nexcerpts. A default POSIX pipeline reports the last program's status: piping a\nfailed build through `head`, `tail` or `grep` can report success and truncate\nerrors. Preserve the producer's status with the chosen shell's supported\nmechanism, or invoke it directly through a process API. In PowerShell,\n`$LASTEXITCODE` is not a record of every native process in a pipeline. To retain\na producer's status, run it separately and capture `$LASTEXITCODE` before another\nnative invocation; then inspect its output and propagate the saved status from a\nwrapper when needed. For cmdlets, inspect their own success or error behavior:\n`$LASTEXITCODE` can still contain an earlier native command's result.\n`$ErrorActionPreference = 'Stop'` alone does not universally stop on native\nnonzero exits; check the host and its native-command preference. Do not assume\nPOSIX and PowerShell pipeline behavior is identical.\n\nRecord the exact command, environment\u002Ftool versions, input revision\u002Fsignatures,\nstatus, diagnostics and artifact location. Distinguish failure, timeout, abort,\nskipped, unavailable and not-run from passed. Retain the first failure and its\ncause when a corrected invocation later passes. A harness error is not a test\nfailure or successful task outcome. Keep credential-bearing logs private and\npublish only suitable evidence.\n\nRead structured test reports and complete denominators. Check that the intended\ntests actually ran and that output-producing wrappers preserve failure. Explain\ngenuine platform skips and remaining coverage; do not disable required tests,\nhide retries or suppress findings to make a report green.\n\n## Verify security and scope\n\nRun the repository's configured secret, dependency and code-scanning checks at\ntheir intended scope. Two grep strings or checking console logging cannot prove\nthe repository clean. Include relevant languages, dependencies, generated files\nand history when required. Fix validated causes, retain unresolved findings and\nreport unavailable scanners explicitly. Never turn off checks or add exemptions\nto satisfy a count.\n\nReview all changed file groups, staged\u002Funstaged edits and relevant untracked\noutputs. Confirm generated artifacts and locks match their inputs. Check that\nthe patch stays within the task's authorized scope and preserves unrelated data.\nAfter a meaningful input change, invalidate affected verification evidence and\nrerun the appropriate gate. Hosted checks must match the exact delivered head.\n\n## Report the practical conclusion\n\nLead with the resulting behavior, then state the relevant tests and their scope.\nReport planned\u002Fexecuted\u002Fpassed\u002Ffailed\u002Fskipped\u002Fnot-run checks and material limits.\nUse a completion verdict only when the requested acceptance criteria and required\ngates are verified. Otherwise name the concrete remaining work and keep the task\nactive. Do not extrapolate a focused pass to untested platforms, remote security,\nall skill categories or coding-agent superiority.\n\nThis experimental overlay corrects the original verification guidance. Actual\nshell controls reproduce the lost-exit-status defect, but no independent matched\nagent trial has established this overlay's benefit over default behavior.\n",{"name":5,"license":15,"metadata":45,"description":7},{"source":46,"source-commit":47,"revision-status":48},"affaan-m\u002Feverything-claude-code","846ffb75da9a5f4e677d927af1ad4a1951652267","experimental-unbenchmarked","main","5c95bcac4646c5aed06bd9aed5235cfc7985aafc","included\u002Fimproved\u002Fskills\u002Fverification-loop-shell-status",0,"https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked","https:\u002F\u002Fgithub.com\u002Fstrmt7","2026-11-11 04:18:12",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add strmt7\u002Fai_skills_collection_benchmarked --skill verification-loop-shell-status",{"tool":62,"command":63},"bunx","bunx skills add strmt7\u002Fai_skills_collection_benchmarked --skill verification-loop-shell-status",{"tool":65,"command":66},"pnpm","pnpm dlx skills add strmt7\u002Fai_skills_collection_benchmarked --skill verification-loop-shell-status","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fimproved\u002Fskills\u002Fverification-loop-shell-status\u002FSKILL.md",true,[70,74,80],{"path":71,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":16},"LICENSE","许可证",1071,{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"NOTICE.md","REFERENCE","参考文档",813,"https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fimproved\u002Fskills\u002Fverification-loop-shell-status\u002FNOTICE.md",{"path":81,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":82,"sourceHtmlUrl":83},"provenance\u002Foriginal-SKILL.md",2617,"https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fimproved\u002Fskills\u002Fverification-loop-shell-status\u002Fprovenance\u002Foriginal-SKILL.md",[85,119,149,174,200,227],{"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":89,"licenseFileUrl":90,"sourceHtmlUrl":91,"categories":92,"keywords":101,"publishedAt":40},"01M71D4H3T6M57DFKN8HENAWRV","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Ftesting-qa-benchmarking\u002Fofficial-reference\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Ftesting-qa-benchmarking\u002Fofficial-reference\u002Fwebapp-testing\u002FSKILL.md",[93,98],{"categoryNo":94,"categoryName":95,"taxonomyType":96,"taxonomyTypeDesc":97},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":99,"categoryName":100,"taxonomyType":96,"taxonomyTypeDesc":97},"01JBSEEDCAT000000000000009","前端开发",[102,103,104,105,106,107,108,109,110,111,112,113,114,115,116,117,118],"webapp","testing","webapp testing","for","applications","local","frontend","debugging","toolkit","logs","browser","with","playwright","web","behavior","ui","screenshots",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":89,"licenseFileUrl":123,"sourceHtmlUrl":124,"categories":125,"keywords":129,"publishedAt":40},"01M71D4CQR2A2TB7GASCR5ZBG3","skill-creator","Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.","https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Ftesting-qa-benchmarking\u002Fofficial-reference\u002Fskill-creator-anthropics\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Ftesting-qa-benchmarking\u002Fofficial-reference\u002Fskill-creator-anthropics\u002FSKILL.md",[126],{"categoryNo":127,"categoryName":128,"taxonomyType":96,"taxonomyTypeDesc":97},"01JBSEEDCAT000000000000023","Skill与智能体开发",[130,131,132,133,134,135,136,137,138,139,140,141,142,143,144,145,146,147,105,148],"skill creator","creator","performance","improve","run evals","new","when","analysis","create","optimize","variance analysis","run","edit","benchmark","a skill","existing skill","evals","modify","accuracy",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":157,"publishedAt":40},"01M71D488XHEZVXXSXFYP8ENMH","playwright-skill","Complete browser automation with Playwright. Auto-detects dev servers, writes reusable test scripts, and supports screenshots, responsive checks, UX validation, login flows, link checks, and arbitrary browser automation. Use when the user wants to test a website, automate browser interactions, validate web functionality, or perform browser-based testing.","https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Ftesting-qa-benchmarking\u002Flatest-release-browser-automation\u002Fplaywright-skill\u002FSKILL.md",[155,156],{"categoryNo":94,"categoryName":95,"taxonomyType":96,"taxonomyTypeDesc":97},{"categoryNo":127,"categoryName":128,"taxonomyType":96,"taxonomyTypeDesc":97},[114,158,159,160,103,161,162,136,163,112,164,165,166,167,168,169,170,171,172,173],"playwright skill","browser automation","flows","auto","access","Bash","website","ux","login","scripts","read","write","node","install","network","responsive",{"skillNo":175,"name":176,"nameZh":6,"description":177,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":89,"licenseFileUrl":178,"sourceHtmlUrl":179,"categories":180,"keywords":182,"publishedAt":40},"01M71CY25GM939M6RES91QSG3T","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Fsearch-retrieval-web-automation\u002Fofficial-reference\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Fsearch-retrieval-web-automation\u002Fofficial-reference\u002Fweb-artifacts-builder\u002FSKILL.md",[181],{"categoryNo":99,"categoryName":100,"taxonomyType":96,"taxonomyTypeDesc":97},[183,184,185,115,186,187,188,105,189,190,108,191,192,193,194,195,196,197,198,199],"builder","artifacts builder","artifacts","web artifacts builder","single-file","css","Tailwind","ui components","single","use","file","components","react","multi","state","routing","state management",{"skillNo":201,"name":202,"nameZh":6,"description":203,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":89,"licenseFileUrl":204,"sourceHtmlUrl":205,"categories":206,"keywords":216,"publishedAt":40},"01M71CXZB60QJJ1H4S3NN94WMZ","frontend-design","Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML\u002FCSS layouts, or when styling\u002Fbeautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.","https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Fsearch-retrieval-web-automation\u002Fofficial-reference\u002Ffrontend-design\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Fsearch-retrieval-web-automation\u002Fofficial-reference\u002Ffrontend-design\u002FSKILL.md",[207,208,211],{"categoryNo":99,"categoryName":100,"taxonomyType":96,"taxonomyTypeDesc":97},{"categoryNo":209,"categoryName":210,"taxonomyType":96,"taxonomyTypeDesc":97},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":212,"categoryName":213,"taxonomyType":214,"taxonomyTypeDesc":215},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[108,217,218,188,219,220,221,106,222,223,192,136,185,29,194,224,195,225,226,113],"design","frontend design","ui design","generic","aesthetics","landing","pages","web ui","react components","examples",{"skillNo":228,"name":229,"nameZh":6,"description":230,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":231,"categories":232,"keywords":233,"publishedAt":40},"01M71CVZ54WFBTVA7R16PFY1ZE","zarr-python","Chunked N-D arrays for cloud storage. Compressed arrays, parallel I\u002FO, S3\u002FGCS integration, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Fscience-research-data-analysis\u002Flatest-release-community\u002Fzarr-python\u002FSKILL.md",[],[234,235,236,237,238,239,240,241,242,105,243,244,245,246,247,248,249,250],"zarr python","python","zarr","arrays","Cloud Storage","scientific","storage","parallel","dask","numpy","gcs","s3","integration","scientific computing","cloud","scale","pipelines"]