Name: fp-ts-errors
Rating: 55.2 (1 reviews)
Author: administrakt0r

fp-ts-errors

Handle errors as values using fp-ts Either and TaskEither for cleaner, more predictable TypeScript code. Use when implementing error handling patterns with fp-ts.

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

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-ts-errors/SKILL.md

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

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 skill is highly actionable with well-chosen fp-ts examples and clear progressive concept-building, but it is verbose for a context-loaded document and keeps everything inline rather than splitting advanced material into reference files.

Suggestions

Trim the repeated 'Before/MESSY try/catch' blocks and redundant per-example import statements; assume Claude knows try/catch and show only the fp-ts solution.

Move the Real Scenarios examples and the Quick Reference table into separate reference files (e.g., references/examples.md, references/quick-reference.md) and link them from a concise overview to improve progressive disclosure.

Add an explicit validate/retry/verify checkpoint to the bulk and batch-operation examples so workflow clarity is not capped.

Dimension	Reasoning	Score
Conciseness	Mostly useful patterns but padded with repeated 'Before: MESSY try/catch' pedagogical blocks (re-explaining try/catch Claude already knows), a marketing-style intro, and import statements repeated in every example.	3 / 5
Actionability	Rich, concrete, copy-paste TypeScript covering fold/chain/tryCatch/sequenceS/TaskEither/retry and bulk operations, with minor gaps from `{ ... }` stubs and undefined `db`/`User` helpers in a few examples.	4 / 5
Workflow Clarity	Sections build progressively and are numbered, but the batch/bulk examples (bulkProcess, processAllCollectErrors) lack validation/verification feedback loops, which caps workflow clarity at 3 per the rubric.	3 / 5
Progressive Disclosure	Good section structure but the entire ~850-line skill is a monolithic inline file with no external references, and advanced examples plus the quick-reference table could be split into separate bundle files.	3 / 5
	Total	13 / 20 Passed

Description

70%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 specific, third-person, and clearly answers both what and when with a concrete 'Use when' trigger tied to fp-ts. It could enumerate more distinct actions and broaden trigger synonyms to reach the top anchor.

Dimension	Reasoning	Score
Specificity	Names the domain and concrete constructs (fp-ts Either/TaskEither, handle errors as values) but restates essentially one action ('implementing error handling patterns') rather than listing several distinct actions, matching the anchor for domain + 1-2 concrete actions.	3 / 5
Completeness	Explicitly answers both what ('Handle errors as values using fp-ts Either and TaskEither') and when ('Use when implementing error handling patterns with fp-ts'), but the trigger phrase is somewhat narrow rather than fully concrete.	4 / 5
Trigger Term Quality	Strong natural keywords ('error handling', 'fp-ts', 'TypeScript', 'Either', 'TaskEither') that users would say, with only a few natural synonyms missing (Result type, try/catch alternative).	4 / 5
Distinctiveness Conflict Risk	fp-ts Either/TaskEither is a clear niche with minimal conflict risk, with only minor overlap against general TypeScript error-handling skills.	4 / 5
	Total	15 / 20 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (858 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
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/fp-ts-errors/SKILL.md
Commit: 57c135b

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.