CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

haskell-pro

Expert Haskell engineer specializing in advanced type systems, pure functional design, and high-reliability software. Use for type-level programming, concurrency, and architecture guidance.

Quality

71%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/haskell-pro/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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 persona definition for a self-contained skill, scoring top marks on structure. Its guidance stays at the level of principles and technique names without concrete examples, executable patterns, or validation checkpoints, which caps actionability and workflow clarity at the midpoint.

Suggestions

Cut the boilerplate 'Use this skill when' / 'Do not use this skill when' / 'Instructions' sections whose content is circular or generic ('haskell pro tasks', 'Clarify goals, constraints, and required inputs') to tighten token efficiency.

Add one short runnable example per key output type (e.g., a newtype-with-invariant model, an STM transaction, a Megaparsec parser) so the Output section demonstrates the expected style instead of only naming it.

Turn the Approach principles into a sequenced workflow with a verification step, e.g. 'After proposing code, confirm it compiles in GHCi and note any required language extensions'.

DimensionReasoningScore

Conciseness

The core content (Focus Areas, Approach, Output) is efficient with no concept-teaching padding, but the boilerplate sections are unnecessary: 'Working on haskell pro tasks or workflows' is circular, and 'Clarify goals, constraints, and required inputs' / 'Apply relevant best practices and validate outcomes' are generic template filler Claude does not need. This is more than the 'minor instances' of anchor 4, so 3 fits.

3 / 5

Actionability

Guidance names concrete techniques and libraries ('STM, async, and lightweight threads', 'Aeson, Megaparsec', 'QuickCheck/Hspec tests', 'Recommend safe, total alternatives to partial functions'), which exceeds minimal hints, but there are no examples, patterns, or specific procedures — the Approach and Output sections describe rather than instruct. As an instruction-only skill this lands at anchor 3's 'some concrete guidance but incomplete'.

3 / 5

Workflow Clarity

The Approach section lists numbered steps ('1. Use expressive types... 7. Provide examples runnable in GHCi'), but these are parallel design principles rather than a sequenced process, and no validation checkpoints or feedback loops exist anywhere in the body. This matches anchor 3's 'steps listed but validation gaps' rather than anchor 4's clear sequence with checkpoints.

3 / 5

Progressive Disclosure

The body is 46 lines (under 50), entirely self-contained with no bundle files to reference, and organized into clear, well-labeled sections (Use when / Do not use / Instructions / Focus Areas / Approach / Output). Per the rubric's simple-skill rule, this earns the top score with just well-organized sections.

5 / 5

Total

14

/

20

Passed

Description

73%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 solid third-person description that explicitly covers both what the skill does and when to use it, with good natural trigger terms and a clearly distinct Haskell niche. Its main weakness is that it enumerates specialty areas rather than concrete actions, leaving specificity below the top anchors.

Suggestions

Replace specialty-area phrasing with concrete actions, e.g. 'Writes and reviews Haskell code, designs GADT/type-family models, tunes performance, and fixes Cabal/Stack builds'.

Add commonly mentioned user terms and synonyms to the trigger clause, such as GHC, Cabal, Stack, .hs, QuickCheck, or 'when the user mentions Haskell code, type errors, or builds'.

DimensionReasoningScore

Specificity

The description names the domain ('Expert Haskell engineer specializing in advanced type systems, pure functional design, and high-reliability software') and lists capability topics ('type-level programming, concurrency, and architecture guidance'), but these are specialty areas rather than the concrete performable actions the 4-5 anchors require. It exceeds anchor 2's bare domain-naming, so 3 fits best.

3 / 5

Completeness

Both parts are explicitly present: the 'what' ('Expert Haskell engineer specializing in...') and the 'when' ('Use for type-level programming, concurrency, and architecture guidance'). The 'when' clause is explicit but less concrete than anchor 5's 'when the user mentions...' trigger phrasing, so it sits at anchor 4.

4 / 5

Trigger Term Quality

Natural terms users would say are present: 'Haskell', 'type-level programming', 'concurrency', 'architecture guidance'. Common variations a user would naturally mention (GHC, Cabal, Stack, .hs) are missing, which keeps it below anchor 5 but above anchor 3's 'missing common variations' since primary natural coverage is good.

4 / 5

Distinctiveness Conflict Risk

'Haskell' combined with 'advanced type systems' and 'type-level programming' defines a clear niche with distinct triggers and minimal conflict risk against generic programming skills. It matches anchor 5's 'clear niche with distinct triggers'.

5 / 5

Total

16

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

rmyndharis/antigravity-skills

Path

skills/haskell-pro/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.