CtrlK
BlogDocsLog inGet started
Tessl Logo

fp-errors

Stop throwing everywhere - handle errors as values using Either and TaskEither for cleaner, more predictable code

48

Quality

53%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/fp-errors/SKILL.md

The canonical home for this skill is fp-errors in administrakt0r/AI-Agents-Safe-Coding-Skills

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.

This is a thorough, highly actionable fp-ts error-handling reference with strong executable examples, but it is verbose and monolithic. Splitting deep material into reference files and trimming the before/bad-code padding would meaningfully improve conciseness and progressive disclosure.

Suggestions

Move the detailed sections (validation accumulation, TaskEither deep-dive, Real Scenarios) into reference files and keep SKILL.md as a concise overview with one-level-deep links.

Trim the 'Before: MESSY' try/catch examples to short snippets or inline comments; the contrast rarely needs full blocks.

Add explicit validation/verification checkpoints to the bulk-operation and retry workflows (e.g., assert partial-success counts, validate before commit) to raise workflow clarity.

DimensionReasoningScore

Conciseness

The body is mostly concrete code, but repeated 'Before: MESSY' bad-code blocks and pedagogical asides (e.g., 'think right as correct') add padding that could be trimmed without losing value.

3 / 5

Actionability

Abundant executable fp-ts code (tryCatch, validation applicative, TaskEither chaining, retry with backoff, API error handling) covers common cases, with only minor gaps from illustrative `{ ... }` stubs.

4 / 5

Workflow Clarity

Concepts build in a clear numbered sequence (sections 1-6 then Real Scenarios), but the batch/bulk operation sections lack explicit validation checkpoints, which caps workflow clarity at 3.

3 / 5

Progressive Disclosure

Content is well-organized into labeled sections, but ~840 lines are fully inlined in SKILL.md with no separate reference files, so disclosure stays a single flat level rather than pointing one level deep.

3 / 5

Total

13

/

20

Passed

Description

48%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 conveys a clear fp-ts niche and concrete constructs, but uses second-person imperative voice and omits an explicit 'Use when...' trigger clause, capping completeness and specificity. Adding third-person voice and a trigger clause would lift it materially.

Suggestions

Rewrite in third person (e.g., 'Handles errors as values using Either and TaskEither...') instead of the imperative 'Stop throwing everywhere'.

Add an explicit trigger clause such as 'Use when refactoring try/catch code or adopting fp-ts error handling in TypeScript.'

Include a couple of natural user phrasings (e.g., 'try/catch', 'error handling', 'fp-ts') to broaden trigger coverage.

DimensionReasoningScore

Specificity

Names the error-handling domain with concrete constructs ('Either and TaskEither'), but the description is written in second-person imperative voice ('Stop throwing', 'handle errors as values'), which the voice guideline penalizes by reducing specificity by one.

2 / 5

Completeness

There is a clear 'what' (handle errors as values using Either/TaskEither for cleaner code), but no explicit 'Use when...' trigger clause, which caps completeness at 3 per the guideline.

3 / 5

Trigger Term Quality

Relevant terms appear ('throwing', 'errors as values', 'Either', 'TaskEither'), but common natural phrasings or synonyms a user would actually say are missing, so coverage is partial rather than comprehensive.

3 / 5

Distinctiveness Conflict Risk

'Either', 'TaskEither', and 'errors as values' carve a clear fp-ts niche with only minor overlap risk against general error-handling skills.

4 / 5

Total

12

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (860 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.