para-classifier

Classifies inbox items into PARA categories using decision trees and emoji mappings.

6|1|Updated Nov 26, 2025
One-click install
npx skills add https://github.com/nathanvale/side-quest-marketplace-old --skill para-classifier-nathanvale
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: para-classifier
Source: https://github.com/nathanvale/side-quest-marketplace-old/tree/main/plugins/para-obsidian/skills/para-classifier
Command: npx skills add https://github.com/nathanvale/side-quest-marketplace-old --skill para-classifier-nathanvale

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Sorting an overflowing inbox into a consistent note-taking system is error-prone and inconsistent without clear rules. This Skill provides reference guidance so triage and distill workflows classify every inbox item the same way using the PARA methodology. ## Core Features & Use Cases - Classification Decision Tree: Routes inbox items to records, resources, areas, or archives based on dates, transactions, and distillable content. - Emoji Mapping: Converts source_format values like article, video, and podcast into consistent emoji prefixes for visual scanning. - Type Disambiguation: Clarifies the difference between resources, meetings, bookings, invoices, and other note types with frontmatter examples. - Use Case: When a triage skill encounters a PDF in the inbox, it loads these references to decide whether the file is an invoice, a resource document, or an archive candidate, and assigns the correct emoji and template. ## Quick Start Load the para-classifier references when triaging inbox notes so each item is routed to the correct PARA category with the right emoji and template.

Frequently Asked Questions about para-classifier

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

FAQPage Schema
How do I classify inbox notes using the PARA method?

PARA classification starts by checking if an item has a date or transaction, which routes it to a record type like meeting, booking, or invoice. Items with distillable knowledge become resources, while irrelevant items are archived or deleted.

What is the difference between a resource and a record in PARA?

Resources are knowledge to learn from, such as articles, videos, and books that go through distillation. Records are reference items tied to events or transactions, like meeting notes, invoices, and bookings, that you retrieve when needed.

How do I choose the right emoji for a note's source format?

Match the primary content format to the emoji mapping table: article uses 📰, video uses 🎬, podcast uses 🎙️, thread uses 🧵, and book uses 📖. When unsure, use 📄 document as a safe fallback.

Should a conference talk be classified as a meeting or a resource?

A talk you attended live with interaction is a meeting record, while a recording you watched alone is a resource with source_format video. The deciding factor is whether the purpose is recording an event or learning from content.

What should I do with bookmarks that have no captured content?

Bookmarks containing only a URL with no substantial content should be archived or deleted since they offer no distillable value. Only bookmarks with captured article text, transcripts, or documents become resources.