CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

climate-indices-conventions

Repository conventions for the climate_indices Python scientific-computing library — enforces coding style, module boundaries, test placement, and Conventional Commit format. Use when changing climate_indices, writing its tests or docs, preparing commits, or running ruff/mypy validation and pytest tests.

Quality

90%

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

82%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-organized, highly actionable conventions document: exact commands, paths, and examples throughout, with a sequenced workflow ending in validation. Minor room to improve by tightening the commit-type and naming lists and adding a brief fix-and-revalidate loop.

Suggestions

Collapse the nine-line commit-type bullet list into a single line (e.g., "Types: feat, fix, docs, test, refactor, chore, ci, build, style") and trim the basic naming-convention table to reclaim tokens.

Add a short error-recovery step to the Feature Workflow, e.g., "If validation fails, fix the reported issues and re-run until clean before review."

Remove the opening 'Use this skill when...' sentence, which duplicates the frontmatter description verbatim in intent.

DimensionReasoningScore

Conciseness

Efficient tables and commands that assume Claude's competence, but with minor trims available: the 9-item commit-type bullet list could be one line, the naming table restates basic Python conventions, and the opening 'Use this skill when...' sentence duplicates the frontmatter description.

4 / 5

Actionability

Fully executable guidance: copy-paste validation commands ('uv run ruff check src/ tests/', 'uv run pytest'), exact file paths (tests/test_<subject>.py, src/climate_indices/__init__.py), and concrete import and commit-message examples cover the common cases.

5 / 5

Workflow Clarity

The Feature Workflow gives a clear 5-step sequence with an explicit final validation checkpoint ("Run the relevant validation commands before review"), but lacks an error-recovery feedback loop for when validation fails.

4 / 5

Progressive Disclosure

Well-sectioned headers with one-level navigation and a clearly signaled pointer to src/climate_indices/CONTEXT.md, but with no bundle files and ~117 lines of inline detail (commit-type list, style tables) that a reference file could offload.

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 strong description: third-person, concise, names the domain and concrete enforced areas, and closes with an explicit multi-activity 'Use when' clause. The only gap is a few natural trigger terms (e.g., refactoring, release/CI changes) that the body covers but the description does not.

DimensionReasoningScore

Specificity

"enforces coding style, module boundaries, test placement, and Conventional Commit format" and "running ruff/mypy validation and pytest tests" list multiple specific concrete actions with named tools, comprehensively covering the skill's scope.

5 / 5

Completeness

Explicitly answers both "what" (conventions enforcing coding style, module boundaries, test placement, commit format) and "when" with concrete enumerated trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

"Use when changing climate_indices, writing its tests or docs, preparing commits, or running ruff/mypy validation and pytest tests" provides good natural-keyword coverage, but a few natural terms (refactoring, releases/CI/workflow changes — covered by the body) are missing.

4 / 5

Distinctiveness Conflict Risk

Anchored to the named "climate_indices Python scientific-computing library", giving a clear niche with distinct triggers and minimal conflict risk with generic Python style 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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

monocongo/climate_indices

Path

.agents/skills/climate_indices/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.