para-pkm

⚠Review·Scanned 2/18/2026

This skill provides PARA-based PKM tooling and documentation and includes scripts to scaffold, validate, generate AI navigation, and archive knowledge bases. It contains runnable instructions to execute python scripts (e.g., python scripts/init_para_kb.py, python archive_project.py) that create, modify, and delete files under projects/active/ and archives/.

from clawhub.ai·v42b6f25·24.3 KB·0 installs
Scanned from 1.0.0 at 42b6f25 · Transparency log ↗
$ vett add clawhub.ai/killerapp/para-pkmReview findings below

PARA PKM

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

Core Concepts

  • 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

ScriptPurposeUsage
init_para_kb.pyScaffold new KB<name> [--path <dir>]
validate_para.pyCheck structure, detect anti-patterns[path]
archive_project.pyArchive with metadata (date, origin)<project-file> [--kb-path]
generate_nav.pyCreate AI nav (<100 lines)[--kb-path] [--output]

Templates

TemplatePurpose
assets/AGENTS.md.templateAI navigation index
assets/project.md.templateProject file structure
assets/area-overview.md.templateArea _overview.md format
assets/README.md.templateKnowledge 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 - Complete PARA method, "actionability not topic" principle
  • decision-guide.md - Detailed decision tree with edge cases
  • common-patterns.md - Proven patterns for different roles
  • ai-navigation.md - AI-friendly navigation best practices