cogni-dao/cogni / .claude/skills/knowledge-syntropy-expert
knowledge-syntropy-expert
VerifiedUse when organizing or curating a Cogni knowledge hub, deciding where durable knowledge belongs, or migrating Markdown docs and skills into the hub. Read the node knowledge axioms first, then the complete guide for the task.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 2.5 KB |
SKILL.md
View on GitHub---
name: knowledge-syntropy-expert
description: Use when organizing or curating a Cogni knowledge hub, deciding where durable knowledge belongs, or migrating Markdown docs and skills into the hub. Read the node knowledge axioms first, then the complete guide for the task.
---
# Knowledge stewardship
This file is the local discovery shell. The hub owns the axioms and procedures;
session cognition supplies the operating contract.
## Read the axioms first
On every invocation, read the full `content` of
`GET /api/v1/knowledge/md-to-hub-design` before proposing or changing knowledge.
Use the current node's verified origin and saved `COGNI_NODE_API_KEY`; do not
default a sovereign node's reads or writes to the operator.
Then fetch the complete guide for the task through
`GET /api/v1/knowledge/{id}`. Index rows and citation links are pointers, not
the instructions: read the selected bodies and their required dependencies.
| task | read |
| ------------------------------------------------------------------------------ | ----------------------------- |
| Migrate repository Markdown, including specs and skills | `migrate-markdown-to-hub` |
| Split a mixed document into skills, guides, contracts, rationale, and findings | `segment-markdown-knowledge` |
| Thin a skill while preserving harness discovery and local resources | `migrate-skill-to-hub` |
| Repair links, anchors, loaders, and references before thinning or purging | `retire-markdown-sources` |
| Judge whether knowledge deserves an entry or refinement | `knowledge-syntropy-protocol` |
| Recall both planes, contribute, cite, and obtain human review | `knowledge-contribution-flow` |
| Choose a registered domain | `cogni-domain-taxonomy` |
| Choose a useful human visual | `knowledge-human-visuals` |
Use the migration guide's full sequence rather than stopping after classification
or an upload. Preserve the source until its reviewed replacement and consumers
pass the guide's cutover gates. Progress and current blockers belong in the
existing work item, not this shell.
If an entry is missing or unreachable, retain the source documents and use only
verified startup/recovery instructions. Record and resolve the failed retrieval
gate; do not invent missing guidance or claim the migration is complete.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file). | Stars: 198k | Updated | Claude CodeCodex | Unverified | Install |
| doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |