CtrlK
BlogDocsLog inGet started
Tessl Logo

feature-exploration

Explore unfamiliar APIs, libraries, or implementation behavior with minimal reproducible examples and documented findings. Use when implementation details are unclear and can be resolved by reading docs, inspecting code, and running focused experiments.

68

Quality

83%

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

78%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 a lean, well-organized instruction skill with a clear sequenced workflow and an embedded experiment-iterate feedback loop. The main gaps are minor: a few verbose guardrails and the absence of an explicit validation checkpoint before applying the production change.

Suggestions

Add an explicit validation checkpoint before step 7, e.g. 'Only apply the production change once the minimal repro consistently confirms the expected behavior.'

Tighten the AGENTS.md guardrail by linking to the rule rather than enumerating CausalPy, PyMC, PyTensor, and matplotlib inline.

Provide a one-line repro template or naming convention for exploratory scripts so step 3 is copy-paste ready.

DimensionReasoningScore

Conciseness

The ~30-line body is lean and assumes Claude's competence with no concept-explanation padding, but a few guardrail lines (e.g. the AGENTS.md import list) could be trimmed, sitting just below the every-token-earns-its-place anchor.

4 / 5

Actionability

Concrete, specific guidance with named paths (`.scratch/`, `causalpy/tests/`, `AGENTS.md`) and named libraries, but a couple of steps ('Read the closest authoritative docs', 'Build the smallest reproducible example') stay high-level without a template or command, leaving minor gaps.

4 / 5

Workflow Clarity

Seven well-sequenced steps with a genuine iterate-until-understood feedback loop (steps 4-5), but there is no explicit re-validation checkpoint before the production change in step 7, leaving a minor validation gap below the full-checklist anchor.

4 / 5

Progressive Disclosure

A simple under-50-line skill with no external references and cleanly organized Workflow, Guardrails, and Output sections, meeting the simple-skill exception for full marks.

5 / 5

Total

17

/

20

Passed

Description

88%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 strong: third-person voice, explicit what-and-when with concrete trigger phrases, and several named concrete actions. Its main weakness is slightly broad trigger terms that could overlap with general exploration skills.

DimensionReasoningScore

Specificity

Names multiple concrete actions across the domain — 'Explore unfamiliar APIs, libraries, or implementation behavior with minimal reproducible examples and documented findings', plus 'reading docs, inspecting code, and running focused experiments' — matching the comprehensive-coverage anchor.

5 / 5

Completeness

Explicitly states both what ('Explore... with minimal reproducible examples and documented findings') and when ('Use when implementation details are unclear and can be resolved by reading docs, inspecting code, and running focused experiments'), with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural developer trigger phrases ('implementation details are unclear', 'reading docs', 'inspect code', 'running focused experiments', 'minimal reproducible examples'), but the domain ('APIs, libraries') is broad with no synonyms or file extensions, missing the fully comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

The feature-exploration / API-uncertainty niche is mostly distinct, but the broad framing around 'APIs, libraries, or implementation behavior' leaves minor overlap risk with general coding and exploration skills, falling just short of a clear-niche anchor.

4 / 5

Total

18

/

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
pymc-labs/CausalPy
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.