log-curation-change
Appends a one-line audit entry to the curation log whenever a brain artifact (skill, agent, prompt) is added or modified.
Install
mkdir -p .claude/skills/log-curation-change && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/15366" && unzip -o skill.zip -d .claude/skills/log-curation-change && rm skill.zipInstalls to .claude/skills/log-curation-change
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Append a one-line entry to docs/ledgers/curation-log.md whenever a brain artifact is added, modified, or removed. Use when committing changes to .github/skills, .github/instructions, .github/prompts, or .github/agents.Key capabilities
- →Append a one-line entry to `curation-log.md`
- →Classify brain artifact changes
- →Compose log entries with specific format
- →Log changes to skills, instructions, prompts, or agents
- →Maintain an audit trail for curation decisions
- →Ensure atomic logging with artifact changes
How it works
This skill ensures that every meaningful change to a brain artifact is documented by appending a classified, one-line entry to a curation log in the same commit.
Inputs & outputs
When to use log-curation-change
- →Logging brain artifact changes
- →Maintaining audit trails
- →Documenting agent updates
About this skill
Log Curation Change (Example)
This is a worked example demonstrating a skill that passes all five gates. See
../../SKILL.mdfor the authoring guide.
Every brain edit produces a one-line entry in docs/ledgers/curation-log.md. The log is the audit trail for curation decisions.
When to Use
- Adding a new skill, instruction, prompt, agent, or muscle
- Modifying an existing one (scope change, content rewrite >20 lines)
- Removing one (archival, sink, or full delete)
When not to use
- Typo fixes, link repairs, formatting-only edits — too small to log.
- Generated files (inventories, dashboards) — those have their own regen audit trail.
How to Apply
Step 1 — Classify
Pick one: [add], [modify], [archive], [delete].
Step 2 — Compose the entry
YYYY-MM-DD [classification] <artifact-path> — <one-line reason>
Step 3 — Append
Append to docs/ledgers/curation-log.md in the same commit as the artifact change.
Anti-Patterns
| Anti-pattern | Correction |
|---|---|
| Logging in a separate commit from the change | Same commit — atomic audit |
| Multi-line reasons | One line. Full reasoning goes in the commit message. |
Falsifiability — Would Revise If
- Event-based: ≥3 brain edits land without log entries in a single quarter — the rule is decorative, not enforced. Switch to a pre-commit hook.
- Date-based: 2026-08-26 — re-evaluate whether a script (
scripts/append-curation-log.cjs) should automate this.
Related
- severity-tagged-commits — the tagging discipline this skill's outcomes record
When not to use it
- →When making typo fixes, link repairs, or formatting-only edits
- →When modifying generated files (inventories, dashboards)
- →When the change is too small to log
Limitations
- →The log entry must be a one-line reason
- →The log entry must be in the same commit as the artifact change
- →The skill applies to changes in .github/skills, .github/instructions, .github/prompts, or .github/agents
How it compares
This skill enforces a specific, atomic logging discipline for brain artifact changes, creating a formal audit trail that differs from informal change tracking.
Compared to similar skills
log-curation-change side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| log-curation-change (this skill) | 0 | 2mo | No flags | Beginner |
| notion-knowledge-capture | 10 | 9mo | No flags | Intermediate |
| feishu-doc | 14 | 5mo | No flags | Intermediate |
| openspec-continue-change | 4 | 6mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by fabioc-aloha
View all by fabioc-aloha →You might also like
notion-knowledge-capture
makenotion
Transforms conversations and discussions into structured documentation pages in Notion. Captures insights, decisions, and knowledge from chat context, formats appropriately, and saves to wikis or databases with proper organization and linking for easy discovery.
feishu-doc
openclaw
Feishu document read/write operations. Activate when user mentions Feishu docs, cloud docs, or docx links.
openspec-continue-change
studyzy
通过创建下一个产出物继续处理 OpenSpec 变更。当用户想要推进其变更、创建下一个产出物或继续其工作流程时使用。
kimi-cli-help
MoonshotAI
Answer Kimi Code CLI usage, configuration, and troubleshooting questions. Use when user asks about Kimi Code CLI installation, setup, configuration, slash commands, keyboard shortcuts, MCP integration, providers, environment variables, how something works internally, or any questions about Kimi Code CLI itself.
openspec-archive-change
studyzy
归档实验性工作流中已完成的变更。当用户想要在实现完成后最终确定并归档变更时使用。
feishu-perm
m1heng
Feishu permission management for documents and files. Activate when user mentions sharing, permissions, collaborators.