[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B3M8A107JN7FD2FN8T07HZ":3,"skill-same:01M7B3M8A107JN7FD2FN8T07HZ":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":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":29,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M7B3M8A107JN7FD2FN8T07HZ","clarvis-tui-e2e-validation",null,"Validate complete Clarvis terminal-UI integration journeys in a real PTY with screenshots, frame evidence, and observable assertions. Use for interactive regressions, transcript or overlay UX changes, release canaries, and claims that a TUI flow works end to end; do not use for headless unit tests alone.","getclarvis\u002Fclarvis","getclarvis","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F268562684?v=4","01M7B3KM3YS9T4PRS3EVESW45V","Clarvis","01M7B3KM4ZAH0EH74XZWE9W8WQ",14,"MIT","https:\u002F\u002Fgithub.com\u002Fgetclarvis\u002Fclarvis\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fclarvis-tui-e2e-validation\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: clarvis-tui-e2e-validation\ndescription: \"Validate complete Clarvis terminal-UI integration journeys in a real PTY with screenshots, frame evidence, and observable assertions. Use for interactive regressions, transcript or overlay UX changes, release canaries, and claims that a TUI flow works end to end; do not use for headless unit tests alone.\"\n---\n\n# Clarvis TUI end-to-end validation\n\nProve the user journey against the artifact that will actually be handed off. A passing component\nrender or textual snapshot is supporting evidence, not a substitute for driving the full-screen\napplication and inspecting what a person sees.\n\n## Establish the contract\n\n1. Read `AGENTS.md`, `packages\u002Fcode\u002FREADME.md`, the owning `specs\u002Fhosts\u002Fcode-*.md` files, and\n   `specs\u002Fknown-issues.md`. Inspect the worktree and preserve unrelated changes.\n2. Write the journey as observable checkpoints before running it: initial state, user actions,\n   intermediate transitions, terminal outcome, and the visual invariants that must remain unchanged.\n3. Build the current TUI artifact, or deliberately enable source mode. Record which one is under\n   test; never validate a stale installed bundle and attribute the result to current source.\n4. Use isolated Clarvis state and a disposable workspace unless the scenario explicitly requires\n   the user's real profile. Real subscriptions, credentials, provider calls, browser authorization,\n   installation, or deletion still require the authorization applicable to that action.\n\n## Aggregate mechanics through `$tui-driver`\n\nUse the `tui-driver` skill as the operational layer for starting the real PTY, observing the screen,\ndriving keyboard or pointer input, waiting for rendered state, recording frames, and capturing\nscreenshots. Read and follow that skill when executing this workflow. Do not reproduce its command\ncatalog in this skill or invent a parallel driver abstraction.\n\nPrefer observable readiness tokens and stable frames over fixed sleeps. Match the terminal size,\nkeyboard path, mouse path, theme, and artifact type implicated by the defect. A PTY result proves\nthe PTY path only; preserve any remaining physical-terminal limitation in the verdict.\n\n## Exercise the complete journey\n\n- Start from the state a user actually encounters, including first paint when relevant.\n- Drive every transition that owns the reported behavior rather than jumping directly to a final\n  fixture. Include keyboard and pointer routes when both are product contracts.\n- For real runs, verify submission, live model text, tool activity, sidebar or overlay transitions,\n  settlement, subsequent turns, scrolling away from and back to the tail, and explicit navigation\n  back from retained surfaces as applicable.\n- Use unique visible tokens so evidence cannot accidentally match splash copy, placeholders, stale\n  history, or another projection.\n- Validate failure and recovery paths when they are part of the change. A notification without the\n  intended state transition is not success.\n\nFor transcript work, treat continuity as a first-class assertion: already painted cells keep their\nrow and style while mutable content grows; native scrolling admits history before it reaches the\nviewport; returning from a child or overlay preserves the reader state; explicit submit returns to\nthe Lead tail; lazy residency stays bounded; and live-to-settled Markdown, diffs, writes, and memory\ntools do not flicker, disappear, or downgrade visually.\n\n## Capture and inspect visual evidence\n\nCapture at least the first meaningful frame, each state-changing boundary implicated by the change,\nand the settled result. Use a short frame sequence around movement or flicker defects; one final\nimage cannot prove that rows did not jump between frames.\n\nInspect the rendered images themselves. Check geometry, spacing, clipping, focus, hierarchy,\nscrollbars, colors or syntax styling, stale labels, duplicate activity, and continuity with adjacent\nhistory. Text extraction may support assertions but cannot establish visual quality on its own.\nName or index evidence so each image maps back to a checkpoint and artifact.\n\n## Make the validation repeatable\n\nTurn stable checkpoints into repository tests when the driver supports a durable assertion without\nencoding incidental timing or terminal noise. Keep screenshots for visual claims and semantic\nassertions for behavior; do not replace one with the other. Re-run the journey against the final\nrebuilt artifact after the last source change.\n\nFor soak or memory-sensitive work, repeat complete turns and navigation cycles while collecting the\nrepository's diagnostic ledger. Assert bounded semantic turns, physical owners, renderer listeners,\npending handles and queues, as well as an environment-qualified RSS ceiling. A quiet screen alone\ndoes not prove bounded retention.\n\n## Report the verdict\n\nState the artifact, commit\u002Fworktree state, terminal dimensions and profile isolation; enumerate the\njourneys and checkpoints; link or name the screenshots and frame sequences; list exact automated\nchecks; and classify each requirement as passed, failed, or unverified. Report driver, provider, OS,\nand physical-terminal limitations precisely. Stop all spawned PTYs and disclose any retained test\nworkspace or state. Do not claim success until both behavior and the relevant visual evidence agree.\n","# Clarvis TUI end-to-end validation\n\nProve the user journey against the artifact that will actually be handed off. A passing component\nrender or textual snapshot is supporting evidence, not a substitute for driving the full-screen\napplication and inspecting what a person sees.\n\n## Establish the contract\n\n1. Read `AGENTS.md`, `packages\u002Fcode\u002FREADME.md`, the owning `specs\u002Fhosts\u002Fcode-*.md` files, and\n   `specs\u002Fknown-issues.md`. Inspect the worktree and preserve unrelated changes.\n2. Write the journey as observable checkpoints before running it: initial state, user actions,\n   intermediate transitions, terminal outcome, and the visual invariants that must remain unchanged.\n3. Build the current TUI artifact, or deliberately enable source mode. Record which one is under\n   test; never validate a stale installed bundle and attribute the result to current source.\n4. Use isolated Clarvis state and a disposable workspace unless the scenario explicitly requires\n   the user's real profile. Real subscriptions, credentials, provider calls, browser authorization,\n   installation, or deletion still require the authorization applicable to that action.\n\n## Aggregate mechanics through `$tui-driver`\n\nUse the `tui-driver` skill as the operational layer for starting the real PTY, observing the screen,\ndriving keyboard or pointer input, waiting for rendered state, recording frames, and capturing\nscreenshots. Read and follow that skill when executing this workflow. Do not reproduce its command\ncatalog in this skill or invent a parallel driver abstraction.\n\nPrefer observable readiness tokens and stable frames over fixed sleeps. Match the terminal size,\nkeyboard path, mouse path, theme, and artifact type implicated by the defect. A PTY result proves\nthe PTY path only; preserve any remaining physical-terminal limitation in the verdict.\n\n## Exercise the complete journey\n\n- Start from the state a user actually encounters, including first paint when relevant.\n- Drive every transition that owns the reported behavior rather than jumping directly to a final\n  fixture. Include keyboard and pointer routes when both are product contracts.\n- For real runs, verify submission, live model text, tool activity, sidebar or overlay transitions,\n  settlement, subsequent turns, scrolling away from and back to the tail, and explicit navigation\n  back from retained surfaces as applicable.\n- Use unique visible tokens so evidence cannot accidentally match splash copy, placeholders, stale\n  history, or another projection.\n- Validate failure and recovery paths when they are part of the change. A notification without the\n  intended state transition is not success.\n\nFor transcript work, treat continuity as a first-class assertion: already painted cells keep their\nrow and style while mutable content grows; native scrolling admits history before it reaches the\nviewport; returning from a child or overlay preserves the reader state; explicit submit returns to\nthe Lead tail; lazy residency stays bounded; and live-to-settled Markdown, diffs, writes, and memory\ntools do not flicker, disappear, or downgrade visually.\n\n## Capture and inspect visual evidence\n\nCapture at least the first meaningful frame, each state-changing boundary implicated by the change,\nand the settled result. Use a short frame sequence around movement or flicker defects; one final\nimage cannot prove that rows did not jump between frames.\n\nInspect the rendered images themselves. Check geometry, spacing, clipping, focus, hierarchy,\nscrollbars, colors or syntax styling, stale labels, duplicate activity, and continuity with adjacent\nhistory. Text extraction may support assertions but cannot establish visual quality on its own.\nName or index evidence so each image maps back to a checkpoint and artifact.\n\n## Make the validation repeatable\n\nTurn stable checkpoints into repository tests when the driver supports a durable assertion without\nencoding incidental timing or terminal noise. Keep screenshots for visual claims and semantic\nassertions for behavior; do not replace one with the other. Re-run the journey against the final\nrebuilt artifact after the last source change.\n\nFor soak or memory-sensitive work, repeat complete turns and navigation cycles while collecting the\nrepository's diagnostic ledger. Assert bounded semantic turns, physical owners, renderer listeners,\npending handles and queues, as well as an environment-qualified RSS ceiling. A quiet screen alone\ndoes not prove bounded retention.\n\n## Report the verdict\n\nState the artifact, commit\u002Fworktree state, terminal dimensions and profile isolation; enumerate the\njourneys and checkpoints; link or name the screenshots and frame sequences; list exact automated\nchecks; and classify each requirement as passed, failed, or unverified. Report driver, provider, OS,\nand physical-terminal limitations precisely. Stop all spawned PTYs and disclose any retained test\nworkspace or state. Do not claim success until both behavior and the relevant visual evidence agree.\n",{"name":5,"description":7},"main","17a550a7fff59752a1917c3c88dbe9a2aef09bdf",".agents\u002Fskills\u002Fclarvis-tui-e2e-validation",1,"https:\u002F\u002Fgithub.com\u002Fgetclarvis\u002Fclarvis","https:\u002F\u002Fclarvis.dev","https:\u002F\u002Fgithub.com\u002Fgetclarvis","2026-10-05 05:46:18",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add getclarvis\u002Fclarvis --skill clarvis-tui-e2e-validation",{"tool":38,"command":39},"bunx","bunx skills add getclarvis\u002Fclarvis --skill clarvis-tui-e2e-validation",{"tool":41,"command":42},"pnpm","pnpm dlx skills add getclarvis\u002Fclarvis --skill clarvis-tui-e2e-validation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgetclarvis\u002Fclarvis\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fclarvis-tui-e2e-validation\u002FSKILL.md",true,[46],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"agents\u002Fopenai.yaml","REFERENCE","参考文档",272,"https:\u002F\u002Fgithub.com\u002Fgetclarvis\u002Fclarvis\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fclarvis-tui-e2e-validation\u002Fagents\u002Fopenai.yaml",[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},"01M7B3N824S0ABTQWA2A2QANGN","suppressed","Reconcile an invoice ledger.","https:\u002F\u002Fgithub.com\u002Fgetclarvis\u002Fclarvis\u002Fblob\u002Fmain\u002Fpackages\u002Fskills\u002Ftests\u002Ffixtures\u002Fforeign-skills\u002Fsuppressed\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},"01M7B3N4Z5VMSJH4W3CDVMP08S","slash-hidden","Rebuild the search index.","https:\u002F\u002Fgithub.com\u002Fgetclarvis\u002Fclarvis\u002Fblob\u002Fmain\u002Fpackages\u002Fskills\u002Ftests\u002Ffixtures\u002Fforeign-skills\u002Fslash-hidden\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},"01M7B3N3AG6C6PKRGV6VK0FREX","presented","Draft release notes from a commit range.","https:\u002F\u002Fgithub.com\u002Fgetclarvis\u002Fclarvis\u002Fblob\u002Fmain\u002Fpackages\u002Fskills\u002Ftests\u002Ffixtures\u002Fforeign-skills\u002Fpresented\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},"01M7B3N1TX6H3K4QYTDGQ0ZJT2","plain","Format a changelog entry.","https:\u002F\u002Fgithub.com\u002Fgetclarvis\u002Fclarvis\u002Fblob\u002Fmain\u002Fpackages\u002Fskills\u002Ftests\u002Ffixtures\u002Fforeign-skills\u002Fplain\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},"01M7B3N0CKN3VWF13VBBT5CKX6","no-name","Bisect a regression across a commit range.","https:\u002F\u002Fgithub.com\u002Fgetclarvis\u002Fclarvis\u002Fblob\u002Fmain\u002Fpackages\u002Fskills\u002Ftests\u002Ffixtures\u002Fforeign-skills\u002Fno-name\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7B3MX6DG19B3S2QD6RKX8QC","no-description","https:\u002F\u002Fgithub.com\u002Fgetclarvis\u002Fclarvis\u002Fblob\u002Fmain\u002Fpackages\u002Fskills\u002Ftests\u002Ffixtures\u002Fforeign-skills\u002Fno-description\u002FSKILL.md",[],[]]