route
Analyze an enriched note and route to the best vault destination. Stage 3 of the processing pipeline.
What this skill does
# Route Stage
Analyze an enriched note against routing memory, vault rules, and generic signals. Move to destination or mark for review.
See `references/pipeline.md` for stage definitions and status flow.
See `references/routing.md` for the scoring algorithm.
See `references/routing-memory.md` for the correction and learning loop.
## Input
An enriched note in the inbox with `status: enriched`.
## Process
1. Load routing context:
- Read `.routing-memory.md` from vault root (create with defaults if missing)
- Read vault CLAUDE.md for disambiguation rules
- Run `sb vault structure` for available destinations
- Run `sb note context --note "{note-path}"` for keywords and signals
2. Score destinations (priority order):
a. Check `.routing-memory.md` corrections for matching topics/keywords
b. Check `.routing-memory.md` learned patterns
c. Apply vault CLAUDE.md disambiguation rules
d. Apply generic signal scoring (per `references/routing.md`)
3. Apply threshold:
- Score >= `auto-route-threshold`: auto-route, move file, set `status: routed`
- Score < threshold: set `status: pending-review`, return without moving
4. If auto-routing, move the file:
```bash
npx @techpickles/sb note move --from "{note-path}" --to "{destination}/"
```
Update frontmatter: `status: routed`
5. If pending-review, present suggestions to human (when called by orchestrator):
- Show top 2-3 destinations with scores and reasoning
- Include "Leave in inbox" option
- If user overrides suggestion, capture correction to `.routing-memory.md`
## Capturing Corrections
When the user picks a destination different from the top suggestion:
1. Ask: "Quick note on why {chosen} over {suggested}?"
2. Append to `## Corrections` in `.routing-memory.md`:
```
- {YYYY-MM-DD}: "{note title}" routed to "{suggested}", corrected to "{chosen}"
Reason: {user's reason}
```
## Output
- Note moved to destination with `status: routed`, OR
- Note marked `status: pending-review` for human input
## Constraints
- Only suggest destinations from `sb vault structure` output
- Always include "Leave in inbox" for pending-review notes
- Show reasoning for all suggestions
- Capture corrections on every override (this is how routing improves)
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.