auto-process-a

Route inbox notes to PARA destinations and update living docs.

1|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/JSai23/claude-tooling --skill auto-process-a
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auto-process-a
Source: https://github.com/JSai23/claude-tooling/tree/main/plugins/vault/skills/auto-process-a
Command: npx skills add https://github.com/JSai23/claude-tooling --skill auto-process-a

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the routine inbox workflow: reading intent, determining the correct PARA destination, and moving notes from 0-Inbox to their proper living docs, while updating references.

Core Features & Use Cases

  • Read frontmatter signals (filing-hint, context, source, type, tags) to infer intent and destination.
  • Determine destination through a cascading routing logic: project, area, resource, or archive/flag for user review.
  • Archive the original item, fix/frontmatter normalization, rename to a date-based slug, and move to the target area.
  • Update living docs and establish connections between related notes to maintain a coherent knowledge base.

Quick Start

Place notes in 0-Inbox and run the auto-process-a workflow to file them into the correct PARA destination.

Frequently Asked Questions about auto-process-a

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate inbox triage and filing notes to PARA destinations?

Automate inbox triage by reading frontmatter signals like filing-hint and context to route notes to PARA destinations. The workflow archives originals, normalizes frontmatter, renames items to a date-based slug, and moves them to the correct project, area, resource, or archive.

How does automated note routing determine the correct PARA destination?

Automated note routing determines the correct PARA destination using cascading logic that reads frontmatter signals including filing-hint, context, source, type, and tags. It routes items sequentially to project, area, resource, or archive, flagging items for user review if intent is ambiguous.

How do I update living docs and build connections when filing notes?

Update living docs and build connections automatically during the inbox filing workflow. As notes are moved to their PARA destinations, the process establishes links between related notes and updates reference documents to maintain a coherent knowledge base.

Can I handle thinker synthesis and note edits during automated inbox processing?

Yes, you can handle thinker synthesis and note edits during automated inbox processing through optional special handling for edits. The workflow supports per-inbox workflows including moving 0-Inbox items, archiving originals, and processing thinker synthesis.

What is the best way to maintain frontmatter normalization when archiving notes?

The best way to maintain frontmatter normalization when archiving notes is to apply automated normalization during the filing workflow. The process fixes frontmatter, renames the original item to a date-based slug, and archives it while moving it to the target area.

Why does automated note filing flag items for user review instead of moving them?

Automated note filing flags items for user review when the cascading routing logic cannot determine a clear PARA destination from the available frontmatter signals. This happens when intent is ambiguous and prevents notes from being misfiled into the wrong project, area, resource, or archive.