dd-verification
Verify claims in pitch decks and founder statements using multiple independent sources. Use when analyzing any claim about market size, traction, team background, or competitive positioning.
What this skill does
# Claim Verification Methodology
When analyzing claims from pitch decks, founder statements, or company materials, follow this rigorous verification process.
## Verification Levels
Assign one of these confidence levels to every claim:
| Level | Definition | Requirements |
|-------|------------|--------------|
| **VERIFIED** | Confirmed via 2+ independent sources | Multiple credible sources agree |
| **PARTIALLY VERIFIED** | Some evidence supports, gaps remain | One credible source + logical consistency |
| **UNVERIFIED** | Cannot confirm with available data | No independent sources found |
| **CONTRADICTED** | Evidence conflicts with claim | Sources disagree with stated claim |
## Verification Process
### 1. Identify the Claim
Extract the specific, testable assertion:
- ❌ "We're growing fast" (vague)
- ✅ "We grew 300% YoY in 2024" (specific, testable)
### 2. Find Independent Sources
Never rely solely on company-provided materials. Seek:
- Public filings (SEC, state records)
- Third-party data providers (Crunchbase, PitchBook, LinkedIn)
- Press coverage (with dates)
- Customer reviews and testimonials
- Industry reports from analysts
### 3. Cross-Reference
Compare across sources:
- Do numbers align within reasonable variance (±10%)?
- Are timelines consistent?
- Do different sources tell the same story?
### 4. Document Everything
For each verified claim, record:
```json
{
"claim": "The specific claim text",
"confidence": "VERIFIED | PARTIALLY VERIFIED | UNVERIFIED | CONTRADICTED",
"sources": [
{"name": "Source name", "url": "URL if available", "date": "YYYY-MM-DD"}
],
"notes": "Any caveats or context"
}
```
## Red Flags
Watch for these warning signs:
- Round numbers without context ("$10M ARR exactly")
- Claims that can't be independently verified
- Metrics that don't match industry standards
- Vague timeframes ("recently", "soon")
- Comparisons without clear methodology
## Output Format
Include a verification summary in your analysis:
```json
{
"verification_summary": {
"total_claims_analyzed": 15,
"verified": 8,
"partially_verified": 4,
"unverified": 2,
"contradicted": 1
},
"key_concerns": [
"Market size claim contradicted by industry reports",
"Founder employment dates don't match LinkedIn"
]
}
```
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.