[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CCKS0PDHGKF3BSPSS5CDH2":3,"skill-same:01M6CCKS0PDHGKF3BSPSS5CDH2":53},{"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":25,"linkOnly":26,"markdownContent":27,"markdownBody":28,"frontMatter":29,"refName":30,"commitSha":31,"skillDirectory":32,"forksCount":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":35,"ownerHtmlUrl":36,"ownerBlogUrl":35,"ownerDescription":37,"updatedAt":38,"install":39,"resources":52},"01M6CCKS0PDHGKF3BSPSS5CDH2","verify-this",null,"Verify a claim with fresh local evidence: restate it falsifiably, capture baseline and treatment, compare artifacts, and return VERIFIED, NOT VERIFIED, or INCONCLUSIVE.","stigmer\u002Fstigmer","stigmer","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F255479904?v=4","01M6CCFBFXXRZC4ZVNS3JSDV4W","Stigmer","01M6CCFBKY7M8QGR4GH9TT35MY",9,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fstigmer\u002Fstigmer\u002Fblob\u002Fmain\u002Fplugins\u002Fcursor-team-kit\u002Fskills\u002Fverify-this\u002FSKILL.md",[],[19,20,21,22,23,24],"verify","verify this","artifacts","baseline","capture","evidence","2026-11-10 10:12:30",false,"---\nname: verify-this\ndescription: \"Verify a claim with fresh local evidence: restate it falsifiably, capture baseline and treatment, compare artifacts, and return VERIFIED, NOT VERIFIED, or INCONCLUSIVE.\"\n---\n\n# Verify This\n\nVerification is not a recap. It proves or disproves a specific claim with repeatable evidence.\n\n## When To Use\n\n- The user asks \"verify this\", \"prove it works\", \"did this fix it\", or \"show me the evidence\".\n- A bug fix needs a before\u002Fafter repro.\n- A UI, CLI, API, performance, or memory claim needs measurement.\n- A test passes but the user-visible behavior still needs confirmation.\n\nDo not use this for vague claims like \"the code is cleaner\". Ask for a measurable claim first.\n\n## Workflow\n\n1. Restate the claim in falsifiable form: condition, metric, and threshold.\n2. Pick the smallest local surface that can disprove it.\n3. Capture a baseline from the old state: merge base, parent commit, failing branch, or current broken repro.\n4. Capture treatment from the changed state with the same command, data, warmup, and environment.\n5. Compare raw artifacts: numbers, screenshots, terminal transcripts, HTTP responses, profiles, heap snapshots, or test output.\n6. Return exactly one verdict: `VERIFIED`, `NOT VERIFIED`, or `INCONCLUSIVE`.\n\n## Local Surfaces\n\n- Code behavior: focused unit\u002Fintegration tests or a minimal repro script.\n- CLI\u002FTUI behavior: `control-cli`, terminal transcript, or demo recording.\n- UI behavior: `control-ui`, screenshots, accessibility snapshots, or browser traces.\n- API behavior: local HTTP\u002FRPC request and response diff.\n- Performance: same-machine baseline\u002Ftreatment timings or CPU profiles.\n- Memory: heap snapshots before and after the suspected operation.\n\n## Artifact Layout\n\nWhen safe to write artifacts:\n\n```text\n\u002Ftmp\u002Fverify-this\u002F\u003Cclaim-slug>\u002F\n├── claim.md\n├── timeline.md\n├── baseline\u002F\n├── treatment\u002F\n├── diff\u002F\n└── verdict.md\n```\n\nIf artifacts may contain sensitive code, prompts, screenshots, HTTP bodies, or heap data, keep only the minimal inline evidence unless the user agrees to disk storage.\n\n## Verdict Rules\n\n- `VERIFIED`: baseline and treatment differ in the predicted direction, by the claimed threshold, with no obvious confound.\n- `NOT VERIFIED`: the behavior is unchanged, moves the wrong way, or misses the threshold.\n- `INCONCLUSIVE`: no valid baseline, noisy signal, failed measurement, or an environment difference invalidates the comparison.\n\n## Output\n\nUse this shape:\n\n```text\nVERIFIED | NOT VERIFIED | INCONCLUSIVE\nClaim: \u003Cfalsifiable claim>\n\nEvidence:\n\u003Cmetric\u002Fartifact>: baseline=\u003C...>, treatment=\u003C...>, delta=\u003C...>, threshold=\u003C...>\n\nReasoning:\n\u003Cone tight paragraph naming the evidence and any confounds>\n```\n\nDo not soften a negative result. A clear `NOT VERIFIED` is useful.\n","# Verify This\n\nVerification is not a recap. It proves or disproves a specific claim with repeatable evidence.\n\n## When To Use\n\n- The user asks \"verify this\", \"prove it works\", \"did this fix it\", or \"show me the evidence\".\n- A bug fix needs a before\u002Fafter repro.\n- A UI, CLI, API, performance, or memory claim needs measurement.\n- A test passes but the user-visible behavior still needs confirmation.\n\nDo not use this for vague claims like \"the code is cleaner\". Ask for a measurable claim first.\n\n## Workflow\n\n1. Restate the claim in falsifiable form: condition, metric, and threshold.\n2. Pick the smallest local surface that can disprove it.\n3. Capture a baseline from the old state: merge base, parent commit, failing branch, or current broken repro.\n4. Capture treatment from the changed state with the same command, data, warmup, and environment.\n5. Compare raw artifacts: numbers, screenshots, terminal transcripts, HTTP responses, profiles, heap snapshots, or test output.\n6. Return exactly one verdict: `VERIFIED`, `NOT VERIFIED`, or `INCONCLUSIVE`.\n\n## Local Surfaces\n\n- Code behavior: focused unit\u002Fintegration tests or a minimal repro script.\n- CLI\u002FTUI behavior: `control-cli`, terminal transcript, or demo recording.\n- UI behavior: `control-ui`, screenshots, accessibility snapshots, or browser traces.\n- API behavior: local HTTP\u002FRPC request and response diff.\n- Performance: same-machine baseline\u002Ftreatment timings or CPU profiles.\n- Memory: heap snapshots before and after the suspected operation.\n\n## Artifact Layout\n\nWhen safe to write artifacts:\n\n```text\n\u002Ftmp\u002Fverify-this\u002F\u003Cclaim-slug>\u002F\n├── claim.md\n├── timeline.md\n├── baseline\u002F\n├── treatment\u002F\n├── diff\u002F\n└── verdict.md\n```\n\nIf artifacts may contain sensitive code, prompts, screenshots, HTTP bodies, or heap data, keep only the minimal inline evidence unless the user agrees to disk storage.\n\n## Verdict Rules\n\n- `VERIFIED`: baseline and treatment differ in the predicted direction, by the claimed threshold, with no obvious confound.\n- `NOT VERIFIED`: the behavior is unchanged, moves the wrong way, or misses the threshold.\n- `INCONCLUSIVE`: no valid baseline, noisy signal, failed measurement, or an environment difference invalidates the comparison.\n\n## Output\n\nUse this shape:\n\n```text\nVERIFIED | NOT VERIFIED | INCONCLUSIVE\nClaim: \u003Cfalsifiable claim>\n\nEvidence:\n\u003Cmetric\u002Fartifact>: baseline=\u003C...>, treatment=\u003C...>, delta=\u003C...>, threshold=\u003C...>\n\nReasoning:\n\u003Cone tight paragraph naming the evidence and any confounds>\n```\n\nDo not soften a negative result. A clear `NOT VERIFIED` is useful.\n",{"name":5,"description":7},"main","49002d2ddc1f123a8d1148f6c6d73d7b385bb0b1","plugins\u002Fcursor-team-kit\u002Fskills\u002Fverify-this",6,"https:\u002F\u002Fgithub.com\u002Fstigmer\u002Fstigmer","https:\u002F\u002Fstigmer.ai","https:\u002F\u002Fgithub.com\u002Fstigmer","The open-source backend for the agents in your product.","2026-11-11 20:28:47",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add stigmer\u002Fstigmer --skill verify-this",{"tool":45,"command":46},"bunx","bunx skills add stigmer\u002Fstigmer --skill verify-this",{"tool":48,"command":49},"pnpm","pnpm dlx skills add stigmer\u002Fstigmer --skill verify-this","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fstigmer\u002Fstigmer\u002Fblob\u002Fmain\u002Fplugins\u002Fcursor-team-kit\u002Fskills\u002Fverify-this\u002FSKILL.md",true,[],[54,84,104,122,136,151],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":73,"publishedAt":25},"01M6CCSERKR4YRSZJ2TB6B0X60","writing-hookify-rules","This skill should be used when the user asks to \"create a hookify rule\", \"write a hook rule\", \"configure hookify\", \"add a hookify rule\", or needs guidance on hookify rule syntax and patterns.","https:\u002F\u002Fgithub.com\u002Fstigmer\u002Fstigmer\u002Fblob\u002Fmain\u002Ftest\u002Fsupport\u002Ffixtures\u002Fclaude-plugins\u002Fhookify\u002Fskills\u002Fwriting-rules\u002FSKILL.md",[60,65,68],{"categoryNo":61,"categoryName":62,"taxonomyType":63,"taxonomyTypeDesc":64},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":66,"categoryName":67,"taxonomyType":63,"taxonomyTypeDesc":64},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":69,"categoryName":70,"taxonomyType":71,"taxonomyTypeDesc":72},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[74,75,76,77,78,79,80,81,82,83],"writing","Writing Hookify Rules","Rules","hookify rules","create","guidance","user","write","configure","syntax",{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":96,"publishedAt":25},"01M6CCSC63RKCGC2S1EZDEMXZE","sql-migrations","Write safe database schema migrations - reversible steps, online index builds, and backfills in batches.","https:\u002F\u002Fgithub.com\u002Fstigmer\u002Fstigmer\u002Fblob\u002Fmain\u002Ftest\u002Fconformance\u002Ffixtures\u002Fworking-agent\u002Fskills\u002Fsql-migrations\u002FSKILL.md",[90,93],{"categoryNo":91,"categoryName":92,"taxonomyType":63,"taxonomyTypeDesc":64},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":94,"categoryName":95,"taxonomyType":71,"taxonomyTypeDesc":72},"01JBSEEDCAT000000000000033","数据分析师",[97,98,99,100,81,101,102,103],"sql","sql migrations","migrations","schema","index","database","safe",{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":25},"01M6CCS9Q8E0R3TYHPZHCPN0JZ","repo-conventions","How to change Go code in this repository - error wrapping, table-driven tests, doc comments, no new dependencies, and running go test before finishing.","https:\u002F\u002Fgithub.com\u002Fstigmer\u002Fstigmer\u002Fblob\u002Fmain\u002Ftest\u002Fconformance\u002Ffixtures\u002Fworking-agent\u002Fskills\u002Frepo-conventions\u002FSKILL.md",[],[111,112,113,114,115,116,117,118,119,120,121],"repo","repo conventions","table","go","test","change","doc comments","code","repository","doc","how",{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":25},"01M6CCS7F2D1YZ9H3N63XTEV09","incident-postmortem","Write a blameless incident postmortem - timeline, impact, root cause, contributing factors and follow-up actions with owners.","https:\u002F\u002Fgithub.com\u002Fstigmer\u002Fstigmer\u002Fblob\u002Fmain\u002Ftest\u002Fconformance\u002Ffixtures\u002Fworking-agent\u002Fskills\u002Fincident-postmortem\u002FSKILL.md",[],[129,130,81,131,132,133,134,135],"incident postmortem","postmortem","contributing","actions","timeline","owners","up",{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":146,"publishedAt":25},"01M6CCS4W1D2K257KHC40HS8JG","data-analysis","Summarise a data export or table - lead with the key finding and give every number its baseline or comparison.","https:\u002F\u002Fgithub.com\u002Fstigmer\u002Fstigmer\u002Fblob\u002Fmain\u002Ftest\u002Fconformance\u002Ffixtures\u002Fworking-agent\u002Fskills\u002Fdata-analysis\u002FSKILL.md",[142,145],{"categoryNo":143,"categoryName":144,"taxonomyType":63,"taxonomyTypeDesc":64},"01JBSEEDCAT000000000000013","分析与可视化",{"categoryNo":94,"categoryName":95,"taxonomyType":71,"taxonomyTypeDesc":72},[147,148,149,22,113,150],"analysis","data analysis","data","export",{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":157,"publishedAt":25},"01M6CCS2MNQYK9S24AYHJAVPWF","customer-support","Answer customer questions about orders, returns and refunds from the written policies and the order system, ending with a clear next step.","https:\u002F\u002Fgithub.com\u002Fstigmer\u002Fstigmer\u002Fblob\u002Fmain\u002Ftest\u002Fconformance\u002Ffixtures\u002Fworking-agent\u002Fskills\u002Fcustomer-support\u002FSKILL.md",[],[158,159,160,161,162,163],"support","customer","customer support","system","refunds","returns"]