fp-types-ref

Quick reference for fp-ts types. Use when user asks which type to use, needs Option/Either/Task decision help, or wants fp-ts imports.

Quality

87%

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

92%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 lean, well-structured, and immediately useful. The decision tree for type selection is a particularly effective format that adds genuine value beyond what Claude would produce by default. The only minor weakness is a couple of undefined helpers (toError, default) in the examples that slightly reduce copy-paste readiness.

Dimension	Reasoning	Score
Conciseness	Every token earns its place. The decision tree, import block, pattern table, and match examples are all pure signal with zero unnecessary explanation. Claude already knows what fp-ts is; this skill correctly assumes that and provides only the decision-making and syntax reference.	5 / 5
Actionability	The imports, one-line patterns table, and pattern match examples are concrete and copy-paste ready. Minor gap: the table uses `default` (a reserved word) and `toError` without defining it, which slightly reduces immediate executability.	4 / 5
Workflow Clarity	This is a single-purpose reference/lookup skill, not a multi-step workflow. The decision tree provides an unambiguous sequence for type selection, and the content is clearly organized for quick consultation. No destructive or batch operations are involved.	5 / 5
Progressive Disclosure	For a concise reference skill under 50 lines with no need for external files, the content is well-structured with clear sections (decision tree → imports → patterns → matching). No bundle files are needed and none are referenced, which is appropriate.	5 / 5
	Total	19 / 20 Passed

Description

82%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.

This is a solid description that clearly communicates its niche (fp-ts type reference) and includes an explicit 'Use when' clause with concrete trigger scenarios. Its main weakness is that the 'what' portion is somewhat thin — 'quick reference' is vague about what specific guidance it provides — and it could include a few more trigger terms for common fp-ts types or concepts.

Suggestions

Expand the 'what' portion to be more specific about capabilities, e.g., 'Provides guidance on choosing between fp-ts types, explains type signatures, and shows correct import paths'

Add more fp-ts-specific trigger terms like 'TaskEither', 'IO', 'pipe', 'flow', or 'functional programming in TypeScript' to improve keyword coverage

Dimension	Reasoning	Score
Specificity	Names the domain (fp-ts types) and a couple of concrete actions (type decision help, imports), but doesn't comprehensively list what the skill actually does beyond being a 'quick reference'. Actions like 'decision help' and 'imports' are somewhat vague.	3 / 5
Completeness	Clearly answers both 'what' (quick reference for fp-ts types) and 'when' (explicit 'Use when' clause with three concrete trigger scenarios: asking which type to use, needing Option/Either/Task decision help, or wanting fp-ts imports).	5 / 5
Trigger Term Quality	Includes good natural trigger terms like 'fp-ts', 'Option', 'Either', 'Task', 'imports', and 'which type to use'. Missing some common variations like 'TaskEither', 'IO', 'functional programming', or 'pipe/flow' that users might naturally mention.	4 / 5
Distinctiveness Conflict Risk	Very distinct niche — fp-ts is a specific TypeScript functional programming library, and the description clearly scopes to type selection and imports within that library. Minimal risk of conflicting with other skills.	5 / 5
	Total	17 / 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-types-ref/SKILL.md
Commit: debb2ec

Reviewed: 14 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.