From career
Given a classified inbox entry (from voice-ingest or text input), execute the proposed route — create tasks, update CRM rows, draft follow-ups, propose ground-truth edits. Always confirms each side-effect before committing. Marks the inbox entry routed when done.
npx claudepluginhub danielrosehill/claude-code-plugins --plugin careerThis skill is limited to using the following tools:
The "do something with the inbox entry" half of the capture pipeline. Reads the classified inbox file, executes the route appropriate to its classification, confirms each side-effect.
Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Share bugs, ideas, or general feedback.
The "do something with the inbox entry" half of the capture pipeline. Reads the classified inbox file, executes the route appropriate to its classification, confirms each side-effect.
$ARGUMENTS:
<inbox-path> — path to an inbox entry (relative to WORKING_FOLDER or absolute).--reclassify=<class> — override the inbox file's classification.--dry-run — show what would happen, don't write./career:capture route inbox/2026-04-28-1430.md
/career:capture route inbox/2026-04-28-1430.md --reclassify=retrospective
/career:capture route inbox/2026-04-28-1430.md --dry-run
Read the inbox file. Check frontmatter status is pending-route. If routed, ask whether to re-route (rare).
Resolve effective classification: --reclassify if set, else frontmatter classification.
quick-noteRead transcript. Extract:
schedule-manager:create-task with title + optional due date inferred from transcript.crm/companies.md (status=watching, lens=employer by default — user can edit).Show each proposed write as a diff. Confirm per-item (multi-step AskUserQuestion or numbered y/n list). Execute confirmed items.
If schedule-manager companion is missing, fall back to writing to ${WORKING_FOLDER}/tasks-inbox.md (an append-only file the user can later sync manually).
retrospectiveRead transcript. Extract:
Propose:
track-status row update on crm/outreach.md for the counterparty.draft-outreach for the follow-up if a follow-up was mentioned.schedule-manager:create-event for the future meeting if mentioned.Each proposal shown as a preview. Confirm per-item.
strategic-dumpRead transcript. Extract topics that look like:
Propose:
## Strategic notes — {{date}} section to ${WORKING_FOLDER}/strategic-dumps.md with the cleaned transcript.ground-truth.md. Don't write — surface the diff and recommend /career:ground-truth edit-section for the affected sections.${WORKING_FOLDER}/research-queue.md (append-only).unclearDon't route. Update frontmatter status: parked with a one-line note. Tell user: "left in inbox — re-run with --reclassify=<class> once intent is clear."
After successful routing, update frontmatter:
status: routed
routed-at: {{ISO timestamp}}
route-summary: {{1 line of what was done}}
Append a ## Route log section listing every side-effect:
## Route log
- 2026-04-28 14:42 — created task "follow up with Jane" via schedule-manager
- 2026-04-28 14:42 — drafted follow-up: drafts/2026-04-28-snowglobe-jane.md
inbox: <path> → routed
side-effects:
- <effect 1>
- <effect 2>
...
next:
- if drafts created: /career:outreach send <draft-path>
- if ground-truth deltas surfaced: /career:ground-truth edit-section <section>
--dry-run must produce identical proposal output to a live run, just without writes.status is the source of truth for routed/unrouted.--reclassify.