CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

example-datasets

Load built-in CausalPy example datasets for demos, tutorials, tests, and quick causal-analysis prototypes. Use when the user needs sample data or asks which demo datasets are available.

Quality

91%

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

100%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 an exemplary lean reference skill: a minimal executable example followed by a complete, well-structured table of dataset keys and a short routing section. Nothing is padded, nothing is missing for the skill's single purpose.

DimensionReasoningScore

Conciseness

The body is lean and every token earns its place: a one-sentence intro, a two-line code snippet, a dense table where each row conveys key, use, and description, and three short guidance bullets. There is no explanation of concepts Claude already knows.

5 / 5

Actionability

The usage snippet ('import causalpy as cp; df = cp.load_data("did")') is copy-paste ready, and the table enumerates every dataset key with its typical use, fully covering the common cases.

5 / 5

Workflow Clarity

This is a simple single-purpose skill under 50 lines, and the single action (load a dataset by key via cp.load_data) is unambiguous, which per the simple-skill exception warrants a 5. No destructive or batch operations exist that would require validation checkpoints.

5 / 5

Progressive Disclosure

Per the rubric's simple-skill guidance, a skill under 50 lines with no need for external references scores 5 with well-organized sections alone. The Usage, Available Datasets, and Guidance sections are clearly headed, no bundle files exist to reference, and pointers to sibling skills ('choosing-causalpy-methods', 'running-causalpy-experiments') are clearly signaled one level deep.

5 / 5

Total

20

/

20

Passed

Description

78%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 what-plus-when structure and natural trigger phrases. Its main limitation is that it rests on a single concrete action, and its triggers rely on somewhat generic phrasing around 'sample data' that could overlap with other data skills.

Suggestions

Name one or two more concrete capabilities (e.g., listing available dataset keys or showing how to load them with cp.load_data) to raise specificity.

Broaden trigger coverage with synonyms users commonly say, such as 'toy data', 'example data', or 'built-in datasets'.

Tighten the trigger so it is unmistakably CausalPy-scoped, e.g. 'Use when the user needs sample data for CausalPy demos, tutorials, or tests.'

DimensionReasoningScore

Specificity

The description names the domain ('built-in CausalPy example datasets') and one concrete action ('Load...') with use contexts, but does not list several distinct concrete actions, matching the '1-2 concrete actions' anchor rather than the 'several specific actions' anchor above.

3 / 5

Completeness

It explicitly answers what it does ('Load built-in CausalPy example datasets for demos, tutorials, tests, and quick causal-analysis prototypes') and when to use it ('Use when the user needs sample data or asks which demo datasets are available'), with concrete trigger phrases matching the anchor-5 example pattern.

5 / 5

Trigger Term Quality

Natural phrases users would say are present ('sample data', 'demo datasets', 'example datasets', 'demos, tutorials, tests'), giving good coverage. It falls short of anchor 5 because common synonyms like 'toy data' or 'test data' as explicit triggers are missing.

4 / 5

Distinctiveness Conflict Risk

'CausalPy example datasets' establishes a clear niche with distinct triggers, but the standalone phrase 'needs sample data' is somewhat broad and could overlap with general data-loading or dataset-fetching skills, indicating minor overlap risk rather than minimal.

4 / 5

Total

16

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

pymc-labs/CausalPy

Path

causalpy/skills/example-datasets/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.