CtrlK
BlogDocsLog inGet started
Tessl Logo

agent-host-e2e-tests

Use when writing, recording, updating, or troubleshooting the agent host end-to-end tests under src/vs/platform/agentHost/test/node/e2e (black-box tests that drive the whole agent host over the AHP protocol, using a CapiReplayProxy record/replay system for Claude/Copilot/Codex). Covers adding a cross-provider test, re-recording fixtures after an SDK bump, gating non-deterministic or platform-specific tests, and diagnosing replay cache misses.

71

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

81%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 well-structured, action-oriented skill body with clearly sequenced workflows, strong validation/feedback loops, and appropriate deferral to a README for deeper detail. It is dense and executable, with only minor conciseness and reference-formatting gaps.

DimensionReasoningScore

Conciseness

Dense and information-rich, assuming Claude's competence (AHP, CapiReplayProxy, hostOnlyTest, dispatchTurn) with no padding; the long Copilot runtime-log paragraph and a few compound sentences could be tightened, keeping it just below a 5.

4 / 5

Actionability

Provides copy-paste-ready shell commands (AGENT_HOST_REPLAY_RECORD=1 ./scripts/test-integration.sh --run …, gh auth token, --grep) and concrete file paths, but in-test API usage is illustrative with (...) placeholders rather than complete copy-paste code, leaving minor gaps.

4 / 5

Workflow Clarity

Three numbered workflows (A/B/C) with explicit validation checkpoints ('Review git diff', 'run plain replay to confirm green, then commit'), feedback loops (leaked PII → extend normalization in capiReplayProxy.ts → re-record), a non-negotiable rules checklist, and a symptom→cause→fix troubleshooting table.

5 / 5

Progressive Disclosure

Clean overview/workflows split with the README explicitly designated as the source of truth and one-level-deep references to README.md, KNOWN_ISSUES.md, capiReplayProxy.ts, and capiStubs.ts; references are inline path strings rather than a consolidated, clearly-formatted link map, a minor organization gap.

4 / 5

Total

17

/

20

Passed

Description

92%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 highly specific, well-triggered description that cleanly answers both what the skill does and when to use it, with concrete action verbs and a distinct niche. The only minor gap is missing synonyms/file extensions in the trigger terms.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'writing, recording, updating, or troubleshooting', 'adding a cross-provider test', 're-recording fixtures after an SDK bump', 'gating non-deterministic or platform-specific tests', and 'diagnosing replay cache misses' — giving comprehensive coverage of what the skill handles.

5 / 5

Completeness

Explicitly answers both: the 'when' via the leading 'Use when writing, recording, updating, or troubleshooting...' and the 'what' via 'Covers adding a cross-provider test, re-recording fixtures... diagnosing replay cache misses.'

5 / 5

Trigger Term Quality

Strong natural phrases a user would say ('re-record fixtures after an SDK bump', 'replay cache misses', 'cross-provider test') plus provider names, but lacks synonyms and file extensions expected for a 5.

4 / 5

Distinctiveness Conflict Risk

A narrow, well-scoped niche (agent host e2e tests under a specific path, AHP protocol, CapiReplayProxy for Claude/Copilot/Codex) with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
posit-dev/positron
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.