fp-taskeither-ref

Quick reference for TaskEither. Use when user needs async error handling, API calls, or Promise-based operations that can fail.

Quality

80%

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

Quality

Content

96%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 an excellent quick reference skill that is concise, actionable, and well-structured. It assumes Claude's competence, provides executable TypeScript examples covering all common use cases, and organizes content in a logical progression from basic operations to advanced patterns. The only minor improvement would be adding cross-references to related fp-ts concepts.

Dimension	Reasoning	Score
Conciseness	Every section is lean and purposeful. No unnecessary explanations of what TaskEither is beyond the one-line definition. The comparison section earns its place by showing a concrete anti-pattern. No padding or redundant commentary.	5 / 5
Actionability	All code examples are executable TypeScript with correct imports. Covers creation, transformation, execution, common patterns (fetch wrapping, chaining, parallel, recovery), and a concrete comparison. Copy-paste ready.	5 / 5
Workflow Clarity	This is a single-purpose quick reference skill, not a multi-step destructive workflow. The sections are logically sequenced (Create → Transform → Execute → Patterns → Comparison), which is the natural learning/usage flow. No validation steps are needed for a reference card.	5 / 5
Progressive Disclosure	Well-structured with clear section headers that progress from basic to advanced usage. No bundle files exist, and for a concise reference under 100 lines this is appropriate. Minor gap: could link to related references (e.g., Either, pipe) for discovery, but the content is well-organized as-is.	4 / 5
	Total	19 / 20 Passed

Description

65%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 has a solid 'Use when' clause with relevant trigger terms, making it functional for skill selection. However, it lacks specificity about what the skill actually provides—'quick reference' is vague and doesn't describe concrete actions like chaining operations, handling errors, or converting between types. Adding the library context (fp-ts) and specific capabilities would significantly improve it.

Suggestions

Add concrete actions the skill covers, e.g., 'Covers TaskEither creation, chaining with flatMap/chain, error recovery with fold, and conversion from Promise.'

Include the library name 'fp-ts' as a trigger term since users searching for TaskEither help will likely mention it.

Dimension	Reasoning	Score
Specificity	Names the domain (TaskEither, async error handling) but provides no concrete actions. It says 'quick reference' but doesn't describe what specific operations or capabilities the skill covers (e.g., chaining, error recovery, mapping).	2 / 5
Completeness	Has a weak 'what' ('Quick reference for TaskEither') and an explicit 'when' clause ('Use when user needs async error handling, API calls, or Promise-based operations that can fail'). The 'what' could be more specific about what the reference actually covers.	4 / 5
Trigger Term Quality	Includes several natural keywords users would say: 'TaskEither', 'async error handling', 'API calls', 'Promise-based operations'. Missing some synonyms like 'fp-ts', 'functional programming', 'Either', 'pipe', or 'error monad'.	4 / 5
Distinctiveness Conflict Risk	TaskEither is a fairly specific concept (fp-ts library), making it distinct from general error handling or async skills. However, 'API calls' and 'Promise-based operations' are broad enough to potentially overlap with general async/HTTP skills.	4 / 5
	Total	14 / 20 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/fp-taskeither-ref/SKILL.md
Commit: 731a928

Reviewed: 20 hours 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.