[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MP63JD78X2XVD2RWF55D1J":3,"skill-same:01M6MP63JD78X2XVD2RWF55D1J":76},{"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":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":42,"commitSha":43,"skillDirectory":44,"forksCount":45,"repositoryHtmlUrl":46,"repositoryHomepageUrl":47,"ownerHtmlUrl":48,"ownerBlogUrl":49,"ownerDescription":50,"updatedAt":51,"install":52,"resources":65},"01M6MP63JD78X2XVD2RWF55D1J","runtime-evidence-and-tracing",null,"Use when connecting observed behavior, logs, metrics, request IDs, run IDs, screenshots, traces, external dependency results, or artifacts into a runtime evidence loop.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1559,"MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fyfge\u002Fagent-harness-skills\u002Fskills\u002Fruntime-evidence-and-tracing\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36],"runtime evidence and tracing","tracing","runtime","evidence","behavior","when","request","traces","dependency","use","screenshots","results","loop","ids","logs","metrics","artifacts","run","2026-11-10 10:12:30",false,"---\nname: runtime-evidence-and-tracing\ndescription: Use when connecting observed behavior, logs, metrics, request IDs, run IDs, screenshots, traces, external dependency results, or artifacts into a runtime evidence loop.\nlicense: MIT\n---\n\n# Runtime Evidence And Tracing\n\n## Overview\n\nMake runtime validation auditable by tying observed behavior to runtime evidence through stable IDs and artifacts.\n\nAgents should not only say they tested something; they should leave run IDs, request IDs, logs, screenshots, interaction records, or traces. For shared harness terms, see `..\u002F..\u002Freferences\u002Fharness-patterns.md`; when evidence surfaces are absent, use `references\u002Fbuild-when-missing.md`. For neutral runtime profiles and redaction policy, see `references\u002Fruntime-profile-policy.md`.\n\n## When To Use\n\n- The user asks to connect, diagnose, or design interactive validation, runtime validation, request IDs, traces, logs, metrics, or artifacts.\n- A production or test-environment issue must be traced from observed behavior to runtime evidence.\n- A flow with external dependencies needs classification as code failure, dependency blocker, environment issue, or data problem.\n\n## Inputs Needed\n\n- Target flow, entry action, command, or interface.\n- Existing logging, request wrapper, headers, and observability endpoints.\n- Artifact directory and run ID naming preference.\n\n## Execution Order\n\n- First: Find the request entrypoint and existing request\u002Flog\u002Ftrace propagation points.\n- Then: Design run IDs, request IDs, artifact bundles, and collection commands.\n- Finally: Output the evidence contract and validation path, including fallback and blocker classification.\n\n## Step-by-Step Process\n\n1. Search request wrappers, service entrypoints, logs, metrics, and trace scripts.\n2. Confirm whether the calling surface can generate or propagate `X-Request-ID` and `X-Harness-Run-ID`.\n3. If no evidence contract exists, bootstrap the minimum run artifact contract from `references\u002Fbuild-when-missing.md`.\n4. Design `artifacts\u002Fruns\u002F\u003Crun_id>\u002F` with manifest, summary, logs, network, screenshots, and trace files.\n5. Define the collection order for the target flow: start, authenticate if needed, operate, wait, read artifacts, and attribute the result.\n6. Define blocker categories: code regression, environment unavailable, external dependency unavailable, data missing, and not evaluable.\n7. Explain how PRs or ledgers should reference artifacts without committing large temporary files.\n\n## Checks\n\n- Propagation: request ID and run ID remain searchable across caller, service, job, and external dependency evidence.\n- Artifact: the directory includes manifest, summary, and reproducible commands.\n- Evidence: screenshots, console, network, logs, and metrics cover the failure boundary.\n- Attribution: external dependency or environment blockers are not reported as product-quality failures.\n- Privacy: artifacts do not contain tokens, phone numbers, real secrets, or sensitive payloads.\n\n## Output Format\n\n```markdown\n# Runtime Evidence And Tracing\n\n## Detected Mapping\n- runtime-evidence:\n- validation:\n- ledger:\n\n## ID Contract\n- Run ID:\n- Request ID:\n- Header propagation:\n\n## Artifact Bundle\n-\n\n## Collection Flow\n1.\n2.\n3.\n\n## Failure Classification\n-\n\n## PR \u002F Ledger Reference\n-\n```\n\n## Common Mistakes\n\n- Keeping only screenshots with no request ID or runtime evidence.\n- Creating traces only in one layer, leaving observed failures disconnected.\n- Treating external account or quota issues as product-quality failures.\n- Committing large artifacts instead of referencing paths and summaries.\n\n## Example Prompts\n\n- \"Connect interactive validation to request IDs.\"\n- \"Design artifacts\u002Fruns evidence for this runtime workflow.\"\n- \"How should this failure be classified: code, environment, or external blocker?\"\n","# Runtime Evidence And Tracing\n\n## Overview\n\nMake runtime validation auditable by tying observed behavior to runtime evidence through stable IDs and artifacts.\n\nAgents should not only say they tested something; they should leave run IDs, request IDs, logs, screenshots, interaction records, or traces. For shared harness terms, see `..\u002F..\u002Freferences\u002Fharness-patterns.md`; when evidence surfaces are absent, use `references\u002Fbuild-when-missing.md`. For neutral runtime profiles and redaction policy, see `references\u002Fruntime-profile-policy.md`.\n\n## When To Use\n\n- The user asks to connect, diagnose, or design interactive validation, runtime validation, request IDs, traces, logs, metrics, or artifacts.\n- A production or test-environment issue must be traced from observed behavior to runtime evidence.\n- A flow with external dependencies needs classification as code failure, dependency blocker, environment issue, or data problem.\n\n## Inputs Needed\n\n- Target flow, entry action, command, or interface.\n- Existing logging, request wrapper, headers, and observability endpoints.\n- Artifact directory and run ID naming preference.\n\n## Execution Order\n\n- First: Find the request entrypoint and existing request\u002Flog\u002Ftrace propagation points.\n- Then: Design run IDs, request IDs, artifact bundles, and collection commands.\n- Finally: Output the evidence contract and validation path, including fallback and blocker classification.\n\n## Step-by-Step Process\n\n1. Search request wrappers, service entrypoints, logs, metrics, and trace scripts.\n2. Confirm whether the calling surface can generate or propagate `X-Request-ID` and `X-Harness-Run-ID`.\n3. If no evidence contract exists, bootstrap the minimum run artifact contract from `references\u002Fbuild-when-missing.md`.\n4. Design `artifacts\u002Fruns\u002F\u003Crun_id>\u002F` with manifest, summary, logs, network, screenshots, and trace files.\n5. Define the collection order for the target flow: start, authenticate if needed, operate, wait, read artifacts, and attribute the result.\n6. Define blocker categories: code regression, environment unavailable, external dependency unavailable, data missing, and not evaluable.\n7. Explain how PRs or ledgers should reference artifacts without committing large temporary files.\n\n## Checks\n\n- Propagation: request ID and run ID remain searchable across caller, service, job, and external dependency evidence.\n- Artifact: the directory includes manifest, summary, and reproducible commands.\n- Evidence: screenshots, console, network, logs, and metrics cover the failure boundary.\n- Attribution: external dependency or environment blockers are not reported as product-quality failures.\n- Privacy: artifacts do not contain tokens, phone numbers, real secrets, or sensitive payloads.\n\n## Output Format\n\n```markdown\n# Runtime Evidence And Tracing\n\n## Detected Mapping\n- runtime-evidence:\n- validation:\n- ledger:\n\n## ID Contract\n- Run ID:\n- Request ID:\n- Header propagation:\n\n## Artifact Bundle\n-\n\n## Collection Flow\n1.\n2.\n3.\n\n## Failure Classification\n-\n\n## PR \u002F Ledger Reference\n-\n```\n\n## Common Mistakes\n\n- Keeping only screenshots with no request ID or runtime evidence.\n- Creating traces only in one layer, leaving observed failures disconnected.\n- Treating external account or quota issues as product-quality failures.\n- Committing large artifacts instead of referencing paths and summaries.\n\n## Example Prompts\n\n- \"Connect interactive validation to request IDs.\"\n- \"Design artifacts\u002Fruns evidence for this runtime workflow.\"\n- \"How should this failure be classified: code, environment, or external blocker?\"\n",{"name":5,"license":15,"description":7},"main","e70ab1d8b0e24fbf8d3f58f35d71702abf856cfc","plugins\u002Fyfge\u002Fagent-harness-skills\u002Fskills\u002Fruntime-evidence-and-tracing",474,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-11 14:40:14",{"source":8,"skillName":5,"commands":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill runtime-evidence-and-tracing",{"tool":58,"command":59},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill runtime-evidence-and-tracing",{"tool":61,"command":62},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill runtime-evidence-and-tracing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fyfge\u002Fagent-harness-skills\u002Fskills\u002Fruntime-evidence-and-tracing\u002FSKILL.md",true,[66,72],{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Fbuild-when-missing.md","REFERENCE","参考文档",2086,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fyfge\u002Fagent-harness-skills\u002Fskills\u002Fruntime-evidence-and-tracing\u002Freferences\u002Fbuild-when-missing.md",{"path":73,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Fruntime-profile-policy.md",1111,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fyfge\u002Fagent-harness-skills\u002Fskills\u002Fruntime-evidence-and-tracing\u002Freferences\u002Fruntime-profile-policy.md",[77,86,93,100,126,151],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":85},"01M746ZWACVKMZ1BJXJZHYJSSX","migrate-to-e2e","Moves an existing Playwright, Cypress, Selenium, Appium, Detox, Maestro, or TesterArmy suite to e2e one slice at a time, with the old suite running beside the new one until each ported test is proven. Keeps a MIGRATION.md progress file so any later session resumes where the last stopped. Optionally plants a defect to show both suites catch it. Use for \u002Fmigrate-to-e2e, \"migrate our tests to e2e\", \"port these Maestro flows\", \"move our TesterArmy tests\", or when a project has an e2e config and an older suite still running.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fmigrate-to-e2e\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":85},"01M746ZPTAX1Q0FBKAB1CYND7E","e2e","Writes, runs, and debugs end-to-end tests for web and mobile apps with e2e, the agentic test runner, which mixes agent.act goals with exact locator assertions on a Playwright browser or an iOS or Android device. Also drives a project's running app live over the e2e MCP server to look at a screen, check a UI change, take a screenshot or record a video, and try a locator; and runs bug bashes, parallel e2e explore runs with each bug proven by a repro test. Use when a project depends on e2e or has an e2e.config.ts, when asked for end-to-end, browser, mobile, or agentic UI tests, to check a change in the running app, to QA or bug bash an app or branch, or when an e2e run fails.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fe2e\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":85},"01M746ZJN784HVHMDP9MQGCSGG","create-verification-skill","Generate a project-local verify-\u003Capp> skill on top of e2e, so any coding agent can launch the app, check it is worth driving, exercise a feature the way a user does, keep evidence, and bug bash it. Writes the skill, a feature map with one explore charter per feature, and proves it once. Use for \u002Fcreate-verification-skill, \"make a verification skill for this repo\", or when a project has no scripted way to prove UI behavior.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fcreate-verification-skill\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":37},"01M716A6ETNB9B1SQ3GXZC75VR","deja-search","deja-vu memory — search the user's past AI coding sessions with the deja CLI. Holds what they already settled and never wrote into the repo (naming rules, banned or already-tried tools, required checks before merge, preferred values, who owns what). Use before your first edit in a task, before you call a change done or ready to merge, before you recommend a tool, library, design or reviewer, before re-debugging an error that may already be solved, when they say 'didn't we fix this before', 'what did we decide about X' or 'I already have that', and before telling them something on this machine does not exist.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-search\u002FSKILL.md",[],[107,108,109,110,111,112,113,114,115,116,117,24,118,119,120,121,122,123,124,125],"search","deja search","never","error","ready","memory","re","decide","fix","design","debugging","you","done","reviewer","io","change","cli","merge","past",{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":37},"01M716A3J2W5SENSE9VGMXB375","deja-reflect","End-of-session reflection and memory curation with deja-vu. Review what was decided, what commands broke and what repaired them, and record durable project rules or decisions with deja remember so the next session starts with them.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-reflect\u002FSKILL.md",[],[133,134,135,121,136,137,138,139,140,141,142,143,144,145,112,146,147,148,149,150],"deja reflect","reflect","review","with","record","github","next","https","node","Rules","decisions","brew","remember","project rules","project","session","end","reflection",{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":168,"publishedAt":37},"01M715T3RR4BAYSR57HPPTJ0PF","revid","Make, edit, export and post AI videos with Revid (revid.ai) through the Revid MCP server. Use whenever the user wants a short-form or long-form video made (from an idea, a script, a URL, an article, a PDF, a tweet, a product page, their own clips, or a song), wants to find what is going viral on TikTok, YouTube, Instagram or X before making something, wants to edit or re-export an existing Revid project, generate a standalone AI image or clip, make a series episode, or publish and schedule a finished video to connected social accounts. Covers setup (hosted MCP with OAuth, or an API key), the 36 tools, credits, polling and the rules for publishing. Routes to the more specific revid-* skills when one fits.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftmakersas\u002Frevid-skills\u002Fskills\u002Frevid\u002FSKILL.md",[157,162,165],{"categoryNo":158,"categoryName":159,"taxonomyType":160,"taxonomyTypeDesc":161},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",{"categoryNo":163,"categoryName":164,"taxonomyType":160,"taxonomyTypeDesc":161},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":166,"categoryName":167,"taxonomyType":160,"taxonomyTypeDesc":161},"01JBSEEDCAT000000000000010","后端与接口",[153,169,170,171,172,173,174,147,175,113,176,177,178,179,24,180,181,182,183,184],"URL","Video","short-form","standalone","PDF","viral","tiktok","short","social","MCP","song","image","mcp server","schedule","api","publish"]