eigenwise

@eigenwise source repo

32 skills
0 followers
5 hours ago last updated

▌
Release · eigenwise
Release a new version of atomic-agents to PyPI and GitHub. Use when the user asks to "release", "publish", "deploy", or "bump version" for atomic-agents.

0
installs
▌
New App · eigenwise
Scaffold a new Atomic Agents project from scratch — create the directory, `pyproject.toml`, env file, first agent, and a runnable entry point. Use when the user asks to start a new atomic-agents project from scratch, says "scaffold" / "new project" / "start from zero", or runs `/atomic-agents:new-app`.

0
installs
▌
Troubleshoot · eigenwise
Diagnose and fix a failing or misbehaving Atomic Agents app — import errors, schema validation failures, empty or malformed LLM output, provider role/mode errors, history and context problems, MCP transport errors. Use when the user reports an error, traceback, or wrong behavior in atomic-agents code, asks "why is my agent not working / crashing / returning garbage", or pastes a `ValidationError`, `ImportError`, or provider API error from an atomic-agents project.

0
installs
▌
Create Atomic Tool · eigenwise
Build a `BaseTool[InSchema, OutSchema]` subclass — input/output schemas, `BaseToolConfig`, `run()` (and optional `run_async()`), env-driven secrets, typed failure outputs. Use when the user asks to "add a tool", "create a tool", "wrap an API as a tool", "build a `BaseTool`", "make a calculator/search/weather tool", or runs `/atomic-agents:create-atomic-tool`.

0
installs
▌
Create Atomic Agent · eigenwise
Build and wire an `AtomicAgent[InSchema, OutSchema]` — schemas, `AgentConfig`, `SystemPromptGenerator`, provider client, history, hooks, optional context providers. Use when the user asks to "create an agent", "add another agent", "build an `AtomicAgent`", "wire up an agent", "make a planner/router/extractor agent", or runs `/atomic-agents:create-atomic-agent`.

0
installs
▌
Create Atomic Schema · eigenwise
Design and write a `BaseIOSchema` input/output pair for an Atomic Agents agent or tool — docstrings, field descriptions, validators, error variants. Use when the user asks to "create a schema", "design the input/output schema", "define an `IOSchema`", "write a `BaseIOSchema`", "model the agent's output", or runs `/atomic-agents:create-atomic-schema`.

0
installs
▌
Create Atomic Context Provider · eigenwise
Build a `BaseDynamicContextProvider` that injects a named, titled block into an agent's system prompt at every `run()` — current time, user identity, retrieved RAG docs, session state, cached DB schema. Use when the user asks to "add a context provider", "inject X into the prompt", "give the agent dynamic context", "wire up RAG", "make a `BaseDynamicContextProvider`", or runs `/atomic-agents:create-atomic-context-provider`.

0
installs
▌
Framework · eigenwise bundle
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

0
installs
▌
Docs Drift · eigenwise
Check whether the hub docs kept up with the four SDK repositories (tesseron-typescript, tesseron-rust, tesseron-python, tesseron-cpp) and the published hub packages. Use before or after an SDK release, when asked "are the docs stale", "did the docs keep up with the release", "which docs pin an old version", or as the release gate that backs the AGENTS.md rule that an SDK release PR is complete only after its hub docs PR merged.

0
installs
▌
Update Docs · eigenwise
Use this skill after any change to `gateway/**`, `docs-mcp/**`, or SDK source in a language repository 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.

0
installs
▌
Tesseron Dev · eigenwise
Tesseron dev

0
installs
▌
Tesseron Docs · eigenwise
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

0
installs
▌
Tesseron Diagram · eigenwise bundle
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".

0
installs
▌
Tesseron Explorer · eigenwise
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.

0
installs
▌
Tesseron Reviewer · eigenwise
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.

0
installs
▌
Board · eigenwise
Open the sidequest board (live Kanban of your tickets) in the browser

0
installs
▌
Groom · eigenwise
Audit a Sidequest board for completed, stale, duplicate, or superseded tickets, then safely close clear cases. Use for board grooming, cleanup, or ticket audits.

