verify
This skill should be used when about to claim work is complete, fixed, or passing — before committing, creating PRs, or telling the user 'done'. Requires running verification commands and reading output before making success claims.
What this skill does
# Verification Before Completion Evidence before claims, always. ## The Rule No completion claims without fresh verification evidence in the current response. "Should work now" is not evidence. Run the command, read the output, then state the result. This applies before ANY transition: completing a task, moving to the next task, delegating to an agent, committing, creating a PR, or telling the user "done." Skip any step and the claim is unverified. ## The Gate Before any claim of success, completion, or readiness: 1. **Identify** what command proves the claim (test suite, build, linter) 2. **Run** it fresh — not from memory, not from a previous run 3. **Read** the full output, check exit code, count failures 4. **State** the result with evidence: "42/42 tests pass" not "tests should pass" ## What Requires What | Claim | Requires | Not Sufficient | |-------|----------|----------------| | "Tests pass" | Test output showing 0 failures | Previous run, "should pass" | | "Build succeeds" | Build command exit 0 | Linter passing | | "Bug fixed" | Failing test now passes | "Code changed, should work" | | "Regression test works" | Pass → revert fix → fail → restore → pass | Test passes once | | "Requirements met" | Line-by-line check against spec | "Tests pass" | | "Agent completed work" | Review the actual diff | Agent's self-report | ## Stop Signs About to write any of these? Stop and run the verification first: - "Should work now" / "That should fix it" - "Done!" / "All set!" / "Ready to merge" - Any expression of satisfaction before running the proof - Committing or pushing without test results in this response - Using "should", "probably", or "seems to" about untested claims - Moving to the next task without verifying the current one - Trusting an agent's self-report without checking the diff - If verification fails, state the actual failure with command output — don't go quiet ## Why This Matters Unverified claims break trust, ship broken code, and waste time on rework. "I'm confident" is not evidence. Run the command.
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.