Name: fp-ts-pragmatic
Rating: 60.8 (1 reviews)
Author: administrakt0r

fp-ts-pragmatic

A practical, jargon-free guide to fp-ts functional programming - the 80/20 approach that gets results without the academic overhead. Use when writing TypeScript with fp-ts library.

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-claude/skills/fp-ts-pragmatic/SKILL.md

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

Quality

Content

75%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 highly actionable, full of executable before/after TypeScript examples and a useful cheat sheet, with clear sectioning. It leans long and could trim promotional prose and split advanced content into reference files.

Dimension	Reasoning	Score
Conciseness	The ~600-line body is mostly dense, executable before/after examples and avoids explaining basics Claude knows, but it carries promotional padding ('No category theory. No abstract nonsense.', 'FP is a tool, not a religion.') and repeated 'don't force FP' framing that could be trimmed.	3 / 5
Actionability	Provides copy-paste-ready, fully executable TypeScript across all five core patterns (pipe, Option, Either, map, flatMap) plus TaskEither, with imports and a cheat sheet mapping intent to fp-ts calls covering common cases.	5 / 5
Workflow Clarity	As a pattern reference rather than a destructive multi-step workflow it has no validation checkpoints, but sections are logically organized (When to use, patterns, when not to, refactors, cheat sheet); the structure is clear with only minor sequencing gaps.	4 / 5
Progressive Disclosure	It is a single well-sectioned file with clear headers and easy navigation, but at ~600 lines with no external references, content like the advanced 'When to Level Up' and lengthy refactor catalogs could be split into one-level-deep reference files.	4 / 5
	Total	16 / 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 clearly states what the skill is and when to use it, with reasonably natural trigger terms anchored to the fp-ts library. Its main weakness is specificity — the framing is promotional ('80/20 approach', 'gets results') rather than naming concrete capabilities.

Suggestions

Replace the promotional framing with concrete capabilities, e.g. 'Chain operations with pipe, handle nullables with Option, and model errors with Either using fp-ts'.

Expand the 'when' clause with concrete trigger phrases users would say, such as 'Use when refactoring imperative TypeScript to fp-ts, handling nullable chains, or modeling fallible operations'.

Add fp-ts-specific synonyms (Option, Either, TaskEither, pipe) to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the fp-ts domain and frames a couple of actions ('guide to fp-ts functional programming', '80/20 approach that gets results'), but no concrete FP operations (pipe/Option/Either) are named, so it matches '1-2 concrete actions, not comprehensive'.	3 / 5
Completeness	Explicitly answers both what ('a practical, jargon-free guide to fp-ts functional programming') and when ('Use when writing TypeScript with fp-ts library'), but the 'when' clause is a single, somewhat generic trigger rather than concrete trigger phrases.	4 / 5
Trigger Term Quality	Includes natural terms a user would say ('TypeScript', 'fp-ts', 'functional programming') but misses common synonyms/operations like Option, Either, or error handling, so coverage is good but not comprehensive.	4 / 5
Distinctiveness Conflict Risk	The fp-ts library trigger carves a fairly specific niche with low conflict risk against unrelated skills, though 'functional programming' + 'TypeScript' leaves minor overlap with general FP/TS 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 (600 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-pragmatic/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.