knowledge-base-mcp: Skill for Claude Code

.claude/skills/research-capture/SKILL.md

research-capture is a skill for Claude Code from Diptanil-x-42/knowledge-base-mcp. It costs 48 tokens per session (574 once invoked), scanned A, original, MIT.

A workflow for saving research findings as organized notes in a knowledge base and checking that knowledge base's health.

In plain words
What is it for?
Use it to capture new findings, search or review saved research, organize notes by tags, and report missing information or next research steps.
Why use it?
It breaks research into focused notes with titles, details, and tags, making later searching and review easier.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is Diptanil-x-42/knowledge-base-mcp's own configuration. It tells Claude Code how to work on knowledge-base-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything knowledge-base-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Diptanil-x-42/knowledge-base-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/Diptanil-x-42/knowledge-base-mcp/main/.claude/skills/research-capture/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/Diptanil-x-42/knowledge-base-mcp

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for research-capture

README.md
[![agentmods](https://agentmods.dev/badge/skills/diptanil-x-42/knowledge-base-mcp/research-capture/github.svg)](https://agentmods.dev/skills/diptanil-x-42/knowledge-base-mcp/research-capture)
Your own site
<a href="https://agentmods.dev/skills/diptanil-x-42/knowledge-base-mcp/research-capture"><img src="https://agentmods.dev/badge/skills/diptanil-x-42/knowledge-base-mcp/research-capture/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for research-capture

Your own site · 80×15
<a href="https://agentmods.dev/skills/diptanil-x-42/knowledge-base-mcp/research-capture"><img src="https://agentmods.dev/badge/skills/diptanil-x-42/knowledge-base-mcp/research-capture.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 574 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00048 $0.00574
Opus 5 $0.00024 $0.00287
Sonnet 5 $0.00010 $0.00115
Haiku 4.5 $0.00005 $0.00057

Measured 9d ago against content hash 9ed006ace61d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

research-capture scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/research-capture/SKILL.md · 68 lines

How it starts

The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Research Capture Workflow

When the user asks you to research, capture, or organize information, follow this workflow using the knowledge-base MCP tools.

Capturing New Research

  1. Break the information into individual, focused notes
  2. Use add_note for each distinct finding with:
    • A clear, descriptive title (e.g., "MCP uses JSON-RPC 2.0 for message encoding")
    • Detailed content explaining the finding
    • Relevant tags for categorization
  3. After saving, confirm what was captured with note IDs

Reviewing Existing Research

  1. Start by running list_tags to see what topics exist
  2. Use get_notes_by_tag to pull notes on the requested topic
  3. Use search_notes for keyword-based lookups when the exact tag is unknown
  4. Present findings in a structured format

Research Summary Format

When summarizing research on a topic, structure your response as:

Key Findings

  • Bullet points of main discoveries

Connections

  • How different notes relate to each other

Knowledge Gaps

  • What is missing or needs further research

Suggested Next Steps

  • What to research or capture next

Tag Conventions

  • Use lowercase with hyphens: machine-learning not Machine Learning
  • Use broad category tags: python, web-dev, ai, devops
  • Add specificity tags: fastapi, react-hooks, prompt-engineering
  • Always include at least one broad and one specific tag per note

Cleanup

  • If the user says information is outdated, use delete_note with the note ID
  • Before deleting, confirm the note title and ID with the user

Knowledge Base Health Check

When the user asks to check the health of their knowledge base, or when starting a new research session:

  1. Run get_statistics to get current metrics
  2. Analyze the results and report:
    • Coverage: Which tags have the most/fewest notes
    • Gaps: Tags with only 1-2 notes that may need more research
    • Activity: How recent the latest notes are (stale if older than 2 weeks)
    • Depth: Whether average content length suggests detailed or shallow notes
  3. Suggest specific actions:
    • Topics that need more notes based on underrepresented tags
    • Tags that could be consolidated (too similar)
    • Areas where the user might want to do fresh research

Read the full file on GitHub · 68 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 68 lines · 48 tokens per session scan A 9ed006ace61d

Subscribe to this mod's changes

research-capture is a skill published in the GitHub repository Diptanil-x-42/knowledge-base-mcp (0 stars, last pushed 2mo ago), licensed MIT. It adds 48 tokens to every session and 574 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

media-ingest

Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.

garrytan/gbrain · 52 tokens

mem0-oss-to-platform

Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…

mem0ai/mem0 · 273 tokens

Cortex

Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…

danielmiessler/LifeOS · 196 tokens

memory

Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.

opensquilla/opensquilla · 44 tokens

ha-data-stores

Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…

shiwenwen/hope-agent · 115 tokens

establishing-project-context

Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.

GanyuanRan/Aegis · 45 tokens