Menu
Quick capture to Inbox. USE WHEN user says /inbox followed by text. Extracts
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Search Amazon, extract product data, and present ranked recommendations. Use when user asks to shop on Amazon, find products, compare items, or research purchases. Prioritizes review count over rating.
Write and iterate on blog articles from idea to publishable draft. Use this skill whenever the user wants to write a new article, continue working on a draft, edit or improve an existing article, or mentions /article. Covers the full lifecycle — from brainstorming and outlining to polishing and finalizing. Also triggers when the user says things like "write a blog post about...", "I have an article idea", "help me finish this draft", or "improve this article".
Interact with personal bank accounts via Enable Banking CLI to check balances, browse transactions, analyze spending, forecast cash flow, and manage alerts. Use this skill whenever the user mentions money, bank accounts, balances, transactions, spending, budgets, forecasts, cash flow, or anything related to personal finances. Also trigger when the user asks questions like "how much did I spend", "what is my balance", "my latest transactions", "cash flow forecast", or any financial query. Proactively use this skill even if the user doesn't explicitly say "banking" — any mention of expenses, income, categories like "groceries", "rent", "transport", or account aliases should trigger it.
Stress-test a raw idea before turning it into a project: reformulate, research the market with Exa deep search, grill the assumptions adversarially, then output a decision log with Go/No-Go/Pivot verdict. Use when the user says /brainstorm, 'j'ai une idée', 'je pense lancer', 'je voudrais creer', 'idée de projet', 'idée de boite', 'on devrait faire X', or shares any half-baked product/business/side-project idea they want to vet before commiting. Especially valuable when the idea is fresh, unvalidated, and the user hasn't yet decided to pursue it.
Daily and weekly brief workflows. USE WHEN user says /brief morning, /brief evening, /brief weekly, /brief monthly, or synonyms like 'start my day', 'end of day', 'weekly brief', 'monthly brief'.
Manage client relationships. USE WHEN user asks about clients, follow-ups, client emails, or who needs attention.
| name | inbox |
| description | Quick capture to Inbox. USE WHEN user says /inbox followed by text. Extracts |
| user_invocable | true |
| argument | text to capture (free text with optional |
/inbox <free text with optional #tags>
Parse the argument text:
#tag patterns from the text (e.g., #urgent, #tech, #client/xxx)Generate a short summary title (3-6 words max) from the capture content. This becomes the title field in frontmatter.
Create a new file at: Inbox/YYYY-MM-DD-HHmmss.md
date +%Y-%m-%d-%H%M%SFile content format:
---
type: note
status: inbox
tags: [inbox, <extracted_tags>]
created: YYYY-MM-DD HH:mm
source: claude-code
title: "<generated summary>"
---
## Content
<cleaned capture text with [[wikilinks]] preserved>
inbox in the tags array alongside any extracted tags[[wikilinks]] in the content as-is[inbox]# prefix when putting tags in frontmatter YAML arrayInput: /inbox #urgent Follow up with [[Alice Martin]] about the freelance contract
→ File: Inbox/2026-03-23-143022.md
→ Title: "Follow up Alice contract"
→ Tags: [inbox, urgent]
→ Body: Follow up with [[Alice Martin]] about the freelance contract
Input: /inbox Idea: use Dataview to track fact_count per project #tech #knowledge-management
→ File: Inbox/2026-03-23-150100.md
→ Title: "Dataview tracking fact_count"
→ Tags: [inbox, tech, knowledge-management]
→ Body: Idea: use Dataview to track fact_count per project