vault inbox triage

    1

    Triage and organize knowledge vault inboxes with Git-safe moves, YAML patching, and tag validation.

    $9

    Secure checkout via Stripe

    30-day refund guarantee

    Converts to your local currency at checkout

    0 installsSecurity scanned

    Works with the AI tools you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIGitHub CopilotGitHub CopilotGemini CLIGemini CLI+20 more

    vault inbox triage

    Example session with this skill installed

    Review my 00-inbox folder, move evergreen notes to 20-notes, and ensure all tags match my dictionary in 90-meta/tags.md.

    • Read your context and instructions
    • Compiled the vault inbox triage
    • Generated the document

    I have surveyed the 00-inbox/ directory. I found 4 files. One is a high-quality insight suitable for your evergreen notes, two are raw clippings, and one requires manual review due to missing data.

    I will now execute the following moves

    1. git mv 00-inbox/probabilistic-thinking.md 20-notes/probabilistic-thinking.md
    2. git mv 00-inbox/rss-digest-05-12.md 10-sources/rss-digest-05-12.md
    3. git mv 00-inbox/api-ref-snippet.md 10-sources/api-ref-snippet.md

    Triage Report

    FileActionNew StatusTags Applied
    probabilistic-thinking.mdPromoted to Notesstatus: seedling#epistemology
    rss-digest-05-12.mdMoved to Sourcesstatus: raw#digest
    api-ref-snippet.mdMoved to Sourcesstatus: raw#dev-docs
    broken-link.mdLeft in Inboxstatus: triageN/A

    Frontmatter Updates

    ---
id: 202310271030
title: Probabilistic Thinking in Systems
status: seedling
tags:
  - epistemology
updated: 2023-10-27
---

    Note: The file broken-link.md was left in the inbox because it appears to be a truncated web clip with no readable body text. Tag #epistemology was added to 90-meta/tags.md before processing.

    Next steps

    • Review 00-inbox/broken-link.md to see if the source URL needs re-clipping.
    • Run a vault-wide broken link check to ensure the moves didn't affect external references.
    • Commit the changes to your main branch.

    vault-inbox-triage.pdf

    PDF · document

    Generated

    Example file from a real run - the skill writes it into your workspace.

    Connects securely to your tools. The creator never sees your data.

    What you get

    Classify inbox items into atomic notes or raw sources.Preserve Git history during file migrations using git mv.Standardize YAML frontmatter and enforce tag dictionaries.Redact PII from raw clippings before they enter the vault.

    About this skill

    Knowledge vaults often become graveyard folders of clipped articles and messy drafts. This skill processes your vault inbox by classifying notes, repairing broken metadata, and moving files to their proper permanent homes.

    What it does

    • Note classification identifies if a file is an atomic insight, a raw source dump, or a low-quality bot failure.
    • Git-safe migration uses git mv to move files while preserving version history.
    • Frontmatter repair patches YAML fields like status, tags, and path-derived metadata.
    • Tag enforcement validates tags against your existing dictionary to prevent taxonomy bloat.
    • PII redaction detects and masks sensitive information found in raw digests.

    How it works

    1. Survey phase reads every file in the designated inbox to understand its content.
    2. Classification plan generates a move list based on your specific folder structure (e.g., Sources, Notes, Projects).
    3. Approval gate presents a dry-run plan for batches larger than ten files.
    4. Execution and Patching moves files via git, updates frontmatter, and verifies YAML integrity.

    Frameworks & tools

    Works with Markdown-based knowledge bases including Obsidian, Logseq, and Foam. Requires a Git-managed repository for history preservation.

    Why this beats prompting it yourself

    Generic prompts often copy and delete files, destroying Git history and breaking internal links. This skill treats your vault as a database, enforcing tag consistency and verifying YAML syntax to prevent silent corruption.

    Use cases

    • Process a week of web clippings into a categorized "Sources" folder.
    • Promote rough daily notes into atomic "Evergreen" notes with proper status tags.
    • Clean up auto-generated digests that contain broken metadata or stray characters.
    • Audit a messy inbox to redact accidental PII before committing to a public repo.

    Known limitations

    Physical deletion is disabled; files can only be archived or moved. You must have a Git repository initialized. YAML ID fields and timestamps are never modified to protect backlink integrity.

    How to install

    Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.

    ~30 seconds
    1. 1

      Download the ZIP

      Free skills download straight away. Paid skills unlock right after purchase.

    2. 2

      Unzip into your skills folder

      Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.

    3. 3

      Ask your agent to use it

      Restart the agent if it was already running. It picks the skill up automatically - no config needed.

    Skills folder by agent

    Click the path to copy it. Create the folder if it does not exist yet.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    30-day refund

    Not a fit? Get your money back

    Trust & safety

    Security scanned

    Verified clean 3 days ago

    • Passed all security checks, Safe to install

    Listed3 days ago

    What's inside

    Frequently Asked Questions