一键在 Manus 中运行任何 Skill

auto-process-a

星标1

分支0

更新时间2026年2月22日 01:40

This skill should be used when the user asks to "process inbox", "auto process", "file this note", "triage inbox", "route this to the right place", or needs to automatically move notes from 0-Inbox to their correct PARA destination.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

JSai23

JSai23/claude-tooling

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Automated Inbox Processing

Process inbox items: read intent, classify, file, rename, connect, and update living docs. Designed for the librarian agent but usable standalone.

Input

Specific file(s): Process only the named files in 0-Inbox/
No argument: Process all files in 0-Inbox/

Process Per Item

1. Read and Understand Intent

Read the note. Check frontmatter for intent signals left by the writer or thinker:

Field	Meaning
`filing-hint`	Suggested destination (area name, project name, "resource", "unsure")
`context`	Freeform context — what prompted this, what it relates to
`source: thinker`	Came from a synthesis session — handle with care
`type`	dump, note, clip, edit
`tags`	Knowledge role: seed, thread, tool, question, insight

If no intent signals, classify from content.

2. Determine Destination

Filing cascade (first match wins):

Project? → Does this help an active project? Check project briefs for goal alignment.
Area? → Does this relate to an ongoing area? Match against area scopes.
Resource? → Is this reference material? Route to correct sub-folder (clips/short-form/long-form/books/videos).
None? → Archive or flag for user.

When filing-hint exists, treat as strong signal but verify.

3. Confirm with Semantic Search

qmd vsearch "key content from the note" --files

Auto-file when:

Semantic search confirms (3+ top results in same location)
Content clearly matches one area/project's scope
filing-hint aligns with search results

Ask the user when:

Top matches span multiple areas
Content is vague or multi-topic
filing-hint: unsure or missing with no clear match

4. Archive Original

Preserve the raw capture before modifying. Rename to YYYY-MM-DD_descriptive-slug.md but keep frontmatter and content as-is — naming is the one thing we always enforce, even on raw archives:

mkdir -p "04-archive/inbox"
cp "0-Inbox/original-name.md" "04-archive/inbox/YYYY-MM-DD_slug.md"

5. Fix Frontmatter

