documentation-research
Fetch and cite current upstream documentation for every external dependency in scope. ISO-8601-stamped sources. Refuse memory-only references.
What this skill does
# documentation-research Phase 2 of `/shannon:forge`. Grounds every external dependency claim in fetched documentation, not training-data recall. ## Behavior contract Produces `e2e-evidence/<run-id>/documentation-research/` containing: 1. `sources/` — raw markdown of each fetched documentation page, with `<source>-<ISO-8601-timestamp>.md` naming. 2. `SUMMARY.md` — citing 3-5 verified facts per source, each linking to the local `sources/` filename. 3. `README.md` + `INDEX.md`. ## Methodology For each external dependency identified by `codebase-analysis`: 1. Prefer `context7` MCP for library docs (current, version-aware). 2. Fall back to `WebFetch` against the canonical docs URL. 3. Save the raw markdown to `sources/<lib>-<timestamp>.md`. 4. In `SUMMARY.md`, write 3-5 facts with `[source: sources/<file>]` inline citations. ## When to use - Phase 2 of `/shannon:forge`. - Before any SDK / API integration. - When training data may be stale (recently released libraries, breaking changes in current major). ## When NOT to use - Pure internal-codebase work with no external deps. - Already-fetched docs < 7 days old (cite the existing source file instead). ## Iron rules - **Refuse memory-only references.** Every external-fact claim must cite a `sources/` file. - **ISO-8601 timestamps mandatory.** Stale docs are surfaced, not silently used. - **No invented URLs.** WebFetch only against URLs the user provided or context7 returned.
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.