keine-manage
Always use this skill before creating, editing, or tagging any document in the knowledge base. Use it when asked to add, ingest, find, link, or manage any entry.
Best use case
keine-manage is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Always use this skill before creating, editing, or tagging any document in the knowledge base. Use it when asked to add, ingest, find, link, or manage any entry.
Teams using keine-manage should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/keine-manage/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How keine-manage Compares
| Feature / Agent | keine-manage | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Always use this skill before creating, editing, or tagging any document in the knowledge base. Use it when asked to add, ingest, find, link, or manage any entry.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Keine Knowledge Base Management ## Assets ``` references |-- TEMPLATE_ENTRY.md |-- TEMPLATE_TAG.md `-- TEMPLATE_TOPIC.md scripts `-- maintain_tags.py — maintain tag index ``` ## Document Format ### Knowledge Entry (`docs/<yyyy-mm-dd-slug>.md`) ```yaml --- title: "Human-readable title" description: "One sentence for use in tag indexes" tags: ["tag1", "tag2"] source: "URL, DOI, or other reference" # required — link to the original source_type: "url | pdf | book | note" # required — omit only for original writing --- ``` Body structure: - **H1** = title (exactly one) - **## Summary** — 2-5 sentences - **## Content** — main knowledge, use H3+ for subsections - **## Related** — relative links to other docs, tags, or maps ### Tag Index (`docs/tags/<slug>.md`) Auto-maintained. **Do not edit manually.** Run `scripts/maintain_tags.py` ### Topic Map (`docs/maps/<slug>.md`) ```yaml --- title: "Topic Area Name" tags: [tag-a, tag-b] --- ``` Body: structured overview, mindmap, or learning path linking to entries. ## Workflow For the task at hand, use the appropriate sub-skill: | Task | Skill | |---|---| | Create or edit a knowledge entry | `keine-update-entries` | | Create or edit a topic map | `keine-update-maps` | | Create a deep research report | `keine-research` | ### Finding entries - By keyword: `grep -ri "term" docs/` - By tag: read `docs/tags/<tag>.md` - By topic: check `docs/maps/` for a topic map