dd-report-format
Standard output format for due diligence analysis reports. Use when producing your final analysis to ensure consistency across all specialist agents.
What this skill does
# Due Diligence Report Format
All specialist agents must output their analysis in this standardized JSON format. This enables automated synthesis by the Deal Lead agent.
## Standard Report Structure
```json
{
"metadata": {
"agent": "dd-{specialist}",
"company": "Company Name",
"analysis_date": "2024-01-15T10:30:00Z",
"version": "1.0"
},
"executive_summary": {
"headline": "One-sentence assessment",
"recommendation": "POSITIVE | NEUTRAL | NEGATIVE | CRITICAL",
"confidence": "HIGH | MEDIUM | LOW",
"key_findings": [
"Finding 1",
"Finding 2",
"Finding 3"
]
},
"risk_assessment": {
"overall_score": 35,
"category_scores": {
"category_name": {
"score": 30,
"weight": 0.25,
"rationale": "Brief explanation"
}
},
"red_flags": [
{
"severity": "HIGH | MEDIUM | LOW",
"description": "Description of the red flag",
"evidence": "Supporting evidence",
"mitigation": "Possible mitigation or none"
}
],
"green_flags": [
{
"description": "Positive indicator",
"evidence": "Supporting evidence"
}
]
},
"detailed_analysis": {
"section_name": {
"findings": "Detailed analysis text",
"data": {},
"sources": ["S1", "S2"]
}
},
"sources": [
{
"id": "S1",
"name": "Source name",
"url": "URL",
"tier": 1,
"access_date": "2024-01-15"
}
],
"verification_summary": {
"total_claims": 15,
"verified": 10,
"partially_verified": 3,
"unverified": 1,
"contradicted": 1
},
"follow_up_items": [
{
"priority": "HIGH | MEDIUM | LOW",
"description": "Item requiring further investigation",
"assigned_to": "dd-{specialist} or HUMAN"
}
]
}
```
## Risk Scoring
Use a 0-100 scale where:
- **0-20**: Minimal risk (green light)
- **21-35**: Low risk (proceed with standard diligence)
- **36-50**: Moderate risk (proceed with caution)
- **51-70**: High risk (significant concerns)
- **71-100**: Critical risk (major red flags)
## File Naming Convention
Save your report to the shared folder as:
```
/shared-out/{your-domain}-analysis/{company_name}_{date}.json
```
Example:
```
/shared-out/founder-analysis/acme_corp_2024-01-15.json
```
## Markdown Summary
In addition to JSON, create a human-readable summary:
```
/shared-out/{your-domain}-analysis/{company_name}_{date}_summary.md
```
This should include:
- Executive summary (2-3 paragraphs)
- Key findings (bullet points)
- Risk assessment visualization
- Recommended actions
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.