keine-update-maps
Use this skill when creating or editing a topic map in the Keine knowledge base. Trigger after ingesting a set of related entries on a topic, or when asked to summarize, compare, survey, or give an overview of a subject area. Also use when a user asks a broad question and you want to leave a synthesized overview for future agents or readers. Maps are different from entries — they synthesize rather than document.
Best use case
keine-update-maps is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Use this skill when creating or editing a topic map in the Keine knowledge base. Trigger after ingesting a set of related entries on a topic, or when asked to summarize, compare, survey, or give an overview of a subject area. Also use when a user asks a broad question and you want to leave a synthesized overview for future agents or readers. Maps are different from entries — they synthesize rather than document.
Teams using keine-update-maps 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-update-maps/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How keine-update-maps Compares
| Feature / Agent | keine-update-maps | 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?
Use this skill when creating or editing a topic map in the Keine knowledge base. Trigger after ingesting a set of related entries on a topic, or when asked to summarize, compare, survey, or give an overview of a subject area. Also use when a user asks a broad question and you want to leave a synthesized overview for future agents or readers. Maps are different from entries — they synthesize rather than document.
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
# Creating and Editing Topic Maps ## What a topic map is for A topic map is a synthesized overview of a subject area. Where entries capture individual pieces of knowledge, a map connects them — explaining how things evolved, how they compare, and where to start depending on what someone needs. Maps serve two audiences equally: - **Humans** wanting to understand a topic landscape at a glance - **Future agents** that need to quickly orient themselves before answering questions or creating more entries A map is worth creating when there are enough related entries (roughly 4–5+) that the relationships between them tell a story worth telling. ## Creating a new map ### 1. Gather related entries Search for everything relevant to the topic: ```sh grep -ri "keyword" docs/ ls docs/tags/<relevant-tag>.md ``` Read the entries. Understand the landscape before writing — the map's value comes from synthesis, not just listing links. ### 2. Write the map File location: `docs/maps/<slug>.md` Frontmatter: ```yaml --- title: "Topic Area Name" tags: [tag-a, tag-b] --- ``` Suggested body structure (adapt as needed): - **H1** = title - **## Overview** — brief introduction: what this topic area is and why it matters - **## Landscape** — how the technologies/concepts relate, how they evolved, how they compare; use H3 subheadings per major area or technology - **## Where to start** — practical guidance for different starting points (e.g. "if you want X, start with Y") - **## Learning Path** *(optional)* — ordered list of entries to read in sequence - **## Entries** — full list of related entries with one-line descriptions The map should read like a knowledgeable friend orienting you to a topic — not a dry index. ### 3. Commit ```sh git add docs/maps/<slug>.md git commit -m "docs(map): add <title>" ``` --- ## Editing an existing map Maps go stale as new entries are added. Update a map when: - New entries have been created that belong in it - The landscape has shifted (new technology, deprecated approach, etc.) - The overview or comparisons are no longer accurate After editing: ```sh git add docs/maps/<slug>.md git commit -m "docs(map): update <title>" ```
Related Skills
keine-update-entries
Use this skill when creating a new knowledge entry or editing an existing one in the Keine knowledge base. Trigger when asked to add, ingest, document, or update any piece of knowledge — a URL, PDF, book, concept, note, or research finding. Use this skill even when the user doesn't say "entry" — if they want to capture or update knowledge, this is the skill.
keine-research
Use this skill only when the user explicitly requests deep research or a detailed report on a topic — phrases like "research X", "give me a detailed report on X", "deep dive into X", "I want a thorough analysis of X", or "write me a research report on X". Do NOT trigger for casual questions, quick lookups, or requests to add/edit entries. This is a heavyweight, multi-step workflow that mines the knowledge base, fills gaps with web research, creates new KB entries along the way, and produces a long-form, citation-rich research report saved to reports/.
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.
keine-chat
Use this skill whenever the user wants to discuss, explore, or ask questions about a topic using the local knowledge base as grounding. Trigger on phrases like "what do you know about X", "let's talk about X", "explain X", "I'm trying to understand X", "discuss X with me", "what does the KB have on X", "help me think through X", "tell me about X", or any conversational question about a concept or idea. Also trigger when the user asks a question that could be answered from stored knowledge, even if they don't explicitly say "knowledge base". This is the default skill for knowledge-grounded conversation — prefer it over answering from memory alone whenever the KB might have relevant content. Do NOT trigger for: deep research reports (use keine-research), adding new entries (use keine-update-entries), or creating maps (use keine-update-maps).
semantic-scholar
Search and retrieve research paper metadata using the Semantic Scholar Academic Graph API via curl. Use this skill whenever the user wants to find academic papers, look up citations, get paper details by DOI/arXiv ID/title, explore an author's publications, or fetch reference/citation lists. Trigger on phrases like "find papers on X", "look up this paper", "how many citations does X have", "papers citing X", "search for research about X", "get metadata for arxiv:...", or any request to explore academic literature. Always use this skill when the task involves academic paper search or metadata retrieval — even if the user just pastes a DOI or arXiv link and wants info about it.
openalex
Search and retrieve scholarly metadata from the OpenAlex API — a free, open catalog of 270M+ works, 90M+ authors, and 100K+ sources. Use this skill whenever the user wants to query OpenAlex for works, authors, institutions, sources, topics, publishers, or funders. Trigger on phrases like "search OpenAlex for X", "find papers in OpenAlex", "OpenAlex works by author Y", "get institution metadata from OpenAlex", "look up this DOI in OpenAlex", "how many works does institution X have in OpenAlex", or any request that specifically involves the OpenAlex API or database. Also trigger when the user pastes an OpenAlex ID (like W1234567890 or A5023888391) or mentions OpenAlex by name in any research context. This skill complements the semantic-scholar skill — use OpenAlex when the user asks for it specifically, when they need institution/funder/topic data that Semantic Scholar doesn't cover, or when they want open-access filtering and aggregation features unique to OpenAlex.
update-pr
Stage, commit, and push follow-up changes to an existing feature branch or PR. Use for quick iterations.
chezmoi-update
This skill should be used when the user asks to "update chezmoi", "sync dotfiles", "match live state", "match repo state", "chezmoi re-add", "chezmoi diff fix", "chezmoi apply", or mentions chezmoi source/live discrepancies, divergence between dotfiles repo and filesystem, or wants to reconcile chezmoi state in either direction.
cfn-expert-update
Update CFN system expert agent with relevant git commits and project changes
implementation-plan-updates
Defines the pattern for updating project documentation when completing features. Use when marking features as complete to ensure consistent documentation of implementation status, test coverage, and deliverables.
dependency-updater
Smart dependency management for any language. Auto-detects project type, applies safe updates automatically, prompts for major versions, diagnoses and fixes dependency issues.
documentation-update
Reusable logic for updating repository documentation (README, indices, tables) with new content while preserving formatting and structure