[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CS5S5S0YY56686G5CQ0WMP":3,"skill-same:01M6CS5S5S0YY56686G5CQ0WMP":62},{"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":24,"linkOnly":25,"markdownContent":26,"markdownBody":27,"frontMatter":28,"refName":29,"commitSha":30,"skillDirectory":31,"forksCount":32,"repositoryHtmlUrl":33,"repositoryHomepageUrl":6,"ownerHtmlUrl":34,"ownerBlogUrl":35,"ownerDescription":36,"updatedAt":37,"install":38,"resources":51},"01M6CS5S5S0YY56686G5CQ0WMP","verification",null,"Use when about to claim work is complete, fixed, or passing, before committing or creating PRs. Requires running verification commands and confirming output before making any success claims. Evidence before assertions, always.","mrtolkien\u002FGHOST","mrtolkien","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F8489650?v=4","01M6CS32Q934XBQQE8BDV5Z6W2","Tolki","01M6CS32VBCD47F5E27WF9W6FC",5,"MIT","https:\u002F\u002Fgithub.com\u002Fmrtolkien\u002FGHOST\u002Fblob\u002Fmain\u002Fassets\u002Fskills\u002Fsuperpowers\u002Fverification\u002Fskill.md",[],[5,19,20,21,22,23],"coding","work","use","evidence","claim","2026-11-10 10:12:30",false,"---\nname: verification\ndescription:\n  Use when about to claim work is complete, fixed, or passing, before committing or\n  creating PRs. Requires running verification commands and confirming output before\n  making any success claims. Evidence before assertions, always.\navailable: coding\n---\n\n# Verification Before Completion\n\n## Overview\n\nClaiming work is complete without verification is dishonesty, not efficiency.\n\n**Core principle:** Evidence before claims, always.\n\n**Violating the letter of this rule is violating the spirit of this rule.**\n\n## The Iron Law\n\n```\nNO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE\n```\n\nIf you haven't run the verification command in this message, you cannot claim it passes.\n\n## The Gate Function\n\n```\nBEFORE claiming any status or expressing satisfaction:\n\n1. IDENTIFY: What command proves this claim?\n2. RUN: Execute the FULL command (fresh, complete)\n3. READ: Full output, check exit code, count failures\n4. VERIFY: Does output confirm the claim?\n   - If NO: State actual status with evidence\n   - If YES: State claim WITH evidence\n5. ONLY THEN: Make the claim\n\nSkip any step = lying, not verifying\n```\n\n## Common Failures\n\n| Claim                 | Requires                        | Not Sufficient                 |\n| --------------------- | ------------------------------- | ------------------------------ |\n| Tests pass            | Test command output: 0 failures | Previous run, \"should pass\"    |\n| Linter clean          | Linter output: 0 errors         | Partial check, extrapolation   |\n| Build succeeds        | Build command: exit 0           | Linter passing, logs look good |\n| Bug fixed             | Test original symptom: passes   | Code changed, assumed fixed    |\n| Regression test works | Red-green cycle verified        | Test passes once               |\n| Agent completed       | VCS diff shows changes          | Agent reports \"success\"        |\n| Requirements met      | Line-by-line checklist          | Tests passing                  |\n\n## Red Flags - STOP\n\n- Using \"should\", \"probably\", \"seems to\"\n- Expressing satisfaction before verification (\"Great!\", \"Perfect!\", \"Done!\", etc.)\n- About to commit\u002Fpush\u002FPR without verification\n- Trusting agent success reports\n- Relying on partial verification\n- Thinking \"just this once\"\n- Tired and wanting work over\n- **ANY wording implying success without having run verification**\n\n## Rationalization Prevention\n\n| Excuse                                  | Reality                            |\n| --------------------------------------- | ---------------------------------- |\n| \"Should work now\"                       | RUN the verification               |\n| \"I'm confident\"                         | Confidence does not equal evidence |\n| \"Just this once\"                        | No exceptions                      |\n| \"Linter passed\"                         | Linter does not equal compiler     |\n| \"Agent said success\"                    | Verify independently               |\n| \"I'm tired\"                             | Exhaustion does not equal excuse   |\n| \"Partial check is enough\"               | Partial proves nothing             |\n| \"Different words so rule doesn't apply\" | Spirit over letter                 |\n\n## Key Patterns\n\n**Tests:**\n\n```\nOK: [Run test command] [See: 34\u002F34 pass] \"All tests pass\"\nNO: \"Should pass now\" \u002F \"Looks correct\"\n```\n\n**Regression tests (TDD Red-Green):**\n\n```\nOK: Write -> Run (pass) -> Revert fix -> Run (MUST FAIL) -> Restore -> Run (pass)\nNO: \"I've written a regression test\" (without red-green verification)\n```\n\n**Build:**\n\n```\nOK: [Run build] [See: exit 0] \"Build passes\"\nNO: \"Linter passed\" (linter doesn't check compilation)\n```\n\n**Requirements:**\n\n```\nOK: Re-read plan -> Create checklist -> Verify each -> Report gaps or completion\nNO: \"Tests pass, phase complete\"\n```\n\n**Agent delegation:**\n\n```\nOK: Agent reports success -> Check VCS diff -> Verify changes -> Report actual state\nNO: Trust agent report\n```\n\n## Why This Matters\n\n- The OPERATOR said \"I don't believe you\" — trust broken\n- Undefined functions shipped — would crash\n- Missing requirements shipped — incomplete features\n- Time wasted on false completion, leading to redirect and rework\n- Violates: \"Honesty is a core value. If you lie, you'll be replaced.\"\n\n## When To Apply\n\n**ALWAYS before:**\n\n- ANY variation of success\u002Fcompletion claims\n- ANY expression of satisfaction\n- ANY positive statement about work state\n- Committing, PR creation, task completion\n- Moving to next task\n- Delegating to agents\n\n**Rule applies to:**\n\n- Exact phrases\n- Paraphrases and synonyms\n- Implications of success\n- ANY communication suggesting completion\u002Fcorrectness\n\n## The Bottom Line\n\n**No shortcuts for verification.**\n\nRun the command. Read the output. THEN claim the result.\n\nThis is non-negotiable.\n","# Verification Before Completion\n\n## Overview\n\nClaiming work is complete without verification is dishonesty, not efficiency.\n\n**Core principle:** Evidence before claims, always.\n\n**Violating the letter of this rule is violating the spirit of this rule.**\n\n## The Iron Law\n\n```\nNO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE\n```\n\nIf you haven't run the verification command in this message, you cannot claim it passes.\n\n## The Gate Function\n\n```\nBEFORE claiming any status or expressing satisfaction:\n\n1. IDENTIFY: What command proves this claim?\n2. RUN: Execute the FULL command (fresh, complete)\n3. READ: Full output, check exit code, count failures\n4. VERIFY: Does output confirm the claim?\n   - If NO: State actual status with evidence\n   - If YES: State claim WITH evidence\n5. ONLY THEN: Make the claim\n\nSkip any step = lying, not verifying\n```\n\n## Common Failures\n\n| Claim                 | Requires                        | Not Sufficient                 |\n| --------------------- | ------------------------------- | ------------------------------ |\n| Tests pass            | Test command output: 0 failures | Previous run, \"should pass\"    |\n| Linter clean          | Linter output: 0 errors         | Partial check, extrapolation   |\n| Build succeeds        | Build command: exit 0           | Linter passing, logs look good |\n| Bug fixed             | Test original symptom: passes   | Code changed, assumed fixed    |\n| Regression test works | Red-green cycle verified        | Test passes once               |\n| Agent completed       | VCS diff shows changes          | Agent reports \"success\"        |\n| Requirements met      | Line-by-line checklist          | Tests passing                  |\n\n## Red Flags - STOP\n\n- Using \"should\", \"probably\", \"seems to\"\n- Expressing satisfaction before verification (\"Great!\", \"Perfect!\", \"Done!\", etc.)\n- About to commit\u002Fpush\u002FPR without verification\n- Trusting agent success reports\n- Relying on partial verification\n- Thinking \"just this once\"\n- Tired and wanting work over\n- **ANY wording implying success without having run verification**\n\n## Rationalization Prevention\n\n| Excuse                                  | Reality                            |\n| --------------------------------------- | ---------------------------------- |\n| \"Should work now\"                       | RUN the verification               |\n| \"I'm confident\"                         | Confidence does not equal evidence |\n| \"Just this once\"                        | No exceptions                      |\n| \"Linter passed\"                         | Linter does not equal compiler     |\n| \"Agent said success\"                    | Verify independently               |\n| \"I'm tired\"                             | Exhaustion does not equal excuse   |\n| \"Partial check is enough\"               | Partial proves nothing             |\n| \"Different words so rule doesn't apply\" | Spirit over letter                 |\n\n## Key Patterns\n\n**Tests:**\n\n```\nOK: [Run test command] [See: 34\u002F34 pass] \"All tests pass\"\nNO: \"Should pass now\" \u002F \"Looks correct\"\n```\n\n**Regression tests (TDD Red-Green):**\n\n```\nOK: Write -> Run (pass) -> Revert fix -> Run (MUST FAIL) -> Restore -> Run (pass)\nNO: \"I've written a regression test\" (without red-green verification)\n```\n\n**Build:**\n\n```\nOK: [Run build] [See: exit 0] \"Build passes\"\nNO: \"Linter passed\" (linter doesn't check compilation)\n```\n\n**Requirements:**\n\n```\nOK: Re-read plan -> Create checklist -> Verify each -> Report gaps or completion\nNO: \"Tests pass, phase complete\"\n```\n\n**Agent delegation:**\n\n```\nOK: Agent reports success -> Check VCS diff -> Verify changes -> Report actual state\nNO: Trust agent report\n```\n\n## Why This Matters\n\n- The OPERATOR said \"I don't believe you\" — trust broken\n- Undefined functions shipped — would crash\n- Missing requirements shipped — incomplete features\n- Time wasted on false completion, leading to redirect and rework\n- Violates: \"Honesty is a core value. If you lie, you'll be replaced.\"\n\n## When To Apply\n\n**ALWAYS before:**\n\n- ANY variation of success\u002Fcompletion claims\n- ANY expression of satisfaction\n- ANY positive statement about work state\n- Committing, PR creation, task completion\n- Moving to next task\n- Delegating to agents\n\n**Rule applies to:**\n\n- Exact phrases\n- Paraphrases and synonyms\n- Implications of success\n- ANY communication suggesting completion\u002Fcorrectness\n\n## The Bottom Line\n\n**No shortcuts for verification.**\n\nRun the command. Read the output. THEN claim the result.\n\nThis is non-negotiable.\n",{"name":5,"available":19,"description":7},"main","083d96429a2d05526f8a294b83c74f0336670def","assets\u002Fskills\u002Fsuperpowers\u002Fverification",0,"https:\u002F\u002Fgithub.com\u002Fmrtolkien\u002FGHOST","https:\u002F\u002Fgithub.com\u002Fmrtolkien","https:\u002F\u002Fblog.tolki.dev","Data Engineer \u002F Esports \u002F Keyboards","2026-04-24 15:41:08",{"source":8,"skillName":5,"commands":39,"prompt":49,"zipAvailable":50},[40,43,46],{"tool":41,"command":42},"npx","npx skills add mrtolkien\u002FGHOST --skill verification",{"tool":44,"command":45},"bunx","bunx skills add mrtolkien\u002FGHOST --skill verification",{"tool":47,"command":48},"pnpm","pnpm dlx skills add mrtolkien\u002FGHOST --skill verification","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmrtolkien\u002FGHOST\u002Fblob\u002Fmain\u002Fassets\u002Fskills\u002Fsuperpowers\u002Fverification\u002Fskill.md",true,[52,58],{"path":53,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":56,"sourceHtmlUrl":57},"evals\u002Fevals.json","REFERENCE","参考文档",7715,"https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FMarketing-and-Growth\u002Fpage-cro\u002Fevals\u002Fevals.json",{"path":59,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Fexperiments.md",7850,"https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FMarketing-and-Growth\u002Fpage-cro\u002Freferences\u002Fexperiments.md",[63,89,113,131,142,153],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":24},"01M6CS613RWD9CFJ3KFX47V1DS","system-management","Use when reading or changing GHOST configuration (providers, models, timing, compaction, services, any config.toml key), adding or switching LLM providers, answering questions about GHOST's own features or capabilities, a CLI tool is missing or \"not found\", services need starting\u002Fstopping\u002Fdebugging, updating GHOST to a newer version, managing the Nix shell environment, or troubleshooting GHOST setup.","https:\u002F\u002Fgithub.com\u002Fmrtolkien\u002FGHOST\u002Fblob\u002Fmain\u002Fassets\u002Fskills\u002Fsystem-management\u002Fskill.md",[],[70,71,72,73,74,75,76,77,78,79,21,80,81,82,83,84,85,86,87,88],"system management","system","management","version","models","configuration","troubleshooting","cli","nix","config","environment","setup","debugging","capabilities","services","Providers","shell","ghost","tool",{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":108,"publishedAt":24},"01M6CS5XTK2884R9HE15YR8YZM","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002Fmrtolkien\u002FGHOST\u002Fblob\u002Fmain\u002Fassets\u002Fskills\u002Fsuperpowers\u002Fwriting-skills\u002Fskill.md",[95,100,103],{"categoryNo":96,"categoryName":97,"taxonomyType":98,"taxonomyTypeDesc":99},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":101,"categoryName":102,"taxonomyType":98,"taxonomyTypeDesc":99},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":104,"categoryName":105,"taxonomyType":106,"taxonomyTypeDesc":107},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[109,110,20,19,111,21,112],"writing","writing skills","deployment","editing",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":121,"publishedAt":24},"01M6CS5V737R1DVB3TZEK0C6WT","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code. Write comprehensive implementation plans assuming the engineer has zero context for our codebase and questionable taste.","https:\u002F\u002Fgithub.com\u002Fmrtolkien\u002FGHOST\u002Fblob\u002Fmain\u002Fassets\u002Fskills\u002Fsuperpowers\u002Fwriting-plans\u002Fskill.md",[119,120],{"categoryNo":101,"categoryName":102,"taxonomyType":98,"taxonomyTypeDesc":99},{"categoryNo":104,"categoryName":105,"taxonomyType":106,"taxonomyTypeDesc":107},[122,109,123,124,125,21,126,127,128,129,130,19],"writing plans","engineer","task","implementation","spec","context","write","ZeRO","code",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":138,"publishedAt":24},"01M6CS5PD2ZSFWYRDZSACNTAJY","tdd","Use when implementing any feature or bugfix, before writing implementation code. Write the test first. Watch it fail. Write minimal code to pass.","https:\u002F\u002Fgithub.com\u002Fmrtolkien\u002FGHOST\u002Fblob\u002Fmain\u002Fassets\u002Fskills\u002Fsuperpowers\u002Ftdd\u002Fskill.md",[137],{"categoryNo":96,"categoryName":97,"taxonomyType":98,"taxonomyTypeDesc":99},[133,139,125,140,21,128,19,130,141,109],"first","minimal","test",{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":149,"publishedAt":24},"01M6CS5K5WE2SHF1YV8D9C4C77","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002Fmrtolkien\u002FGHOST\u002Fblob\u002Fmain\u002Fassets\u002Fskills\u002Fsuperpowers\u002Fsystematic-debugging\u002Fskill.md",[148],{"categoryNo":96,"categoryName":97,"taxonomyType":98,"taxonomyTypeDesc":99},[82,150,141,151,21,152,19],"systematic debugging","bug","behavior",{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":159,"publishedAt":24},"01M6CS5FPYWZHHG4X0GQHR8CKT","subagent-development","Use when executing implementation plans with independent tasks in the current session. Dispatch a fresh subagent per task, with two-stage review after each — spec compliance review first, then code quality review. Keeps context clean and quality high.","https:\u002F\u002Fgithub.com\u002Fmrtolkien\u002FGHOST\u002Fblob\u002Fmain\u002Fassets\u002Fskills\u002Fsuperpowers\u002Fsubagent-development\u002Fskill.md",[],[160,161,162,163,164,124,165,125,166,21,167,127,19,139,168,130,169,170,126,171],"subagent development","subagent","development","quality","quality review","clean","dispatch","session","compliance","tasks","code quality","review"]