Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
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.)
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.)
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Organize by actionability, not topic. Projects/Areas/Resources/Archives for optimal AI navigation. Monthly review cadence.
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
Has deadline/end state? โ Projects Ongoing responsibility? โ Areas Reference material? โ Resources (default for uncertain items) Completed/inactive? โ Archives
python scripts/init_para_kb.py <name> - Creates PARA + projects/stories/ + navigation Identify projects (deadlines) โ areas (ongoing) โ resources (reference) python scripts/generate_nav.py - Generate AI navigation
ScriptPurposeUsageinit_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]
TemplatePurposeassets/AGENTS.md.templateAI navigation indexassets/project.md.templateProject file structureassets/area-overview.md.templateArea _overview.md formatassets/README.md.templateKnowledge base README
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}/
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
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)
Resources โ Projects โ Archives (research โ active work โ completed) Areas โ Archives (no longer responsible) Projects โบ Areas (goal becomes ongoing or vice versa)
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
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
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.