CtrlK
BlogDocsLog inGet started
Tessl Logo

e2e

Write, run, review, and debug end-to-end tests for rtp2httpd. ALWAYS use this skill when the user: (1) wants to write or optimize e2e/integration tests, (2) asks to run tests or mentions run-e2e.sh, uv, pytest, collect-only, xdist, markers, fixtures, or parallelism, (3) needs to debug failing, flaky, slow, or hanging e2e tests, (4) mentions any file under e2e/ or scripts/run-e2e.sh, (5) mentions MockRTSP*, MockHTTP*, MockFCC*, MockSTUN*, R2HProcess, MulticastSender, helper APIs, or test fixtures, (6) asks about multicast, RTSP, HTTP proxy, FCC, STUN, M3U, EPG, URL template, or zerocopy test coverage in rtp2httpd, or (7) uses Chinese phrases such as "端到端测试", "跑测试", or "e2e 测试" in this repo.

77

Quality

96%

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

92%

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

The body is lean, highly actionable, and clearly sequenced with validation checkpoints, reflecting strong token efficiency and workflow clarity. Its one weakness is progressive disclosure: the helper API catalog and layout are inline in SKILL.md rather than split into a one-level-deep reference file.

Suggestions

Move the full helper API signature catalog (port/process, config, HTTP, mock server listings) into a references/ file (e.g. references/helpers.md) and link to it from a short summary in SKILL.md, keeping only the most-used helpers inline.

Consider extracting the e2e/ directory layout block into references/layout.md or condensing it to the essential entries, leaving SKILL.md as a concise overview that points one level deep.

Add clearly signaled one-level-deep references (e.g. "**Helper API**: See [references/helpers.md](references/helpers.md)") so the overview points to detailed materials rather than inlining them.

DimensionReasoningScore

Conciseness

The body assumes Claude's competence (no explanation of what pytest/xdist are) and confines itself to repo-specific, actionable reference, with every section earning its tokens; there is no padded explanation of known concepts.

3 / 3

Actionability

It provides fully executable commands (./scripts/run-e2e.sh variants, cmake build, ruff) and copy-paste-ready code patterns with complete helper signatures and default args, matching the score-3 anchor.

3 / 3

Workflow Clarity

Multi-step flows are clearly sequenced with explicit validation checkpoints — the numbered Debugging Checklist (reproduce → confirm binary/collection → check causes) and the "Validation Before Finishing" section provide feedback loops for error recovery.

3 / 3

Progressive Disclosure

Sections are well-organized, but at ~270 lines with a large inline helper-API signature catalog that could live in a separate reference file and no one-level-deep external references, it matches the score-2 anchor of content that should be separate being inline.

2 / 3

Total

11

/

12

Passed

Description

100%

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

The description is specific, comprehensive, and well-triggered, clearly stating both capabilities and precise use conditions with third-person voice and no fluff. It is an exemplar of the score-3 anchors across all dimensions.

DimensionReasoningScore

Specificity

"Write, run, review, and debug end-to-end tests" lists multiple specific concrete actions rather than vague language, matching the score-3 anchor.

3 / 3

Completeness

It explicitly answers both what (write/run/review/debug e2e tests for rtp2httpd) and when ("ALWAYS use this skill when the user:" with enumerated triggers), satisfying the score-3 anchor.

3 / 3

Trigger Term Quality

Covers natural user terms broadly — run-e2e.sh, uv, pytest, collect-only, xdist, markers, fixtures, mock helper names, file paths, and Chinese phrases — giving good coverage of what a user would actually say.

3 / 3

Distinctiveness Conflict Risk

Tightly scoped to rtp2httpd e2e testing with repo-specific triggers (MockRTSP*, R2HProcess, MulticastSender, e2e/ paths), making it clearly distinguishable and unlikely to fire for the wrong skill.

3 / 3

Total

12

/

12

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
stackia/rtp2httpd
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.