CtrlK
BlogDocsLog inGet started
Tessl Logo

explore-feature

Use when a developer wants a release-gate test for a change before merge — e.g. "explore this feature", "add a release-gate test for my PR", "gate this branch", "cover the feature in PR

75

Quality

92%

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

85%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.

The body is highly actionable with executable commands and a clearly sequenced, validated five-phase workflow, but it is a long monolithic file that inlines detail (worktree gotcha, skip-check cases) that would benefit from being split into bundled reference files. Progressive disclosure is the weakest dimension because no bundle files accompany the referenced templates and contracts.

Suggestions

Move the Phase 3 'Worktree gotcha' and Phase 1 skip-check case taxonomy into bundled reference files under ./references/ (e.g. local-stack-recipes.md, skip-check-guide.md) and link to them one level deep, so SKILL.md stays a lean overview.

Add the referenced test-plan-template.md and release-gate-contract.md to a ./references/ or ./assets/ bundle so the 'read it' / 'pass it verbatim' pointers resolve to real files.

Tighten the Phase 1 skip-check paragraph: collapse the nested (a)/(b) sub-cases into a short decision table or a bulleted skip-vs-gate rule to reduce token cost without losing the gating logic.

DimensionReasoningScore

Conciseness

Mostly efficient and assumes Claude's competence with domain-specific operational detail (worktree port-offset gotcha, /api/is-alive/ver health signal), but the Phase 1 skip-check block runs long with nested cases that could be trimmed or split out. Not a 5 because some dense passages could be tightened without losing clarity.

4 / 5

Actionability

Fully executable, copy-paste-ready guidance throughout: git merge-base/diff commands, 'git show origin/main:version.txt', curl health check, docker socat bridge command, npm run start with pinned ports, and 'python3 tests_end_to_end/coverage/tag_lint.py …' — covering the common cases concretely.

5 / 5

Workflow Clarity

Five phases are clearly sequenced with explicit gated checkpoints (Scope gate, Skip check, Local-run gate) and validation/feedback loops ('tag_lint.py reports 0 problem(s)', 'runs green locally', re-validate on failure), matching the anchor for clear sequence with explicit validation and error recovery.

5 / 5

Progressive Disclosure

Has clear section structure and one-level references to test-plan-template.md and release-gate-contract.md ('read it', 'pass it verbatim'), but no bundle files exist so those references are unverified, and substantial operational detail (worktree gotcha, skip-check taxonomy) is inlined in a 230-line monolith rather than split into separate files. Not a 4 because content that clearly belongs in separate files is inlined and references aren't backed by a bundle.

3 / 5

Total

17

/

20

Passed

Description

100%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.

The description is excellent: it states explicit 'Use when' trigger guidance with multiple natural phrases, names several concrete actions, and carves out a distinct niche with a clear delegation boundary. It answers both what and when concisely without padding.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Reads a ticket + changed code', 'writes a happy-path test-plan.md (posted to Jira)', 'commits one staging-ready @release-gate Playwright test', 'Delegates the actual test authoring to writing-e2e-tests' — with comprehensive coverage of what the skill does.

5 / 5

Completeness

Explicitly answers both what (reads ticket+code, writes plan to Jira, commits @release-gate Playwright test, delegates authoring) and when ('Use when a developer wants a release-gate test for a change before merge') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural trigger phrases including synonyms and concrete variants: 'explore this feature', 'add a release-gate test for my PR', 'gate this branch', 'cover the feature in PR #7303', 'release-gate test for these tickets'.

5 / 5

Distinctiveness Conflict Risk

Clear niche (release-gate test gating a change's own release) with distinct triggers and an explicit delegation boundary to writing-e2e-tests, minimizing overlap risk with adjacent skills.

5 / 5

Total

20

/

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
comet-ml/opik
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.