From gotcontext
Query-guided compression of a documentation site, docs folder, README, wiki, or specification for Q&A. Use this skill whenever the user points you at multi-page reference material and wants to find something in it. Trigger phrases include "help me find X in these docs", "what does the Y docs say about Z", "search the Stripe/AWS/Anthropic docs for", "summarize this reference", "check the docs for". Passes the user's question as a query parameter so gotcontext weights relevant sections heavier and compresses off-topic sections more aggressively — keeps answers grounded without loading every page.
How this skill is triggered — by the user, by Claude, or both
Slash command
/gotcontext:ingest-docsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
A docs tree is the perfect target for query-guided compression:
A docs tree is the perfect target for query-guided compression: sprawling, repetitive, and mostly irrelevant to any single question. Loading the full tree exhausts context; loading one page misses cross-references. Query-guided compression solves both by keeping what's relevant to the user's question and shrinking what isn't.
./docs), a docs URL, or a list
of URLs. Ask the user if it's unclear.fidelity=balanced
without a query.ingest_context MCP tool with:
source — path or URL(s)query — the user's question (enables relevance-weighted
compression; highly recommended)fidelity=balanced — good Q&A accuracy, ~50% savingsRead it./docs directory in a repoWithin one session, cache the compressed result of a tree after the first call and query against the cached blob for follow-ups. Each re-ingestion is a paid compression call — don't waste the user's credits on the same tree twice.
npx claudepluginhub oimiragieo/gotcontext-sdk --plugin gotcontextFetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Applies a firm's KYC/AML rules grid to parsed onboarding records: assigns risk rating, checks required documents, outputs rule outcomes with citations, and routes for escalation.
Generates daily or weekly digests of activity from connected sources (chat, email, docs, tasks, CRM), highlighting action items, decisions, mentions, and project updates.