inbox-triage
Process notes in 00-Inbox/ into the correct PARA location with frontmatter filled in. Use when the user asks to "triage inbox", "process inbox", "sort inbox", or "clear inbox".
What this skill does
# Inbox Triage
Read all notes in the inbox folder, classify each into its PARA destination, propose frontmatter values, and move them. Each move is shown to the user before execution.
## Settings
Read `.claude/bulletjournal.local.md` (use Read tool). Parse YAML frontmatter:
| Variable | Key | Default |
|----------|-----|---------|
| `INBOX_PATH` | `inbox_path` | `00-Inbox` |
| `PROJECTS_PATH` | `projects_path` | `10-Projects` |
| `AREAS_PATH` | `areas_path` | `20-Areas` |
| `RESOURCES_PATH` | `resources_path` | `30-Resources` |
| `ARCHIVE_PATH` | `archive_path` | `40-Archive` |
Run `/bulletjournal:init` to create this file. Use these variables for all path references below.
## PARA Destinations
| Folder | When to use |
|--------|-------------|
| `{PROJECTS_PATH}/` | Has a defined outcome and end date |
| `{AREAS_PATH}/` | Ongoing responsibility with no end date |
| `{RESOURCES_PATH}/` | Reference material, research, read-later |
| `{ARCHIVE_PATH}/` | Already done, inactive, or historical |
## Step-by-Step
### 1. List inbox notes
```bash
ls {INBOX_PATH}/
```
If empty, report "`{INBOX_PATH}/` is empty — nothing to triage." and stop.
### 2. Read each note
Read each file in `00-Inbox/`. Extract: title, any existing tags/frontmatter, body content.
### 3. Classify and propose frontmatter
For each note, determine:
- **Destination folder** (PARA logic above)
- **Frontmatter fields** (for action notes going to 10-Projects/ or 20-Areas/):
- `status`: `seed` (default for new items)
- `domain`: one of `apps | career | wellness | personal | learning | people`
- `urgency`: 1–5
- `importance`: 1–5
- `effort`: 1–5
- `impact`: 1–5
- `next-action`: first concrete step
- `tags`: `#action` for projects/areas, `#resource` for 30-Resources/
Use qmd to check for existing related notes before classifying:
```
ToolSearch select:mcp__qmd__query
mcp__qmd__query "note title or key concept"
```
### 4. Present triage plan
Show a table before making any moves:
```
| Note | → Destination | Status | Domain | Urgency | Importance | Next Action |
|------|--------------|--------|--------|---------|------------|-------------|
| filename.md | 10-Projects/ | seed | apps | 3 | 4 | Write spec |
```
Ask: "Apply this triage? (yes / edit / skip [filename])"
Wait for user confirmation before proceeding.
### 5. Apply moves
For each approved note:
1. Update frontmatter with proposed values (use Edit)
2. Move file to destination folder (use Bash `mv`)
3. Update `created` and `updated` dates if missing
### 6. Confirm
Report how many notes were triaged:
```
Triaged 4 notes: 2 → 10-Projects/, 1 → 30-Resources/, 1 → 40-Archive/
```
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.