Menu
Linear via mock MCP (e2e test fixture — do not use in production)
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Use when modifying logging, error handling, or diagnostic messages — logger setup, transports, error diagnosis patterns in src/logger.ts and src/errors.ts
Use when modifying the trusted host process — server orchestration, message routing, IPC handler, request lifecycle, event streaming, file handling, plugin loading, or agent delegation in src/host/
Use when modifying the sandboxed agent process — runner, IPC client, local/IPC tools, tool catalog, prompt building, or identity loading in src/agent/
Use when modifying agent sandbox isolation -- Docker, Apple Container (macOS), or k8s providers in src/providers/sandbox/
Use when modifying IPC protocol between host and agent — schemas, actions, length-prefix framing, or Zod validation in ipc-schemas.ts and ipc-server.ts
AX project architecture and coding skills - use sub-skills for specific subsystems (agent, host, cli, providers, etc.)
| name | linear_mcp |
| description | Linear via mock MCP (e2e test fixture — do not use in production) |
| mcpServers | [{"name":"linear","url":"https://mock-target.test/mcp/linear","transport":"http"}] |
This is a test-fixture skill used by the Task 4.4 e2e test. It declares a
mock MCP server at https://mock-target.test/mcp/linear; config.url_rewrites
in kind-values.yaml redirects that hostname to the e2e mock server where
a small JSON-RPC 2.0 handler speaks MCP.
Tools advertised by the mock: get_team, list_cycles, list_issues.
The Task 4.4 test chains all three through the unified call_tool indirect
dispatch pipeline to prove the catalog is populated correctly, MCP calls
actually land on the server, and zero retries are needed.
