New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Para Skill

by aiskillstore in aiskillstore/marketplace

PARA method knowledge management for Obsidian vaults. An agent skill from aiskillstore/marketplace.

MITAuto-check passedKnowledge Management

Install Para Skill

skills CLI
$ npx skills add aiskillstore/marketplace --skill para-skill -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install aiskillstore/marketplace para-skill --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/aiskillstore/marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/scifishelf/para-skill .claude/skills/para-skill && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
para-skill
GitHub stars
430
Token cost
~2k tokens
SKILL.md length
854 words
Files
9 (incl. references)
Skills in repo
1,044
Repo updated
First seen
Licence
MIT

At a glance

PARA method knowledge management for Obsidian vaults. An agent skill from aiskillstore/marketplace.

  • Works in 8 steps: Read the note content, title, existing… → Collect signals — look for project… → Check conventions — respect existing… → …
  • The user wants to organize notes using PARA (Projects
  • SKILL.md covers What this skill does, Vault Configuration, Core Workflow and Available Actions, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Para Skill is an agent skill from aiskillstore/marketplace. PARA method knowledge management for Obsidian vaults. Use this skill whenever the user wants to organize notes using PARA (Projects, Areas, Resources, Archive), classify a note into a PARA category, route a note to the right vault folder, normalize frontmatter fields, run a PARA hygiene review, suggest archiving, audit vault structure, or process new knowledge inputs into an existing PARA-based vault. Also trigger when the user mentions inbox processing, vault cleanup, note classification, PARA review, or asks…

Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 9 other files, including reference files (for example `CHANGELOG.md`, `README.md` and `references/classification-rules.md`).

It sits in Knowledge Management, covering Email management. It works with Obsidian. The repository describes itself as: Security-audited skills for Claude, Codex & Claude Code. One-click install, quality verified. The licence is MIT.

When your agent uses it

  • The user wants to organize notes using PARA (Projects
  • Classify a note into a PARA category
  • Route a note to the right vault folder
  • Normalize frontmatter fields

Example prompts

  • “where does this note belong?”
  • “/para-skill”

Workflow steps

8 steps, taken from the first numbered list in SKILL.md.

  1. Read the note content, title, existing frontmatter, tags, and current file path
  2. Collect signals — look for project indicators (deadlines, tasks, goals), area indicators (ongoing, recurring), resource indicators…
  3. Check conventions — respect existing para_type frontmatter; existing folder placement is a strong signal
  4. Classify with a confidence level: high, medium, or low
  5. Plan frontmatter additions — only add fields from the schema, never overwrite non-PARA fields
  6. Propose routing — suggest the target path
  7. Assess risk — only act directly when confidence is high AND the user has given explicit permission or the mode is balanced/aggressive
  8. Log changes when writing anything

What it can do on your machine

Read from SKILL.md and the folder at commit 755bc35. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are yaml and markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Para Skill loads about 2k tokens when it runs, and up to ~5.8k if it reads all its reference files. Until then it costs about 163 tokens; SKILL.md has 854 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~163
When it runs · the whole SKILL.md, loaded when a task matches
~2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~5.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from aiskillstore/marketplace at commit 755bc35, republished under its MIT licence (© aiskillstore). 854 words, ~2,031 tokens.

Download SKILL.mdSave it as .claude/skills/para-skill/SKILL.md (or your agent's skills folder). This skill also uses 8 other files; get the full folder from GitHub.
name
para-skill
description
PARA method knowledge management for Obsidian vaults. Use this skill whenever the user wants to organize notes using PARA (Projects, Areas, Resources, Archive), classify a note into a PARA category, route a note to the right vault folder, normalize frontmatter fields, run a PARA hygiene review, suggest archiving, audit vault structure, or process new knowledge inputs into an existing PARA-based vault. Also trigger when the user mentions inbox processing, vault cleanup, note classification, PARA review, or asks "where does this note belong?". Works with existing Obsidian skills (obsidian-markdown, obsidian-cli) — never replaces them.

PARA Obsidian Skill

What this skill does

This skill provides PARA-method decision logic for Obsidian vaults. It decides where notes belong, when to archive, and how to keep the vault healthy — while leaving file creation, markdown formatting, and Obsidian syntax to the installed base skills.

PARA is an organizational framework by Tiago Forte that structures information by action relevance, not topic:

  • Projects — concrete initiatives with a goal and an endpoint
  • Areas — ongoing responsibilities with no fixed end date
  • Resources — reference knowledge for potential future use
  • Archive — completed, paused, or inactive content

Read references/classification-rules.md for detailed classification heuristics.

Vault Configuration

Default paths for this vault (override in conversation if different):

yaml
paths:
  inbox: "0_Inbox"          # created on demand if missing
  projects: "1_Projects"
  areas: "2_Areas"
  resources: "3_Resources"
  archive: "4_Archives"

Default mode: cautious — suggest first, act only when confident or explicitly asked.

Core Workflow

For every PARA-related task, follow this sequence:

  1. Read the note content, title, existing frontmatter, tags, and current file path
  2. Collect signals — look for project indicators (deadlines, tasks, goals), area indicators (ongoing, recurring), resource indicators (reference, no action pressure), archive indicators (done, cancelled, historical)
  3. Check conventions — respect existing para_type frontmatter; existing folder placement is a strong signal
  4. Classify with a confidence level: high, medium, or low
  5. Plan frontmatter additions — only add fields from the schema, never overwrite non-PARA fields
  6. Propose routing — suggest the target path
  7. Assess risk — only act directly when confidence is high AND the user has given explicit permission or the mode is balanced/aggressive
  8. Log changes when writing anything

When in doubt: set needs_review: true, place in Inbox, and explain why.

See references/classification-rules.md for the full decision tree.

Available Actions

capture — Process new content

Accept raw text, meeting notes, ideas, or document descriptions. Classify them, propose or create a note in the right location, and set frontmatter.

Example trigger: "Capture this: Vorbereitung Workshop Führungsteam April" Output: PARA classification + proposed path + frontmatter draft

classify — Classify an existing note

Read a note and determine its PARA type. Return classification, confidence level, and reasoning.

Example trigger: "Welcher PARA-Typ ist diese Notiz?" or "Klassifiziere 2_Areas/Weiterbildung/..." Output: para_type, confidence, explanation, suggested changes

route — Determine or apply target location

Calculate the correct target folder for a note. In cautious mode: suggest only. With explicit permission: move the file.

Example trigger: "Wo gehört diese Notiz hin?" or "Route diese Notiz korrekt ein" Output: Current path → suggested path, reasoning, conflict check

normalize — Fix frontmatter

Add missing PARA frontmatter fields to a note without touching non-PARA fields. Never remove existing fields.

Example trigger: "Normalisiere das Frontmatter dieser Notiz" or "Füge PARA-Metadaten hinzu" Output: Updated frontmatter block (show diff before applying)

review — PARA hygiene report

Scan a folder or the whole vault for hygiene issues. See references/review-playbook.md for what to check.

Example trigger: "Mach einen PARA-Review" or "Zeig mir, was im Vault aufgeräumt werden sollte" Output: Structured report (projects without next steps, stale areas, inbox backlog, archiving candidates)

archive — Archive a note defensively

Move a note to the Archive folder with archived: true, archive_date, and updated status. Never delete. Preserve all wikilinks.

Example trigger: "Archiviere dieses Projekt" or "Das Projekt ist abgeschlossen" Output: Confirmation of move + frontmatter changes (dry-run by default)

Show full SKILL.md (341 more words)Show less
audit — Full vault consistency audit

Scan all notes for PARA inconsistencies: missing frontmatter, wrong folder placement, orphaned notes, stale reviews. Produces a prioritized action list.

Example trigger: "Mach einen vollständigen Vault-Audit" or "Was stimmt in meinem Vault nicht?" Output: Audit report with actionable items

suggest — Recommendation without changes

Give a PARA recommendation with full reasoning, but make no changes to any file.

Example trigger: "Was würdest Du mit dieser Notiz machen?" or "Vorschlag für diese Datei" Output: Recommendation + reasoning (read-only)

Safety Rules

These rules are non-negotiable regardless of mode:

  1. No mass moves without explicit user authorization — always ask first
  2. No deletion — archive means move, never delete
  3. No overwriting non-PARA frontmatter fields — only add/update defined PARA fields
  4. Low confidence → needs_review — never force a classification when unsure
  5. Dry-run by default — show what would happen before doing it
  6. Preserve wikilinks — never rename files in ways that break [[links]]
  7. Log every structural change — use the change log format below
  8. No reclassification from a single weak signal — require 2+ supporting indicators
Change Log Format

When making structural changes, append to a PARA-Changelog.md in the vault root:

markdown
## 2026-03-14
- Classified `Meeting Notes Team Alpha` → project (confidence: medium)
- Suggested move to `1_Projects/team-alpha/` (not yet applied, needs_review: true)
- Normalized frontmatter in `2_Areas/Weiterbildung/KI-Kurs.md`

Frontmatter Schema

Read references/frontmatter-schema.md for the full field definitions.

Quick reference — only write these fields:

yaml
para_type: project        # project | area | resource | archive
status: active            # active | on-hold | done | archived | reference | needs_review
review_date: 2026-03-21
confidence: high          # high | medium | low
needs_review: false
archived: false
archive_date:             # only when archiving
source: manual            # manual | meeting | import | daily-note | web

Never touch: titles, body content, existing tags not prefixed with para/, wikilinks, non-PARA frontmatter fields.

Cooperation with Other Skills

This skill handles: classification logic, routing decisions, PARA frontmatter, review reports

Leave to obsidian-markdown / obsidian-cli: file creation, markdown syntax, wikilink formatting, template application, dataview queries

When creating a new note as part of capture or route, delegate file creation to the obsidian-markdown or obsidian-cli skill if available. Only use direct file writes as fallback.

Read references/compatibility-notes.md for conflict avoidance rules.

Response Format

Always communicate:

  1. What you classified/found (with para_type and confidence)
  2. Why — at least 2 supporting signals
  3. What you propose to change (as a clear list)
  4. What you're uncertain about (if anything)
  5. What you'll do next — or ask for permission before acting

For reviews and audits, use the structured report format in references/review-playbook.md.

© aiskillstore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 8 other files (references) in skills/scifishelf/para-skill of aiskillstore/marketplace.

  • SKILL.md
  • CHANGELOG.md
  • LICENSE
  • README.md
  • references/classification-rules.md
  • references/compatibility-notes.md
  • references/frontmatter-schema.md
  • references/review-playbook.md
  • skill-report.json

Open the folder on GitHubat commit 755bc35

Compare with similar skills

Para Skill next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Para Skill compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Para Skill this skillaiskillstore/marketplace430—~2kAutomated safety check: PassMIT
Cascading Goal Trackerballred/obsidian-claude-pkm1.9k—~1.5kAutomated safety check: PassMIT
Dbrain Processorsmixs/agent-second-brain392—~3.3kAutomated safety check: PassMIT
Ingestsuperhero-tech/super-brain166—~1.3kAutomated safety check: PassMIT
Setupjdpolasky/ai-chief-of-staff104—~3.5kAutomated safety check: PassMIT
Weekly Review PlanningNousResearch/hermes-agent252k—~994Automated safety check: PassMIT

Similar skills

  • Cascading Goal Tracker

    ballred/obsidian-claude-pkm

    Tracks three-year, yearly, monthly, and weekly goals in linked Markdown files, calculating completion percentages and flagging stalled goals.

    1.9k GitHub stars~1.5k tokensUpdated 7 mo ago
    Knowledge ManagementAuto-check passed

  • Dbrain Processor

    smixs/agent-second-brain

    Personal assistant for processing daily voice/text entries from Telegram.

    392 GitHub stars~3.3k tokensUpdated 2 mo ago
    Knowledge ManagementAuto-check passed

  • Ingest

    superhero-tech/super-brain

    Compiles a source from 2-Inbox/ into the wiki, across every page it touches, then archives it.

    166 GitHub stars~1.3k tokensUpdated 1 mo ago
    Knowledge ManagementAuto-check passed

  • Setup

    jdpolasky/ai-chief-of-staff

    First-time setup for the Chief of Staff system. An agent skill from jdpolasky/ai-chief-of-staff.

    104 GitHub stars~3.5k tokensUpdated 6 days ago
    Knowledge ManagementAuto-check passed

  • Weekly Review Planning

    NousResearch/hermes-agent

    Weekly reset: commitments, stalled work, next-week plan. An agent skill from NousResearch/hermes-agent.

    252k GitHub stars~994 tokensUpdated today
    Knowledge ManagementAuto-check passed

  • Preserve

    iurykrieger/claude-bedrock

    Single write point for the vault. An agent skill from iurykrieger/claude-bedrock.

    105 GitHub stars~14k tokensUpdated 5 mo ago
    Knowledge ManagementAuto-check: notes

More from aiskillstore/marketplace

All 1,044 skills in this repo

  • Code Stats

    aiskillstore/marketplace

    Analyze codebase with tokei (fast line counts by language) and difft (semantic AST-aware diffs).

    430 GitHub starsUsed in 1 repo~697 tokens
    Auto-check: notes

  • Data Processing

    aiskillstore/marketplace

    Process JSON with jq and YAML/TOML with yq. An agent skill from aiskillstore/marketplace.

    430 GitHub starsUsed in 1 repo~720 tokens
    Auto-check: notes

  • Doc Scanner

    aiskillstore/marketplace

    Scans for project documentation files (AGENTS.md, CLAUDE.md, GEMINI.md, COPILOT.md, CURSOR.md, WARP.md, and 15+ other formats) and synthesizes guidance.

    430 GitHub starsUsed in 1 repo~644 tokens
    Auto-check: notes

  • File Search

    aiskillstore/marketplace

    Modern file and content search using fd, ripgrep (rg), and fzf.

    430 GitHub starsUsed in 1 repo~598 tokens
    Auto-check: notes

  • Find Replace

    aiskillstore/marketplace

    Modern find-and-replace using sd (simpler than sed) and batch replacement patterns.

    430 GitHub starsUsed in 1 repo~527 tokens
    Auto-check: notes

  • Project Planner

    aiskillstore/marketplace

    Detects stale project plans and suggests session commands. An agent skill from aiskillstore/marketplace.

    430 GitHub starsUsed in 1 repo~504 tokens
    Auto-check passed

Works with

Categories

Questions about Para Skill

What does Para Skill do?

PARA method knowledge management for Obsidian vaults. An agent skill from aiskillstore/marketplace. Para Skill is an agent skill from aiskillstore/marketplace. PARA method knowledge management for Obsidian vaults.

When should I use Para Skill?

Para Skill fits situations like: the user wants to organize notes using PARA (Projects; classify a note into a PARA category; route a note to the right vault folder; normalize frontmatter fields.

How do I install Para Skill in Claude Code?

Run `npx skills add aiskillstore/marketplace --skill para-skill -a claude-code`. Or copy the skill folder (skills/scifishelf/para-skill in aiskillstore/marketplace) into .claude/skills/para-skill in your project. Claude Code loads it when a task matches its description.

How do I install Para Skill in Codex?

Run `npx skills add aiskillstore/marketplace --skill para-skill -a codex`. Or copy the skill folder (skills/scifishelf/para-skill in aiskillstore/marketplace) into .agents/skills/para-skill in your project. Codex loads it when a task matches its description.

Can I use Para Skill in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add aiskillstore/marketplace --skill para-skill -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/para-skill, .gemini/skills/para-skill, .github/skills/para-skill and .opencode/skills/para-skill in your project.

What does Para Skill need to run?

SKILL.md names no scripts, command-line tools or credentials: Para Skill is instructions for the agent only.

Does Para Skill access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Para Skill safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Para Skill use?

Para Skill is published under the MIT licence (from the LICENSE file in the skill folder). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Para Skill use?

About 2k tokens (SKILL.md is roughly 8.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.8k tokens, read only when the agent opens those files.

What are the alternatives to Para Skill?

Skills that share tags, products or a category with Para Skill: Cascading Goal Tracker (ballred/obsidian-claude-pkm, 1.9k stars), Dbrain Processor (smixs/agent-second-brain, 392 stars), Ingest (superhero-tech/super-brain, 166 stars) and Setup (jdpolasky/ai-chief-of-staff, 104 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Para Skill?

aiskillstore (a GitHub organization) maintains it in aiskillstore/marketplace, which has 430 GitHub stars. The repository holds 1,044 skills in this directory. The repository was last updated on October 9, 2026.

Source: aiskillstore/marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.