Run any Skill in Manus with one click

tesseron-docs

Stars18

Forks0

UpdatedJune 9, 2026 at 20:28

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

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

Eigenwise

Eigenwise/tesseron

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name

tesseron-docs

description

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__*:

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.
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.
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.
Fall back to list_docs only when the user wants the full catalogue ("what are all the protocol pages?") or when search_docs keeps missing the page you expect.

When not to use this skill

For orientation or mental-model questions ("what is Tesseron?", "how does the SDK fit together?", "which consumer package should I use?") — load the framework skill. That skill is a cheat sheet; this one is a manual.
For project-integration tasks ("add Tesseron to this app", "switch to @tesseron/react", "upgrade versions") — load the tesseron-dev skill.
For codebase mapping or review — load the tesseron-explorer or tesseron-reviewer skill. They read the project, not the docs.

Fallbacks when the MCP server is not configured

If calls to mcp__plugin_tesseron_tesseron-docs__* fail (e.g. the user has disabled the MCP server) fall back in order:

Read directly from docs/src/content/docs/**/*.{md,mdx} if the workspace is the Tesseron monorepo itself.
Fetch the deployed site: https://eigenwise.github.io/tesseron/llms-full.txt has the complete docs as plain text; https://eigenwise.github.io/tesseron/<section>/<slug>/ serves the rendered page.
Defer to the framework skill's bundled reference files (plugin/skills/framework/references/*.md).

Never answer precision questions from training data alone without noting that you could not retrieve the current spec.

Citing sources

When you read a page via read_doc, cite it by slug and link the hosted URL so the user can verify. Example:

Per protocol/handshake (https://eigenwise.github.io/tesseron/protocol/handshake/), the welcome frame carries sessionId, claimCode, resumeToken, and the negotiated capabilities.

The slug is stable; the published URL tracks the same path.

More from this repository

same repository

tesseron-reviewer

Eigenwise/tesseron

Reviews Tesseron TypeScript code for framework- and protocol-specific correctness — app manifest hygiene, action/resource builder invariants, ActionContext capability checks, handler async/signal forwarding, subscriber cleanup, session resume flow, React hook registration patterns, gateway origin-allowlist sanity — using confidence-based filtering. Use PROACTIVELY after any change to Tesseron code, before commit or PR, and whenever the user asks to review, audit, check, or validate code that imports from `@tesseron/core`, `@tesseron/web`, `@tesseron/server`, `@tesseron/react`, or `@tesseron/mcp`. Complements generic code review by focusing only on Tesseron-specific concerns. The caller should pass the scope (diff, file paths, or module) in the invocation prompt.

2026-06-0918

framework

Eigenwise/tesseron

Quick-reference mental model for the Tesseron TypeScript SDK — core abstractions (app, action, resource, handler, ActionContext, transport, session, gateway), canonical imports per consumer package (`@tesseron/web`, `/server`, `/react`, `/core`, `/mcp`), and the minimum-viable-app template. Load when the user is starting Tesseron work, wiring a first action or resource, deciding which consumer package to import, writing a handler for the first time, or orienting on how the pieces fit together. Triggers on code that imports from `@tesseron/*`, on calls to `tesseron.action(...)`, `tesseron.resource(...)`, `tesseron.connect(...)`, `useTesseronAction`, `useTesseronResource`, or `useTesseronConnection`, and on broad questions like "what is Tesseron", "how do actions work", "where do I start". For authoritative specs — exact wire format, error code tables, handshake and resume shapes, full protocol behaviour — prefer the `tesseron-docs` skill, which queries the live `@tesseron/docs-mcp` server. This skill is the ch

2026-05-2918

tesseron-explorer

Eigenwise/tesseron

Maps existing Tesseron TypeScript codebases — catalogs apps, actions, resources, context-method usage, transports, React hooks, and session-lifecycle wiring; traces how agent invocations flow through handlers into app state; returns a compact architecture summary with file:line references. Use PROACTIVELY when the user asks to "explore", "map", "understand", "analyze", "trace", or "explain how this works" in a project that imports from `@tesseron/core`, `@tesseron/web`, `@tesseron/server`, `@tesseron/react`, or `@tesseron/mcp`, or before extending a non-trivial Tesseron codebase. The caller should pass the scope (project root, package, or specific feature) in the invocation prompt.

2026-04-2918

update-docs

Eigenwise/tesseron

Use this skill after any change to `packages/**` source that shifts Tesseron's public surface - protocol messages, exported types, action/resource builder APIs, ActionContext methods, transports, gateway CLI flags, or React hooks - to sync `docs/src/content/docs/` so the Starlight site matches the code. Triggers on "update the docs", "sync docs", "docs are stale after this change", or when a session ends with public-surface edits unaccompanied by doc edits. Do NOT trigger for test-only, tooling-only, or internal refactors that leave the public surface identical.

2026-04-2318

tesseron-diagram

Eigenwise/tesseron

Create professional technical diagrams (architecture, sequence, state, flow) in the Tesseron docs visual language — dark slate base with a single amber accent, dotted-grid background, gradient cards, Lucide-style icons, Gaussian-blur glow on the emphasized node, and Inter + JetBrains Mono typography. Use when creating docs diagrams for a Tesseron-style project, any Starlight/Astro docs site that wants a restrained monochrome-plus-one-accent aesthetic, or when the user says "use our Tesseron design system".

2026-04-2118

name

tesseron-docs

description

Tesseron docs

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__*:

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.
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.
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.
Fall back to list_docs only when the user wants the full catalogue ("what are all the protocol pages?") or when search_docs keeps missing the page you expect.

When not to use this skill

For orientation or mental-model questions ("what is Tesseron?", "how does the SDK fit together?", "which consumer package should I use?") — load the framework skill. That skill is a cheat sheet; this one is a manual.
For project-integration tasks ("add Tesseron to this app", "switch to @tesseron/react", "upgrade versions") — load the tesseron-dev skill.
For codebase mapping or review — load the tesseron-explorer or tesseron-reviewer skill. They read the project, not the docs.

Fallbacks when the MCP server is not configured

If calls to mcp__plugin_tesseron_tesseron-docs__* fail (e.g. the user has disabled the MCP server) fall back in order:

Read directly from docs/src/content/docs/**/*.{md,mdx} if the workspace is the Tesseron monorepo itself.
Fetch the deployed site: https://eigenwise.github.io/tesseron/llms-full.txt has the complete docs as plain text; https://eigenwise.github.io/tesseron/<section>/<slug>/ serves the rendered page.
Defer to the framework skill's bundled reference files (plugin/skills/framework/references/*.md).

Never answer precision questions from training data alone without noting that you could not retrieve the current spec.

Citing sources

When you read a page via read_doc, cite it by slug and link the hosted URL so the user can verify. Example:

Per protocol/handshake (https://eigenwise.github.io/tesseron/protocol/handshake/), the welcome frame carries sessionId, claimCode, resumeToken, and the negotiated capabilities.

The slug is stable; the published URL tracks the same path.