onboarding-analyzer
Gather and analyze source material for onboarding documentation. Creates source_inventory.md and extraction_tables.md. Triggered by onboarding-start during source-material-gathering and key-information-extraction phases.
What this skill does
# Onboarding Analyzer
Gather source material and extract key information from a codebase for onboarding documentation.
## Workflow
### Phase 1: Source Material Gathering
Create `{name}_source_inventory.md` with the following procedure:
**1.1 Identify Keywords**
- Identify the most general keyword for the feature (e.g., "auth", "cache", "validation")
- Break it into related terms (e.g., "auth" → "auth", "login", "token", "session")
**1.2 BM25 Search**
- Uses `git ls-files` to search all tracked files. Pass each term with `-t`:
```bash
uv run /path/to/skill/scripts/search.py -t auth -t login -t token
```
VERY IMPORTANT: YOU MUST USE search.py using uv.
- Record top results with path and 1-2 sentence summary
- For each file found, note:
- File path
- Entry points (main functions, exports)
- Brief 1-line description
**1.3 Identify Plans/Specs**
- Search for design docs, specs, requirements:
```bash
uv run /path/to/skill/scripts/search.py -t spec -t design -t plan
```
- Note if absent.
### Phase 2: Key Information Extraction
Create `{name}_extraction_tables.md` with structured tables:
**2.1 Function Table**
| Function | File:Lines | Purpose |
|----------|-----------|---------|
| `foo()` | `main.py:42-50` | Initializes the config |
| `bar()` | `main.py:52-80` | Processes input data |
**2.2 Dependency Table**
| Dependency | Version/Source | Used By |
|------------|----------------|---------|
| `anthropic` | PyPI | `llm.py` |
| `requests` | PyPI | `api.py` |
**2.3 Data Flow**
Document the "happy path":
1. Entry: `main()` receives request
2. Calls: `validate()` checks input
3. Calls: `process()` does work
4. Returns: result to caller
## Key Questions to Answer
During gathering:
- What feature/phase is being documented?
- Which files are main implementation?
- What existing documentation exists?
During extraction:
- What are the main functions/classes?
- What calls what?
- What external APIs are used?
## Success Criteria
`{name}_source_inventory.md`:
- [ ] Keywords and related terms listed
- [ ] Files found via BM25 search with summaries and entry points
- [ ] Plans/specs noted (or marked absent)
`{name}_extraction_tables.md`:
- [ ] Function table with accurate line numbers
- [ ] Dependency table with versions
- [ ] Data flow from entry to exit documented
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.