Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
Spin up a **background agent** to do the research, so you keep working while it reads.
Its job:
1. Investigate the question against **primary sources** (official docs, source code, specs, first-party APIs), not a secondary write-up of them. Follow every claim back to the source that owns it.
2. Write the findings to a single Markdown file, citing each claim's source.
3. Save it where the repo already keeps such notes; match the existing convention, and if there is none, put it somewhere sensible and say where.
The line at the top of this page pins the label git:20260821.05c0d52, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_morixr2lurxxnad2
GET https://markdownregistry.com/api/v1/resolve?ref=vodailocz/kilo-kit-mcp/research
GET https://markdownregistry.com/api/v1/blob/985569f15739c713d6784887c3d186d4ef9ac85bec5ad9c068d25bf0739928e4
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
vodailocz/kilo-kit-mcp · skills/agent-frameworks/agent-memory/SKILL.md · Use when implementing or managing persistent, hierarchical memory systems for AI agents. Covers cross-session state…
vodailocz/kilo-kit-mcp · skills/agent-frameworks/mcp-agent-patterns/SKILL.md · Use when integrating or optimizing Model Context Protocol (MCP) servers and clients. Keywords: MCP, Model Context…
vodailocz/kilo-kit-mcp · skills/agent-frameworks/workflow-state-machines/SKILL.md · Use when designing, implementing, or debugging complex agentic workflows using state machine patterns. Keywords: state…
vodailocz/kilo-kit-mcp · skills/ai-media/ai-multimodal/SKILL.md · Process and generate multimedia content using Google Gemini API. Capabilities include analyze audio files…
vodailocz/kilo-kit-mcp · skills/ai-media/screenshot/SKILL.md · Use when the user explicitly asks for a desktop or system screenshot (full screen, specific app or window, or a pixel…
sethgammon/citadel · skills/research/SKILL.md · Focused research investigations. Converts questions into structured findings with confidence levels and source…
zhongkaifu/tensorsharp · TensorAgent/skills/research/SKILL.md · Use for web searches and current information lookups, finding sources, and fact-checking without being given any URLs…
oliver-kriska/claude-elixir-phoenix · plugins/elixir-phoenix/skills/research/SKILL.md · Research Elixir/Phoenix/Ecto topics or evaluate Hex libraries (--library). Use when learning about libraries, patterns…
boshu2/agentops · plugin/skills/research/SKILL.md · Answer one cited question on code, history, claims or patterns. Use when: asked how it works, why it changed, if a…
boshu2/agentops · skills/research/SKILL.md · Answer one cited question on code, history, claims or patterns. Use when: asked how it works, why it changed, if a…
