process-inbox

process-inbox is a skill for Claude Code from technicalpickles/pickled-claude-plugins. It costs 29 tokens per session (1,234 once invoked), scanned A, original, MIT.

A workflow for processing notes collected in an inbox through several stages: importing, enriching, routing, connecting, and linking them to a daily note.

In plain words
What is it for?
Running a full personal knowledge-management pipeline for notes stored in a vault.
Why use it?
It turns a pile of unprocessed notes into organized knowledge. It also shows the inbox status and identifies notes that have been waiting for a long time.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: reads .claude/ paths; mentions CLAUDE.md.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the second-brain plugin — 11 skills, 7 commands shipped together

Good fit Running a full personal knowledge-management pipeline for notes stored in a vault.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add technicalpickles/pickled-claude-plugins
Claude Code
/plugin install second-brain

Made for: Claude Code.

Or install second-brain, the plugin that ships this one along with the rest of its 11 skills, 7 commands.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for process-inbox

README.md
[![agentmods](https://agentmods.dev/badge/skills/technicalpickles/pickled-claude-plugins/process-inbox/github.svg)](https://agentmods.dev/skills/technicalpickles/pickled-claude-plugins/process-inbox)
Your own site
<a href="https://agentmods.dev/skills/technicalpickles/pickled-claude-plugins/process-inbox"><img src="https://agentmods.dev/badge/skills/technicalpickles/pickled-claude-plugins/process-inbox/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for process-inbox

Your own site · 80×15
<a href="https://agentmods.dev/skills/technicalpickles/pickled-claude-plugins/process-inbox"><img src="https://agentmods.dev/badge/skills/technicalpickles/pickled-claude-plugins/process-inbox.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 29 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,234 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00029 $0.01234
Opus 5.5 $0.00012 $0.00494
Sonnet 5.5 $0.00006 $0.00247
Haiku 4.5 $0.00003 $0.00123

Measured 1mo ago against content hash 9a278d7b2624, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

process-inbox scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/second-brain/skills/process-inbox/SKILL.md · 149 lines

How it starts

The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Process Inbox

Process accumulated inbox notes through the full pipeline: ingest, enrich, route, connect, link to daily note.

See references/pipeline.md for stage definitions and status flow.

Step 1: Load Configuration

npx @techpickles/sb config default
npx @techpickles/sb config vaults

If no vault configured:

Second brain not configured. Run /second-brain:setup first.

Load skill references:

  • second-brain:obsidian for tool mechanics
  • references/pipeline.md for stage definitions
  • references/routing-memory.md for learning loop
  • references/routing.md for scoring algorithm
  • references/connecting.md for connection discovery
  • references/daily-linking.md for daily note linking
  • references/sb-cli.md for sb command reference

Step 2: Survey Inbox

npx @techpickles/sb inbox list --detail

Parse the JSON response. Group notes by status field (notes without status are raw).

Check for stale notes (captured more than 14 days ago based on captured frontmatter field).

Present summary:

Inbox: {total} notes
  {n} raw (session notes awaiting ingestion)
  {n} ingested (insights awaiting enrichment)
  {n} enriched (notes awaiting routing)
  {n} pending-review (need your input)
  {n} routed (awaiting connection)
  {n} connected (awaiting daily linking)

{If stale notes exist:}
  Heads up: {n} notes have been in the inbox for over 2 weeks.

If inbox is empty:

Inbox is empty. Nothing to process.

Step 3: Process by Stage

Work through notes in pipeline order. Each stage picks up notes at its expected input status.

3a: Ingest raw session notes

For each note with status: raw and type: session-notes:

  • Follow the ingest skill (keeps the note whole by default, only splits on a real cross-topic signal)
  • Report: Ingested: {session filename} (default case), or Ingested: {session filename} -> {n} insights (split) (exception case)

3b: Enrich ingested insights

For each note with status: ingested and type: insight:

  • Follow the enrich skill to create proper zettelkasten notes
  • Report: Enriched: {filename}

Read the full file on GitHub · 149 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 149 lines · 29 tokens per session scan A 9a278d7b2624

Subscribe to this mod's changes

process-inbox is a skill published in the GitHub repository technicalpickles/pickled-claude-plugins (11 stars, last pushed yesterday), licensed MIT. It adds 29 tokens to every session and 1,234 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Related

Other skills, from other repositories

doc-bootstrapping

A project-documentation setup guide that creates a central set of rules, memory notes, and Diátaxis documentation folders. Diátaxis is a method that separates explanations, specifications, how-to guides, and tutorials.

VidyFoo/antigravity-skill-engine · 30 tokens

suggest-automations

Offer the three most common automations for a user as a single-choice card, from your own knowledge of their team and their apps, then build the one they choose once they confirm, or offer more. The system preloads it on onboarding threads, where the opening card already asked the user about themselves. Use it on…

n8n-io/n8n · 87 tokens

customer-journey-map

Construye un mapa de recorrido del cliente para un producto, servicio o experiencia. Úsalo cuando se te pida mapear un recorrido del cliente, crear un viaje del usuario, documentar puntos de contacto y puntos de fricción, o diseñar un mapa de experiencia. Produce un mapa de recorrido completo con etapas, puntos de…

mohitagw15856/pm-claude-skills · 86 tokens

design-handoff-brief

Transform feature briefs into structured design briefs that give designers the context they need before opening Figma. Use when asked to write a design brief, create a design handoff, brief a designer on a new feature, or translate a PRD into design requirements. Produces a brief with user goal, emotional context…

mohitagw15856/pm-claude-skills · 83 tokens

scenario-zbrush-expert

Use when an agent drives Maxon ZBrush 2026 for any task (sculpt in ZBrush, DynaMesh, ZRemesher, UVs, export, polypaint, posing, 3D print, clean up an AI mesh in ZBrush), when writing ZBrush Python (zbrush.commands) or ZScript, when the ZBrush bridge is not answering, a palette path or set() does nothing, a scripted…

scenario-labs/skills · 124 tokens

company-brain

Your team's shared, AI-ready knowledge base — people, companies, meetings, SOPs, and decisions structured so an agent can answer on your team's behalf. Team-scope sibling to second-brain. Modes — capture, compile (wiki pages + INDEX.md), query (trust-weighted, saved to outputs/), review (verify / deprecate / supersede…

coreyhaines31/makerskills · 222 tokens