Set type: note if missing (keep original type if appropriate)
Set created: YYYY-MM-DD using today's date if missing
Validate tags against the 5-tag vocabulary (#seed, #thread, #tool, #question, #insight)
Set appropriate status (draft, refining, or omit for stable)
Remove intent fields: Strip filing-hint, context, source — they served their purpose

6. Rename and Move

Rename to YYYY-MM-DD_descriptive-slug.md, then move to destination:

mv "0-Inbox/original-name.md" "2-Areas/area-name/YYYY-MM-DD_slug.md"

7. Update Living Docs

Read the parent MOC or project brief. Add the note with annotation:

- [[YYYY-MM-DD_slug]] — brief description of what the note covers

For thinker synthesis (source: thinker):

Check if the synthesis updates the MOC's thesis paragraph
Check if it resolves any Open Questions
Update source notes' ## Related sections

8. Build Connections

Find related notes via semantic search and structural analysis. Add ## Related section if strong connections exist. Only add connections that are clear and useful.

Special: Edit Notes

For notes with type: edit:

Read the targets array from frontmatter
Read each target file
Apply the described edits
Archive the edit note

Processing Report

After processing, show summary:

## Inbox Processing Report

### Filed
- "Raw thoughts on agents" → 2-Areas/ai-dev-ecosystem/2025-02-07_agent-thoughts.md
- "Market data notes" → 1-Projects/polymarket-framework/2025-02-07_market-data.md

### Living Docs Updated
- 00_ai-dev-ecosystem.md — added link to agent-thoughts
- 00_polymarket-framework.md — added link to market-data

### Connections Found
- agent-thoughts ↔ agentic-primitives (shared concepts)

### Needs Attention
- "Ambiguous note" — couldn't determine destination, left in inbox

After Batch Processing

Reindex semantic search:

qmd update

同仓库更多 Skills

同仓库

loop-loop-author-a

JSai23/claude-tooling

Write high-quality session prompts (SESSION_WORKER.md and SESSION_REVIEWER.md) for an agent loop. Reads repo context and follows the loop-author guide to produce targeted, effective prompts. Use when setting up a new loop or rewriting session prompts for an existing one.

2026-03-151

loop-loop-launch-a

JSai23/claude-tooling

Pre-flight checks and launch for agent loops. Validates branch state, session prompts, creates loop directory structure, and launches run.sh in a tmux session. Use when the user wants to start a new agent loop in the current repo.

2026-03-151

loop-loop-observe-a

JSai23/claude-tooling

Cross-repo visibility for agent loops. Lists running, completed, and crashed loops. Reads the registry and per-repo tracking logs. Shows tmux attach commands. Use when checking what loops are active, what ran recently, or loop details.

2026-03-151

util-improve

JSai23/claude-tooling

Capture feedback about wf, util, or vault plugins and file it as a GitHub issue for improvement. Use after any session where the tooling fell short — wrong agent behavior, missing skill coverage, misleading prompts, workflow friction, or convention gaps. Only for generic plugin improvements that would help ANY project, not repo-specific config. Files to JSai23/claude-tooling with the plugin-feedback label.

2026-03-151

loop-author-a

JSai23/claude-tooling

2026-03-151

loop-launch-a

JSai23/claude-tooling

2026-03-151

name	auto-process-a
type	action
description	This skill should be used when the user asks to "process inbox", "auto process", "file this note", "triage inbox", "route this to the right place", or needs to automatically move notes from 0-Inbox to their correct PARA destination.
argument-hint	[filename(s)] or blank for all inbox

Action skill — Inbox processing workflow: read intent, determine destination, confirm, file, update living docs.

Automated Inbox Processing

Process inbox items: read intent, classify, file, rename, connect, and update living docs. Designed for the librarian agent but usable standalone.

Input

Specific file(s): Process only the named files in 0-Inbox/
No argument: Process all files in 0-Inbox/

Process Per Item

1. Read and Understand Intent

Read the note. Check frontmatter for intent signals left by the writer or thinker:

Field	Meaning
`filing-hint`	Suggested destination (area name, project name, "resource", "unsure")
`context`	Freeform context — what prompted this, what it relates to
`source: thinker`	Came from a synthesis session — handle with care
`type`	dump, note, clip, edit
`tags`	Knowledge role: seed, thread, tool, question, insight

If no intent signals, classify from content.

2. Determine Destination

Filing cascade (first match wins):

Project? → Does this help an active project? Check project briefs for goal alignment.
Area? → Does this relate to an ongoing area? Match against area scopes.
Resource? → Is this reference material? Route to correct sub-folder (clips/short-form/long-form/books/videos).
None? → Archive or flag for user.

When filing-hint exists, treat as strong signal but verify.

3. Confirm with Semantic Search

qmd vsearch "key content from the note" --files

Auto-file when:

Semantic search confirms (3+ top results in same location)
Content clearly matches one area/project's scope
filing-hint aligns with search results

Ask the user when:

Top matches span multiple areas
Content is vague or multi-topic
filing-hint: unsure or missing with no clear match

4. Archive Original

Preserve the raw capture before modifying. Rename to YYYY-MM-DD_descriptive-slug.md but keep frontmatter and content as-is — naming is the one thing we always enforce, even on raw archives:

mkdir -p "04-archive/inbox"
cp "0-Inbox/original-name.md" "04-archive/inbox/YYYY-MM-DD_slug.md"

5. Fix Frontmatter

Set type: note if missing (keep original type if appropriate)
Set created: YYYY-MM-DD using today's date if missing
Validate tags against the 5-tag vocabulary (#seed, #thread, #tool, #question, #insight)
Set appropriate status (draft, refining, or omit for stable)
Remove intent fields: Strip filing-hint, context, source — they served their purpose

6. Rename and Move

Rename to YYYY-MM-DD_descriptive-slug.md, then move to destination:

mv "0-Inbox/original-name.md" "2-Areas/area-name/YYYY-MM-DD_slug.md"

7. Update Living Docs

Read the parent MOC or project brief. Add the note with annotation:

- [[YYYY-MM-DD_slug]] — brief description of what the note covers

For thinker synthesis (source: thinker):

Check if the synthesis updates the MOC's thesis paragraph
Check if it resolves any Open Questions
Update source notes' ## Related sections

8. Build Connections

Find related notes via semantic search and structural analysis. Add ## Related section if strong connections exist. Only add connections that are clear and useful.

Special: Edit Notes

For notes with type: edit:

Read the targets array from frontmatter
Read each target file
Apply the described edits
Archive the edit note

Processing Report

After processing, show summary:

## Inbox Processing Report

### Filed
- "Raw thoughts on agents" → 2-Areas/ai-dev-ecosystem/2025-02-07_agent-thoughts.md
- "Market data notes" → 1-Projects/polymarket-framework/2025-02-07_market-data.md

### Living Docs Updated
- 00_ai-dev-ecosystem.md — added link to agent-thoughts
- 00_polymarket-framework.md — added link to market-data

### Connections Found
- agent-thoughts ↔ agentic-primitives (shared concepts)

### Needs Attention
- "Ambiguous note" — couldn't determine destination, left in inbox

After Batch Processing

Reindex semantic search:

qmd update