verify-quality-a
Quality verification framework — dimensions, severity levels, grading criteria
What this skill does
> **Action skill** — Quality verification procedures: dimensions, severity grading, production readiness checks.
# Quality Standards
## Verification Dimensions
**Design quality** — Are abstractions earning their complexity? Dependencies pointing right? Module boundaries in the right places? Hidden coupling?
**Code integrity** — Is the code genuine or performative? Do tests verify real behavior? Does error handling actually handle errors?
**Code cleanliness** — Unnecessary defensive code? Over-engineered abstractions? Clear naming? Dead code?
**Production readiness** — Tests pass? No hardcoded secrets? Errors handled? Dependencies pinned?
## Finding Severity
**Critical** (must fix) — Crashes, data loss, security vulnerabilities. Fake code that will fail in production. Missing error handling for common failure modes.
**Warning** (should fix) — Design issues that will cause problems at scale. Inconsistencies that will confuse future sessions. Tests that don't verify real behavior.
**Suggestion** (consider) — Readability improvements. Minor naming inconsistencies. Simplification opportunities.
## Grading
- **A**: Clean, well-tested, good design. No critical or warning findings.
- **B**: Mostly clean. Minor warnings, no criticals.
- **C**: Functional but has warnings that should be addressed.
- **D**: Has critical issues or significant design concerns.
- **F**: Fake code, missing tests, or fundamental design problems.
Finding no issues is valid. Don't invent problems. Be specific — every finding needs path, line, description.
## Production Readiness Checks
Every check follows: state what you're checking, run the actual command, show the output, render verdict with evidence.
- **Functionality**: Tests pass (run them), no skipped tests, critical paths traced
- **Security**: No hardcoded secrets (grep for password/secret/api_key/token), no debug endpoints, input validation present
- **Stability**: Errors handled not swallowed, no silent failures, appropriate logging
- **Dependencies**: Pinned versions, lock files present, audit for known vulnerabilities
## Output Format
```
### [PASS|FAIL] {Check name}
COMMAND: what you ran
OUTPUT: what you saw
VERDICT: Pass/Fail — brief reason
```
Overall verdict: READY or NOT READY. Don't pass checks you didn't actually run.
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.