Agent skill
evergreen
Principles for creating evergreen notes - atomic, lasting insights that compound over time. Use when discussing note quality, what makes a good evergreen note, or the "only what was explored" principle. Tool-agnostic concepts that apply regardless of note-taking app.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/devops/evergreen-odysseus0-nix-config-680bdb6e
SKILL.md
Evergreen Notes
Atomic insights that remain true and useful over time.
Atomicity
One claim per note. The title states the claim. If you can't write a complete statement title, decompose.
- Good: "Spaced repetition works because forgetting is desirable difficulty"
- Bad: "Spaced repetition"
Quality Bar
Include: Genuinely grasped, non-obvious, atomic, lasting value
Reject: Surface observations, vague generalizations, obvious statements, current-event descriptions
Core Principles
Only what was explored - The note reads "here's what you discovered, explained expertly."
- If something would illuminate understanding → stop and discuss first
- Deepen, don't expand
Self-contained - Makes sense when you've forgotten the original context.
Notes evolve - Not final artifacts. Revise as understanding deepens.
Concept-oriented - "How spaced repetition works" not "Notes from Make It Stick"
Links over folders - Connections create value; associative beats hierarchical.
Multiple Notes
Write in dependency order. If re-explaining → link instead. If concept repeats → extract.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?