CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ax-mcp

This skill helps an LLM build correct native Model Context Protocol integrations with @ax-llm/ax. Use when the user asks about AxMCPClient, MCP transports, tools, prompts, resources, subscriptions, tasks, sampling, elicitation, roots, authentication, OAuth, MCP Apps, recording/replay, or MCP integration with AxGen, AxAgent, AxFlow, chat, optimization, and AxEventRuntime.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A technically dense, highly actionable reference for native MCP integration, with concrete code, option names, defaults, and a solid validation checklist. Weaknesses are mild redundancy from repeating per-language details across sections, snippets that assume undefined surrounding setup, and heavy inline detail (~450 lines) with only two external doc pointers whose target files are not verifiable in the provided bundle.

Suggestions

Move the detailed subscription lifecycle semantics and the per-language configuration differences (transports, tasks, OAuth) into the referenced docs (e.g., docs/MCP_SUBSCRIPTIONS.md, a new docs/MCP_LANGUAGES.md), keeping SKILL.md as a ~150-line overview with one-level-deep pointers.

Consolidate the Python/Java/C++/Go/Rust behavior notes that currently repeat across the Transports, Multi Round-Trip Requests, Tasks, and OAuth sections into a single per-language matrix in one place.

Make the example snippets self-contained (or mark their prerequisites) so the AxGen/AxAgent/EventSource examples define or import the surrounding setup (llm, ax, agent, eventRuntime) they rely on.

DimensionReasoningScore

Conciseness

The body is dense and imperative with almost no explanation of concepts Claude already knows — no 'what is MCP' padding — and deprecated APIs are properly isolated ('callToolTask(), listTasks(), and getTaskResult() ... are deprecated'). It is not a 5 because there is trimming opportunity: the Python/Java/C++/Go/Rust per-language enumeration is repeated across four sections (transports, MRTR, tasks, OAuth) and some edge-case minutiae (e.g., 'ping() clears its deadline timer when the request settles') could move to reference docs. It is above anchor 3 since the verbosity is incidental, not pervasive padding.

4 / 5

Actionability

Mostly executable guidance: copy-paste-ready TypeScript for transport + client setup with imports and an authorization policy, concrete option names and defaults (maxInputRounds limit of five, eraStore, taskHandling: 'expose'), and runnable commands ('npm run test:mcp-events:generated', AX_MCP_ENDPOINT setup). It falls short of anchor 5 because several snippets reference undefined context (ax(...), llm, agent(...), eventRuntime, reviewer) and later examples are illustrative fragments rather than fully self-contained cases.

4 / 5

Workflow Clarity

Sections form a coherent progression (rules → transport choice → era handling → attach to AxGen/AxAgent/Flow → catalogs → advanced features) and the Testing Checklist supplies explicit validation checkpoints ('Assert namespace and tool collisions fail before model execution', 'Test authorization denial before transport execution', 'Close clients ... in finally'). It is anchor 4 rather than 5 because there is no explicit ordered sequence for the main integration flow, and error-recovery loops (e.g., what to do when a validation check in the checklist fails) are implied rather than spelled out.

4 / 5

Progressive Disclosure

References that exist are well-signaled and one level deep ('For the detailed lifecycle and troubleshooting guide, read docs/MCP_SUBSCRIPTIONS.md', 'See docs/MCP_UCP.md for compact per-language configuration snippets'), but none of the referenced files (docs/, src/examples/, the 'checked-in six-language MCP examples') are present in the bundle as provided, and the ~450-line body inlines deep detail — subscription lifecycle semantics (~70 lines) and per-language OAuth configuration — that the rationale says belongs in separate reference files. That mix of clearly-signaled references with substantial inline content that should be split matches anchor 3 ('content that should be separate is inline') better than anchor 4.

3 / 5

Total

15

/

20

Passed

Description

86%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description with an explicit third-person 'what' and a rich, explicit 'Use when...' trigger list covering the full component surface. The main weakness is that the capability statement is a single generic action ('build integrations') rather than a list of concrete actions, and a few trigger terms are generic MCP vocabulary with mild overlap risk.

DimensionReasoningScore

Specificity

The 'what' is a single action — "helps an LLM build correct native Model Context Protocol integrations with @ax-llm/ax" — which names the domain plus one concrete action but does not list several specific actions (e.g., configure transports, attach clients to programs, manage tasks/subscriptions). It matches anchor 3 ('names domain and 1-2 concrete actions, but not comprehensive') and falls short of anchor 4, which expects a list of several specific actions.

3 / 5

Completeness

It explicitly answers both questions: what ("build correct native Model Context Protocol integrations with @ax-llm/ax") and when ("Use when the user asks about AxMCPClient, MCP transports, ... AxEventRuntime") with concrete trigger phrases. This matches anchor 5 ('clearly and explicitly answers both what AND when with concrete trigger phrases'); a missing or implicit 'when' would cap it at 3, which is not the case here.

5 / 5

Trigger Term Quality

The trigger list is comprehensive and natural for this domain: "AxMCPClient, MCP transports, tools, prompts, resources, subscriptions, tasks, sampling, elicitation, roots, authentication, OAuth, MCP Apps, recording/replay", plus integration targets "AxGen, AxAgent, AxFlow, chat, optimization, and AxEventRuntime", with both the spelled-out "Model Context Protocol" and "MCP" variants present. This exceeds the anchor-4 example ('PDF files, forms, document extraction' — a few natural terms missing) and matches anchor 5's comprehensive synonym/component coverage for the niche.

5 / 5

Distinctiveness Conflict Risk

Strong niche signals (AxMCPClient, @ax-llm/ax, AxGen, AxEventRuntime) make it clearly distinguishable, matching anchor 4 ('mostly distinct; minor overlap risk with closely related skills'). It does not reach 5 because several trigger terms in the list — "tools, prompts, resources, subscriptions, tasks, sampling, authentication, OAuth" — are generic MCP vocabulary that could also fire for users asking about MCP generally or with a non-Ax MCP skill.

4 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

ax-llm/ax

Path

website/static/typescript/.well-known/agent-skills/ax-mcp/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.