Name: para-pkm
Author: Vaskin Kissoyan

According to AlphaMoat, as of 2026-09, para-pkm has 2,435 downloads and 1 stars — ranked #4,156 of 5,078 AI skills overall, and #358 of 442 in Knowledge.

Installs

127

Downloads

2.4K

Stars

Overall Rank

#4,156

Top 82% overall · Top 81% in Knowledge

Platform	Installs	Downloads	Stars	Comments
ClawHub ↗	74	2.3K	1	-
SkillHub ↗	127	2.4K	1	—

Platforms count differently and update at different times.

What this skill does

It distinguishes time-bound projects, ongoing responsibilities, reference resources, and inactive archives, and describes archiving completed work, navigation files, and recurring reviews. Use it to create or reorganize a knowledge base; inspect the current structure and preserve a recoverable copy before moving content.

Profile published 2026-10-29

What you can do with it

Create a PARA structure for a personal knowledge base

When to use it

Organize existing notes into projects, areas, resources, or archives

Example prompts

Generated from the skill’s documentation as examples; not results of actual runs.

Summarize PARA’s classification rules and how to protect existing content before reorganization.

Monthly Trend

Downloads2.4K

Stars1

The counting method changed in 2026-09: skills with the same name are now counted separately by author, and the full catalog is covered. Dashed lines show months before the change; they are not compared with later months, and no growth is computed across the change.

Month	Downloads	MoM	Stars
2026-09	2.4K	—	1
2026-08	2.2K	+3.3%	1
2026-07	2.1K	—	1
2026-05	1.9K	—	1
2026-03	1.6K	—	1

SKILL.md (original)

The author’s original file, shown as plain text without edits or review by AlphaMoat. Links are not clickable; check commands before running them. Fetched 2026-10-23.

4.1 KB · ClawHub v1.0.0

---
name: para-pkm
description: Manage PARA-based personal knowledge management (PKM) systems using Projects, Areas, Resources, and Archives organization method. Use when users need to (1) Create a new PARA knowledge base, (2) Organize or reorganize existing knowledge bases into PARA structure, (3) Decide where content belongs in PARA (Projects vs Areas vs Resources vs Archives), (4) Create AI-friendly navigation files for knowledge bases, (5) Archive completed projects, (6) Validate PARA structure, or (7) Learn PARA organizational patterns for specific use cases (developers, consultants, researchers, etc.)
---

# PARA PKM

Organize by actionability, not topic. Projects/Areas/Resources/Archives for optimal AI navigation. Monthly review cadence.

## Core Concepts

Show all (91 lines)


- **Projects** = Time-bound goals with deadlines (completes → Archives); includes `projects/stories/` for job applications
- **Areas** = Ongoing responsibilities (use `_overview.md` per area for context)
- **Resources** = Reference material; when unsure, put here temporarily
- **Archives** = Inactive items from any category

## Decision Tree

```
Has deadline/end state? → Projects
Ongoing responsibility? → Areas
Reference material? → Resources (default for uncertain items)
Completed/inactive? → Archives
```

## Quick Start

1. `python scripts/init_para_kb.py <name>` - Creates PARA + `projects/stories/` + navigation
2. Identify projects (deadlines) → areas (ongoing) → resources (reference)
3. `python scripts/generate_nav.py` - Generate AI navigation

## Scripts

| Script | Purpose | Usage |
|--------|---------|-------|
| `init_para_kb.py` | Scaffold new KB | `<name> [--path <dir>]` |
| `validate_para.py` | Check structure, detect anti-patterns | `[path]` |
| `archive_project.py` | Archive with metadata (date, origin) | `<project-file> [--kb-path]` |
| `generate_nav.py` | Create AI nav (<100 lines) | `[--kb-path] [--output]` |

## Templates

| Template | Purpose |
|----------|---------|
| `assets/AGENTS.md.template` | AI navigation index |
| `assets/project.md.template` | Project file structure |
| `assets/area-overview.md.template` | Area `_overview.md` format |
| `assets/README.md.template` | Knowledge base README |

## Patterns by Role

- **Developers**: `projects/active/` features/bugs, `areas/professional-development/`, `resources/coding-standards/`
- **Consultants**: `projects/active/` deliverables + `projects/stories/`, `areas/consulting/clients/`, `resources/templates/`
- **Researchers**: `projects/active/` papers/grants, `areas/research-program/`, `resources/literature-review/`
- **Product Builders**: `projects/active/` launches, `areas/product-development/{active,research,graduated,legacy}/`

## Complex Scenarios

**Client = project + relationship**: `projects/active/client-x.md` (deliverables) + `areas/consulting/clients/client-x.md` (relationship, billing)

**Research lifecycle**: `areas/product-development/{research → graduated → active → legacy}` with cross-references

## Anti-Patterns

- inbox/ folder (capture directly into PARA; use Resources when uncertain)
- Deep nesting (max 2-3 levels; flat > nested)
- Topic-based organization ("work/personal" → use actionability)
- Todo folders (tasks belong with their projects/areas)
- Perfectionism (move freely as understanding evolves; monthly review catches misplacements)

## Content Lifecycle

```
Resources → Projects → Archives (research → active work → completed)
Areas → Archives (no longer responsible)
Projects ⟺ Areas (goal becomes ongoing or vice versa)
```

## AI Navigation & Success Tips

- Keep nav under 100 lines; point to paths not files; minimize tokens
- Start simple ("What am I working on now?"); one home per item (use links)
- Monthly review: archive completed, reassess areas; let patterns emerge

## References

- [para-principles.md](references/para-principles.md) - Complete PARA method, "actionability not topic" principle
- [decision-guide.md](references/decision-guide.md) - Detailed decision tree with edge cases
- [common-patterns.md](references/common-patterns.md) - Proven patterns for different roles
- [ai-navigation.md](references/ai-navigation.md) - AI-friendly navigation best practices