← ClaudeAtlas

tesseron-docslisted

Authoritative Tesseron documentation lookup via the `@tesseron/docs-mcp` MCP server. Calls `search_docs` to find relevant pages and `read_doc` to fetch the full markdown body when the user asks precision questions about Tesseron protocol or SDK behaviour. Triggers on requests that need an exact spec, not an overview — wire format (JSON-RPC envelopes, `tesseron/hello`, `tesseron/welcome`, `tesseron/resume`, `actions/progress`, `actions/cancel`), transport framing, handshake and claim-code flow, session resume and resumeToken, lifecycle transitions, sampling contract, elicitation contract (`ctx.confirm`, `ctx.elicit`), progress + cancellation via `AbortSignal`, error codes (`TesseronErrorCode`, `SamplingNotAvailableError`, `ElicitationNotAvailableError`, `TimeoutError`, `CancelledError`, `ResumeFailedError`), capability negotiation, origin allowlist, multi-app namespacing, MCP gateway config, Standard Schema (Zod, Valibot, Typebox) integration, action-builder steps, resource read/subscribe, React hook semantics
Eigenwise/tesseron · ★ 20 · AI & Automation · score 71
Install: claude install-skill Eigenwise/tesseron
# Tesseron docs This skill is the on-demand, authoritative lookup path for Tesseron documentation. Whenever precision matters (exact wire-format envelope, specific error code, fields a handshake carries, structural contract of resume) prefer calling the MCP tools below over recalling from memory or the `framework` skill's cheat sheet. ## How to use The plugin bundles `@tesseron/docs-mcp` at install time, so these tools are normally already connected in Claude Code as `mcp__plugin_tesseron_tesseron-docs__*`: 1. **Search first.** Call `search_docs({ query, limit })` with the user's question as-is (or a short paraphrase that keeps the load-bearing nouns). It returns ranked hits with `slug`, `title`, `description`, `score`, and a ~240-char `snippet`. `limit` defaults to 8 and caps at 20; 4-8 is the sweet spot. 2. **Read the top hit.** Call `read_doc({ slug })` on the first promising hit. It returns the full markdown body plus structured frontmatter (`title`, `description`, `section`, `related`). Quote the exact spec text into your answer instead of paraphrasing it. 3. **Walk the graph if the answer is cross-cutting.** The `related` field in `read_doc`'s response is a slug list. Follow those edges with more `read_doc` calls when a single page does not cover the question. Typical example: `protocol/resume` is incomplete without `protocol/handshake` and `protocol/transport`. 4. **Fall back to `list_docs` only** when the user wants the full catalogue ("what are all the protoco