0
installs
▌
Add Rule · eigenwise bundle
Create or edit a live-rules instruction in the project's atomic rule set. Use to add a rule, coding guideline, guardrail, convention, or automatic reminder.

0
installs
▌
Setup · eigenwise bundle
Set up a Claude Code workspace for a new or existing project, informed by hindsight from the user's whole session history. Installs and wires whichever Toolshed pieces the project actually wants (codebase-mapper, live-rules, sidequest's routing and executors, observability, model-gateway are each independent and opt-in) plus stack plugins, seeds rules and permissions from what the history shows the user actually needs. Use for workspace setup, .claude configuration, project bootstrap, or Toolshed installation.

0
installs
▌
Sidequest · eigenwise bundle
Open or manage Sidequest tickets and board workflow. Use for board lifecycle work, planning substantial or ambiguous work, and dispatch/integration/recovery. Stay inline for quick edits at a known location, direct questions, or operational requests.

0
installs
▌
User Story · eigenwise
Drive a feature from a rough request to shipped, integrated work through the Sidequest board, at a depth you choose to match the work: recon, competing architecture proposals judged and merged into one contract, a story holding the complete backlog, one or many parallel executor waves, and a review pass sized to the risk. Use this by default for anything beyond a small task, including requests to build, add, implement, redesign, or extend a feature, a subsystem, or any multi-part change, even when they never mention Sidequest, tickets, or a board. Use it in place of a generic feature-development flow: those flows have the expensive orchestrator explore, design, and implement inline, which is the exact loop this board replaces. Skip it for a one-line fix to files the user named, and for operational asks like running the app or answering from context.

0
installs
▌
Resupply · eigenwise bundle
Work out what a workspace is short of and get it: a measurement nobody can run yet, work being done by hand that a plugin or skill should own, knowledge that keeps being re-derived, and the setup pushing back. Reads recent sessions for what the user was actually working toward, then proposes one item at a time for approval. Use whenever the user asks what would make this easier or faster, what they are missing, why something keeps being hard, or what could have gone better; when they want to improve their Claude Code setup, tooling, or workflow; whenever the quartermaster nudge fires at SessionStart or a Stop-time offer blocks a real pause, after proactively asking and receiving the user's approval or when the user has explicitly given standing permission for these rounds; proactively offer the round at a natural pause after a long or expensive stretch of work; or when they are starting a goal they have no way to verify. Running the pass requires current or standing user approval. Every recommendation then ne

0
installs
▌
Manage Rules · eigenwise
Inspect, audit, enable, or disable project live-rules. Use to list rules, check active instructions, explain an injected rule, or recover an atomic manifest.

0
installs
▌
Model Gateway · eigenwise
Set up, update, or diagnose the local ChatGPT/Codex gateway for Claude Code's /model picker. Use for gateway setup, login, model visibility, routing, or failures.

0
installs
▌
Verify Discipline · eigenwise
Run focused verification for a ticket and report what it actually covers. The orchestrator runs the one combined full gate after integration. Use when running tests, verifying a change, or choosing a test command.

0
installs
▌
Map Codebase · eigenwise bundle
Create a self-maintaining codebase map in .claude/.codebase-info/. Use to map, document, analyze, or onboard a codebase, including a new project.

0
installs
▌
Verify · eigenwise
Verify model-gateway

0
installs
▌
Toolshed Doctor · eigenwise
Run a read-only health check for Quartermaster and installed Toolshed plugins. Use to diagnose Toolshed, check workspace health, or troubleshoot stale plugins.

0
installs
▌
Update Toolshed · eigenwise
Update installed Eigenwise Toolshed plugins and model-gateway, or check their status. Use to update Toolshed, refresh the marketplace, or check versions.

0
installs
▌
Update Codebase Map · eigenwise
Refresh an existing .claude/.codebase-info/ map after code changes. Use for stale codebase or architecture docs; use map-codebase to create one.

0
installs
▌
Enable Project Telemetry · eigenwise bundle
Opt the current project into local Claude Code usage telemetry, or verify its setup. Use to enable, disable, or check project telemetry.

0
installs
▌
Remote Control Compatibility · eigenwise
Choose RC-compatibility or turn Model Gateway off for one project when /remote-control is unavailable.

0
installs

32 published skills