vault-canonical-promotion
Routes polished notes into official canonical documentation through a structured promotion process.
Install
mkdir -p .claude/skills/vault-canonical-promotion && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/14335" && unzip -o skill.zip -d .claude/skills/vault-canonical-promotion && rm skill.zipInstalls to .claude/skills/vault-canonical-promotion
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.
Use when curated vault material may need to become stable canonical knowledge, or when an agent wants to update an existing canonical note without direct authority. Applies when promotion criteria, proposal files, registry updates, and merge safety matter.Key capabilities
- →Create promotion candidates for canonical knowledge
- →Update items in the `promotion-queue.json`
- →Prepare proposal notes for canonical updates
- →Recommend target paths for canonical knowledge
- →Confirm source notes are in `intake` or `curation`
How it works
This skill routes curated vault material through a promotion process by confirming the source note's location, checking for existing canonical knowledge, and then adding or updating `promotion-queue.json` or preparing a proposal.
Inputs & outputs
When to use vault-canonical-promotion
- →Promoting research to canonical status
- →Managing documentation quality
- →Queueing notes for documentation review
About this skill
Vault Canonical Promotion
Overview
This skill exists to stop agents from publishing working notes as official knowledge too early. It routes durable material through a promotion process instead of silent direct edits.
If your agent supports MCP, 优先 use the governance MCP server for proposal, queue, review, and apply operations. Use this skill as the compatibility layer when MCP is unavailable.
Promotion Conditions
The candidate should have:
- a resolved
topic_id - valid source lineage
- curation-level stability
- long-term reuse value
- a clear home in canonical knowledge
Read references/promotion-criteria.md before promoting.
Standard Flow
- Confirm the source note lives in
intakeorcuration - Check whether canonical already exists for the topic
- If canonical exists and you are not Hermes/human, prepare a proposal instead of overwriting
- Add or update
promotion-queue.json - Add ledger entry
- Leave final merge to Hermes or a human
Allowed Actions
- create promotion candidate
- update queue item
- prepare proposal note
- recommend canonical target path
Disallowed Actions
- silent overwrite of canonical notes
- reclassifying raw notes as canonical without curation
- skipping queue update
Common Mistakes
- treating polished wording as proof of canonical readiness
- publishing without checking for existing canonical home
- forgetting to record why this note deserves promotion
When not to use it
- →When directly overwriting canonical notes is intended
- →When reclassifying raw notes as canonical without curation
- →When skipping queue updates
Limitations
- →Does not allow silent overwrite of canonical notes
- →Does not allow reclassifying raw notes as canonical without curation
- →Does not allow skipping queue updates
How it compares
This skill enforces a structured promotion process for knowledge, preventing direct, unauthorized edits to canonical notes.
Compared to similar skills
vault-canonical-promotion side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| vault-canonical-promotion (this skill) | 0 | 3mo | No flags | Intermediate |
| notion-knowledge-capture | 10 | 9mo | No flags | Intermediate |
| history-insight | 0 | 7mo | Review | Beginner |
| log | 0 | 6mo | No flags | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
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.
history-insight
team-attention
This skill should be used when user wants to access, capture, or reference Claude Code session history. Trigger when user says "capture session", "save session history", or references past/current conversation as a source - whether for saving, extracting, summarizing, or reviewing. This includes any mention of "what we discussed", "today's work", "session history", or when user treats the conversation itself as source material (e.g., "from our conversation").
log
dev-whitecrow
기록 스킬. 중요한 의사결정이나 순간을 Decision_Log나 History에 빠르게 기록합니다.
distill
dev-whitecrow
정제 스킬. Inbox의 날것의 생각(Raw Data)을 읽어 분석하고, 이를 The_Ark의 적절한 위치에 구조화하여 배치합니다. 온보딩 단계에 따라 다르게 작동합니다.
wiki-fileback
GYF0311
把对话中产生的洞察/决策/事实按主语写回 corpus，追加 timeline 或新建页面。触发词：记一下、存下来、笔记、把刚才那个放进去、fileback、存回知识库。
paper-connections-session-summary
IcyChlorine
Update durable workflow/docs and write a new Paper Connections session summary for the current worktree. Use near session close-out when the user asks to summarize lessons learned, create a new session summary, or says `总结沉淀`.