Name: fp-ts-errors
Rating: 60.8 (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

72%

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/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

71%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 thorough, highly actionable fp-ts error-handling tutorial with excellent executable examples and clear sequencing. Its main weaknesses are token verbosity and a monolithic structure with no progressive disclosure to reference files.

Suggestions

Trim conversational commentary and redundant 'Before' try/catch blocks (which are long and illustrative only) to reduce padding and lift conciseness toward 4.

Split the bulkier material (detailed real-scenario examples, full Quick Reference) into referenced files under references/ with one-level-deep links from the overview to improve progressive_disclosure.

Dimension	Reasoning	Score
Conciseness	Content is mostly practical but runs ~850 lines with conversational padding ('Might explode!', 'Who knows!', 'No academic jargon') and explanatory asides that could be trimmed, fitting anchor 3 rather than 4.	3 / 5
Actionability	Abundant copy-paste-ready, executable TypeScript covering the common cases (Either, chain, validation accumulation, TaskEither, retry, boundary conversions, scenarios) with a Quick Reference table, matching anchor 5.	5 / 5
Workflow Clarity	Sections are clearly sequenced (problem → Either → chaining → accumulating errors → async → conversions → real scenarios → reference → summary); no validation checkpoints are needed for a non-destructive patterns skill, so it sits at anchor 4.	4 / 5
Progressive Disclosure	A single ~850-line monolith with no bundle files and no one-level-deep references; though well-organized with section headers, content that could live in separate reference files (Quick Reference, detailed scenarios) is inlined, matching anchor 3.	3 / 5
	Total	15 / 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.

The description is well-formed, answering both 'what' and 'when' with concrete, niche-specific trigger terms in third-person voice. It is slightly limited in action coverage and trigger breadth rather than being comprehensive.

Suggestions

Expand the 'what' to list a couple more concrete actions (e.g. 'chain fallible operations, accumulate validation errors, wrap async boundaries') to push specificity from 3 toward 4-5.

Broaden the 'Use when' clause with additional natural triggers (e.g. 'Use when replacing try/catch with Either, accumulating form validation errors, or chaining fallible async operations with TaskEither').

Dimension	Reasoning	Score
Specificity	Names the domain (fp-ts error handling) and 1-2 concrete constructs ('Either and TaskEither') with the action 'Handle errors as values', but does not comprehensively enumerate error-handling actions, fitting anchor 3 rather than 4.	3 / 5
Completeness	Clearly states what ('Handle errors as values using fp-ts Either and TaskEither...') and when ('Use when implementing error handling patterns with fp-ts'); the 'when' is explicit but somewhat narrow with a single trigger scenario, matching anchor 4.	4 / 5
Trigger Term Quality	Includes natural terms users would say — 'fp-ts', 'Either', 'TaskEither', 'error handling patterns', 'TypeScript', 'errors as values' — with good coverage; a few synonyms or variants are missing, so it sits at anchor 4 rather than 5.	4 / 5
Distinctiveness Conflict Risk	The fp-ts/Either/TaskEither niche is highly specific with distinct triggers and minimal overlap risk with other skills, matching anchor 5.	5 / 5
	Total	16 / 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/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.