Confidence Check
Pre-implementation confidence assessment (≥90% required). Use before starting any implementation to verify readiness with duplicate check, architecture compliance, official docs verification, OSS references, and root cause identification.
What this skill does
# Confidence Check Skill ## Purpose Prevents wrong-direction execution by assessing confidence **BEFORE** starting implementation. **Requirement**: ≥90% confidence to proceed with implementation. **Test Results** (2025-10-21): - Precision: 1.000 (no false positives) - Recall: 1.000 (no false negatives) - 8/8 test cases passed ## When to Use Use this skill BEFORE implementing any task to ensure: - No duplicate implementations exist - Architecture compliance verified - Official documentation reviewed - Working OSS implementations found - Root cause properly identified ## Confidence Assessment Criteria Calculate confidence score (0.0 - 1.0) based on 5 checks: ### 1. No Duplicate Implementations? (25%) **Check**: Search codebase for existing functionality ```bash # Use Grep to search for similar functions # Use Glob to find related modules ``` ✅ Pass if no duplicates found ❌ Fail if similar implementation exists ### 2. Architecture Compliance? (25%) **Check**: Verify tech stack alignment - Read `CLAUDE.md`, `PLANNING.md` - Confirm existing patterns used - Avoid reinventing existing solutions ✅ Pass if uses existing tech stack (e.g., Supabase, UV, pytest) ❌ Fail if introduces new dependencies unnecessarily ### 3. Official Documentation Verified? (20%) **Check**: Review official docs before implementation - Use Context7 MCP for official docs - Use WebFetch for documentation URLs - Verify API compatibility ✅ Pass if official docs reviewed ❌ Fail if relying on assumptions ### 4. Working OSS Implementations Referenced? (15%) **Check**: Find proven implementations - Use Tavily MCP or WebSearch - Search GitHub for examples - Verify working code samples ✅ Pass if OSS reference found ❌ Fail if no working examples ### 5. Root Cause Identified? (15%) **Check**: Understand the actual problem - Analyze error messages - Check logs and stack traces - Identify underlying issue ✅ Pass if root cause clear ❌ Fail if symptoms unclear ## Confidence Score Calculation ``` Total = Check1 (25%) + Check2 (25%) + Check3 (20%) + Check4 (15%) + Check5 (15%) If Total >= 0.90: ✅ Proceed with implementation If Total >= 0.70: ⚠️ Present alternatives, ask questions If Total < 0.70: ❌ STOP - Request more context ``` ## Output Format ``` 📋 Confidence Checks: ✅ No duplicate implementations found ✅ Uses existing tech stack ✅ Official documentation verified ✅ Working OSS implementation found ✅ Root cause identified 📊 Confidence: 1.00 (100%) ✅ High confidence - Proceeding to implementation ``` ## Implementation Details The TypeScript implementation is available in `confidence.ts` for reference, containing: - `confidenceCheck(context)` - Main assessment function - Detailed check implementations - Context interface definitions ## ROI **Token Savings**: Spend 100-200 tokens on confidence check to save 5,000-50,000 tokens on wrong-direction work. **Success Rate**: 100% precision and recall in production testing.
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.