skills/para-custodian/SKILL.md
Periodically maintain a shallow PARA workspace using specialised sub-agents. The skill surveys the repo, classifies files into PARA containers, distils atomic notes using the CODE method, and safely proposes or applies maintenance actions.
npx skillsauth add michael-f-bryan/skills para-custodianInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
This skill maintains a repository organised using a strict shallow PARA layout.
The repository uses numbered PARA roots:
1-projects/2-areas/3-resources/4-archives/Each root may contain one level of containers only.
Example:
1-projects/mdbook-linkcheck-triage/plan.md
3-resources/para/PARA-summary.md
Deeper nesting must not be introduced.
Both skills assume the same PARA layout (four roots, one level of containers); retrieval aids (manifests, indexes, note metadata) are described in knowledge-base-navigator references.
This skill periodically:
Before creating a new atomic note or moving content, use the knowledge-base-navigator skill to check whether equivalent knowledge already exists; avoid duplicates.
The process is designed to run autonomously with minimal intervention.
After each workflow step, persist the step output.
If the step changed tracked repository files, commit and push immediately with a step-scoped commit message.
If the step produced only temporary analysis artefacts, do not commit them unless the workflow is running on a dedicated maintenance branch that preserves intermediate state.
Safe auto-apply:
Proposal required:
10 files moved/created
Large changes must be surfaced through the configured communication channel (e.g. Discord).
Each maintenance stage is performed by a specialised sub-agent with strict inputs and outputs.
Agents:
Agents should adapt rather than fail.
When uncertain they should:
Agents must not abort the process unless the repository cannot be accessed.
The skill uses a references/ directory.
Each reference file describes:
Agents should load only the references required for their step.
This reduces context usage during long-running autonomous workflows.
Never re-read the full PARA repository by default.
Default to incremental maintenance based on:
Each sub-agent must operate within a bounded read budget.
Prefer:
The Atomic Distillation Agent may create at most 3 atomic notes per run.
It should prefer strong, reusable insights over broad coverage.
Container-wide structural review should not run on every heartbeat.
Run broad container-health checks on a slower cadence than delta-based maintenance.
documentation
Use when handling multi-step tasks, investigations, or long sessions where working notes, interim findings, and scratch planning are needed to keep context and handoffs clear.
documentation
When generating or editing markdown content, actively look for existing pages to link to and incorporate relevant wikilinks so content is interconnected. Use when writing notes, docs, or any .md content.
development
Wait for a GitHub Actions run to finish with minimal terminal output and a reliable exit code. Use when an agent must wait for CI to pass (e.g. after push, after opening a PR, or when verifying a specific run). Prefer gh run watch with --exit-status and --compact to avoid flooding context with poll output.
testing
Use when drafting, editing, or evaluating communication that should sound like Michael across public technical prose, internal notes, agent prompts, engineering feedback, and concise operational updates.