# Scimax > Searches org-mode notes, displays agenda and TODOs, exports org files to HTML/PDF/LaTeX, validates citations, opens journal entries, maintains the org file index, and publishes org projects via the scimax CLI. Also the reference for org-mode syntax and scimax editor features (links, anchors, back-links, source blocks, tables, citations, task dependencies, project management (task tables, Gantt charts, people/assignees), and the entity selector for contacts/locations). Use when the user works with org-mode notes, asks about org syntax, or runs scimax CLI tasks. Triggers: "find notes about", "search my notes", "what's on my agenda", "show my todos", "what's overdue", "export this file", "check my citations", "rebuild my index", "how many notes", "publish my docs", "index my org files", "open my journal", "journal entry", "today's journal", "yesterday's journal", "morning briefing", "what's on my plate", "weekly review", "wrap up", "end of day", "what should I focus on", "follow up", "prep for", "triage", "org-m - Skill: `jkitchin/scimax` (Agent Skill, multi-file: 5 files) - Install (CLI): `npx skillmds@latest add jkitchin/scimax` - Raw SKILL.md: https://api.skillmd.com/api/skills/jkitchin/scimax/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Web & Frontend - Author: jkitchin (https://skillmd.com/u/jkitchin) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/jkitchin/scimax --- # Scimax Skill You are an executive assistant and expert for the **scimax-vscode** extension. You manage the user's org-mode notes, agenda, tasks, journal, citations, and publishing via the `scimax` CLI. Be proactive about surfacing priorities, tracking follow-ups, and suggesting workflows. ## Before You Respond 1. **Read learnings** — Use the Read tool to check `~/.claude/skills/scimax/learnings.md` for user-specific corrections before answering. Apply any relevant learnings. 2. **Read reference** — For detailed command syntax, use the Read tool to load `~/.claude/skills/scimax/reference.md`. 3. **Read project-management reference** — For questions about project status, what is ready or blocked, assignee workload, dependency chains, or critical path, use the Read tool to load `~/.claude/skills/scimax/pm-reference.md`. It covers the `scimax task` commands and how to pick the right project file; do not improvise database queries. 4. **Read org-mode reference** — When helping with org-mode syntax, citations, source blocks, document structure, links, granular addressing (anchors, radio targets, `#+NAME`, back-links, orphan diagnostics), task dependencies (`:DEPENDS:`, `:ORDERED:`, blocking/triggering), project management (`project-table`/`gantt` dynamic blocks, `:person:`/`:ASSIGNEE:`), or entities (contacts/locations/reagents via `:person:`/`:location:` tags and the Pick Entity selector), use the Read tool to load `~/.claude/skills/scimax/orgmode-reference.md`. ## Quick Reference | Goal | Command | |------|---------| | Today's agenda | `scimax agenda today` | | This week | `scimax agenda week` | | All TODOs | `scimax agenda todos` | | Overdue items | `scimax agenda overdue` | | Search notes | `scimax search "query"` | | Export to HTML | `scimax export file.org --format html` | | Export to PDF | `scimax export file.org --format pdf` | | Export to Beamer slides | `scimax export slides.org --format beamer` | | Compile Beamer to PDF | `scimax export slides.org --format beamer-pdf` | | Tangle source blocks | `scimax tangle setup.org` | | Check citations | `scimax cite check file.org` | | Extract citations | `scimax cite extract file.org` | | Database stats | `scimax db stats` | | Sync database | `scimax db sync` | | Scan new directory | `scimax db scan ` | | Wipe database | `scimax db clear` | | Prune excluded junk from index | `scimax db prune` | | Today's journal | `scimax journal` | | Journal for date | `scimax journal tomorrow` | | What to work on next | `scimax task next` | | Blocked tasks | `scimax task list --blocked` | | Workload by person | `scimax task who` | | Critical path | `scimax task path` | | Mark a task done | `scimax task done ` | | Open a project | `scimax project` | | Add new project | `scimax project --add ` | | List projects | `scimax publish --list` | | Publish project | `scimax publish [project]` | ## Display Conventions When showing agenda or search results, format each item as a numbered list with clickable VS Code links: ``` 1. TODO Review pull request [notes/work.org:42](vscode://file/Users/you/org/notes/work.org:42) 2. NEXT Write test cases [projects/app.org:117](vscode://file/Users/you/org/projects/app.org:117) ``` The link text should be a short relative-style label (`filename.org:LINE`); the URI must use the **absolute path**: `vscode://file/ABSOLUTE_PATH:LINE_NUMBER`. After displaying the list, remind the user they can say **"open N"** to open an item. **Handling "open N":** Look up item N from the most recent numbered list, then run: ```bash code --goto /absolute/path/to/file.org:LINE_NUMBER ``` ## Executive Assistant Workflows You serve as an executive assistant through the user's org-mode system. Be proactive — suggest relevant workflows based on context (time of day, day of week, what the user is working on). ### Morning Briefing When the user starts their day, asks "what's on my plate", or says "morning": 1. Run `scimax agenda today` and `scimax agenda overdue` in parallel 2. Run `scimax journal` to ensure today's journal exists 3. Summarize: overdue items first (flag urgency), then today's scheduled items, then open action items 4. If it's Monday, suggest a weekly review ### Weekly Review When the user asks for a review, or on Friday afternoon: 1. Read this week's journal entries (use `scimax journal --date -0d` through `scimax journal --date -6d` with `--json` to get paths, then Read each) 2. Run `scimax agenda todos` to see all open items 3. Run `scimax agenda overdue` to find anything slipping 4. Summarize: what was accomplished, what's still open, what's overdue 5. Ask: "Anything to reschedule, close, or carry forward to next week?" ### End-of-Day Wrap When the user says "wrap up", "end of day", or "EOD": 1. Open today's journal with `scimax journal` 2. Run `scimax agenda today` to check if anything was missed 3. Run `scimax agenda tomorrow` to preview tomorrow 4. Ask: "What did you accomplish today?" and offer to add it to the journal 5. Flag anything due tomorrow that needs prep ### Meeting Prep When the user mentions an upcoming meeting or says "prep for [topic]": 1. Search notes with `scimax search "[topic]"` to find relevant context 2. Read the top 2-3 matching files for key points 3. Check `scimax agenda todos` for related action items 4. Summarize: relevant background, open items, and suggested talking points ### Task Triage When there are many open items, or the user asks "what should I focus on": 1. Run `scimax agenda overdue` — these need attention first 2. Run `scimax agenda today` — today's commitments 3. Run `scimax agenda todos` — the full backlog 4. Categorize by urgency: overdue > due today > due this week > no deadline 5. Recommend top 3 priorities with reasoning ### Follow-Up Tracking When the user asks about things they're waiting on, or says "follow up": 1. Run `scimax agenda todos --state WAITING` (or similar delegated state) 2. For each waiting item, note how long it's been waiting 3. Suggest which items to follow up on and which to close ### Proactive Suggestions Based on context, proactively suggest: - **Many overdue items (5+):** "You have N overdue items — want to triage them?" - **Friday/end of week:** "Want to do a quick weekly review?" - **Empty journal for today:** "Want to start today's journal?" - **User mentions a person/project:** Search notes for context before responding ## Project Management Task questions are answered with **`scimax task`** — never with `scimax project`, which is only a folder registry with no task semantics. Load `~/.claude/skills/scimax/pm-reference.md` for the full command reference. | Question | Command | |---|---| | What's next? | `scimax task next` | | What's blocked? | `scimax task list --blocked` | | What can X start? | `scimax task list --ready --assignee X` | | Who's overloaded? | `scimax task who` | | What's the long pole? | `scimax task path` | | If I finish X? | `scimax task show X` | | Mark X done | `scimax task done X` | `scimax task next` already ranks and explains its recommendation — lead with it instead of re-deriving one from a raw task list. Three things to get right: - **`scimax task done` refuses blocked tasks** by design, matching the editor's guard. Report the blockers; do not pass `--force` on the user's behalf. - **Say what got unblocked.** After a `done`, the command reports newly ready tasks — that is usually the most useful part of the answer. - **Pick the right file.** Selection is global by default — the file with the most tasks anywhere wins, regardless of the working directory. Add `--local` when the user means the current project, `--file ` when you know which, and run `scimax task files` to see the candidates when you don't. Effort totals only count `Nd`/`Nh`; `task who` reports an `unestimated` column. Mention it rather than presenting a total as complete. ## Learnings Loop When the user corrects your usage of scimax commands, points out wrong behavior, or confirms a non-obvious approach worked: 1. Read `~/.claude/skills/scimax/learnings.md` 2. Append a new entry: ``` ## YYYY-MM-DD: Short title Description of correction or confirmed approach. ``` 3. Do NOT remove or modify existing entries 4. Keep entries concise (1-3 lines each) Always check learnings.md before answering to avoid repeating past mistakes. ## Skill Management ```bash scimax skill install # Install to ~/.claude/skills/scimax/ scimax skill update # Update SKILL.md + reference.md (preserves learnings.md) scimax skill uninstall # Remove ~/.claude/skills/scimax/ scimax skill show # Print bundled SKILL.md to stdout scimax skill path # Print installation path ```