verify-this
Verify a claim with fresh local evidence: restate it falsifiably, capture baseline and treatment, compare artifacts, and return VERIFIED, NOT VERIFIED, or INCONCLUSIVE.
What this skill does
# Verify This Verification is not a recap. It proves or disproves a specific claim with repeatable evidence. ## When To Use - The user asks "verify this", "prove it works", "did this fix it", or "show me the evidence". - A bug fix needs a before/after repro. - A UI, CLI, API, performance, or memory claim needs measurement. - A test passes but the user-visible behavior still needs confirmation. Do not use this for vague claims like "the code is cleaner". Ask for a measurable claim first. ## Workflow 1. Restate the claim in falsifiable form: condition, metric, and threshold. 2. Pick the smallest local surface that can disprove it. 3. Capture a baseline from the old state: merge base, parent commit, failing branch, or current broken repro. 4. Capture treatment from the changed state with the same command, data, warmup, and environment. 5. Compare raw artifacts: numbers, screenshots, terminal transcripts, HTTP responses, profiles, heap snapshots, or test output. 6. Return exactly one verdict: `VERIFIED`, `NOT VERIFIED`, or `INCONCLUSIVE`. ## Local Surfaces - Code behavior: focused unit/integration tests or a minimal repro script. - CLI/TUI behavior: `control-cli`, terminal transcript, or demo recording. - UI behavior: `control-ui`, screenshots, accessibility snapshots, or browser traces. - API behavior: local HTTP/RPC request and response diff. - Performance: same-machine baseline/treatment timings or CPU profiles. - Memory: heap snapshots before and after the suspected operation. ## Artifact Layout When safe to write artifacts: ```text /tmp/verify-this/<claim-slug>/ ├── claim.md ├── timeline.md ├── baseline/ ├── treatment/ ├── diff/ └── verdict.md ``` If 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. ## Verdict Rules - `VERIFIED`: baseline and treatment differ in the predicted direction, by the claimed threshold, with no obvious confound. - `NOT VERIFIED`: the behavior is unchanged, moves the wrong way, or misses the threshold. - `INCONCLUSIVE`: no valid baseline, noisy signal, failed measurement, or an environment difference invalidates the comparison. ## Output Use this shape: ```text VERIFIED | NOT VERIFIED | INCONCLUSIVE Claim: <falsifiable claim> Evidence: <metric/artifact>: baseline=<...>, treatment=<...>, delta=<...>, threshold=<...> Reasoning: <one tight paragraph naming the evidence and any confounds> ``` Do not soften a negative result. A clear `NOT VERIFIED` is useful.
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.