360 Secure SkillHub
360 安全技能中心

para-pkm

该 Skill 提供 PARA 个人知识管理方法论的完整指导：按可行动性（Projects/Areas/Resources/Archives）组织内容，附带决策树、角色模式和反模式说明，并通过四个 Python 脚本完成知识库脚手架搭建、结构校验、项目归档和 AI 导航文件生成。适用于新建或重整知识库、判断内容归属以及生成低 token 的导航索引。

killerapp
killerapp
热度 69.86
最近更新 2026-05-11 15:54:00
分类：知识依赖：代码执行 / 读写文件应用场景：笔记整理 / 工作流 / 模板 / 任务管理

安装技能

复制下面的话术发给你的 Agent，它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill： npx secure-skills-cli add para-pkm
Metadata
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

  • 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