context

Read, write, list, and delete ContextHub documents via ch_*_context MCP tools.

Updated May 12, 2026
One-click install
npx skills add https://github.com/contexthub-md/marketplace --skill context-contexthub-md
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: context
Source: https://github.com/contexthub-md/marketplace/tree/main/contexthub/skills/context
Command: npx skills add https://github.com/contexthub-md/marketplace --skill context-contexthub-md

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams using ContextHub need a reliable way to store and manage documents (mission docs, project docs, SOPs, artifacts) so they are properly indexed and searchable, instead of bypassing the metadata pipeline by writing raw files to S3 or misusing memos. ## Core Features & Use Cases - Document CRUD via MCP tools: Create, read, list, and delete documents of any content type (mission, project, sop, artifact, context, session) using ch_write_context, ch_read_context, ch_list_context, and ch_delete_context. - Automatic metadata and indexing: Writes run a metadata sidecar, Obsidian frontmatter injection, and Bedrock KB indexing so documents are searchable and correctly tagged. - Use Case: Attach an implementation plan to a mission by calling ch_write_context with content_type="mission" and a path like {mission_id}/docs/plan.md, then verify it landed with ch_list_context. ## Quick Start Ask the agent to save the current plan as a document on your mission in ContextHub and then list the mission's docs to confirm it was stored.

Frequently Asked Questions about context

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I attach a document to a mission in ContextHub?

Use ch_write_context with content_type="mission" and a path like {mission_id}/docs/your-file.md, passing the file content plus mission_id and project_id. The tool adds metadata, frontmatter, and KB indexing automatically.

How do I list or read documents stored in ContextHub?

Call ch_list_context with a content_type and optional path prefix to list documents, and ch_read_context to read one. Use detail="summary" to get metadata only without the body, reducing tokens shown to the model.

Should I use ch_write_context or ch_create_memo to save a document?

Use ch_write_context for documents. Memos are findings or alerts and will not appear in a mission's or project's docs, while ch_write_context stores a proper indexed document.

Why does ch_write_context take a long time or report indexed false?

By default it waits for KB indexing verification, which can take around 30 seconds. Pass both wait_for_index=False and verify_access=False for a fast asynchronous write when immediate searchability is not needed.

Why does a recursive delete fail in ContextHub?

Recursive deletes with ch_delete_context require confirm=True as a safety guard. Without it the tool refuses the operation, so pass confirm=True explicitly when deleting a path tree.