Name: fp-ts-react
Rating: 64 (1 reviews)
Author: administrakt0r

fp-ts-react

Practical patterns for using fp-ts with React - hooks, state, forms, data fetching. Use when building React apps with functional programming patterns. Works with React 18/19, Next.js 14/15.

Quality

76%

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

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

Quality

Content

78%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 content is a strong, code-dense pattern catalog with high actionability and efficient prose. Its weakness is progressive disclosure: everything lives inline in one long file with no references to split the load, and a few chatty titles/comments could be trimmed.

Suggestions

Split the larger pattern sections (e.g. RemoteData, Dependency Injection, React 19 patterns) into reference files linked from a concise overview in SKILL.md to reduce inline bulk.

Tighten chatty section titles ('Maybe It's There, Maybe Not', 'The Right Way to Handle Async State') and remove obvious inline comments that restate the code.

Add a brief 'Getting started' or prerequisites note (install fp-ts) at the top so the first examples are immediately runnable.

Dimension	Reasoning	Score
Conciseness	The body is mostly executable code with tight, useful prose ('Either is perfect for validation: Left = errors, Right = valid data'); not a 5 because of chatty section titles ('Maybe It's There, Maybe Not') and minor hand-holding comments ('Option says this might not exist yet').	4 / 5
Actionability	Numerous complete, copy-paste-ready TypeScript examples (hooks, validation applicatives, RemoteData type + fold, useActionState/useOptimistic) cover the common cases with executable code, matching the top anchor.	5 / 5
Workflow Clarity	A pattern catalog with clear navigation (Quick Reference table, numbered sections 1-8, 'When to Use What' table) makes pattern selection unambiguous; not a 5 because there are no explicit multi-step validation checkpoints, though none are required since no destructive/batch operations are involved.	4 / 5
Progressive Disclosure	Section structure is good, but ~790 lines of patterns are inlined entirely in SKILL.md with no bundle/reference files and no one-level-deep references, fitting the 'content that should be separate is inline' anchor; the under-50-line exception does not apply.	3 / 5
	Total	16 / 20 Passed

Description

75%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 concise and covers both what the skill does and when to use it, with concrete sub-areas and version scope. Its main weakness is that the trigger guidance describes the task context rather than explicit user-cue phrases, keeping it just short of the top anchor.

Suggestions

Add explicit user-cue triggers to the 'when' clause, e.g. 'Use when the user mentions fp-ts, Option/Either/TaskEither, or wants type-safe state management in React'.

Reframe the capability list as concrete actions (e.g. 'model optional values, validate forms with error accumulation, fetch data with TaskEither') rather than bare nouns.

Include common synonyms/aliases (e.g. 'Maybe', 'Result', 'monadic error handling') to broaden natural trigger matching.

Dimension	Reasoning	Score
Specificity	Names the domain ('fp-ts with React') and several concrete sub-areas ('hooks, state, forms, data fetching'), matching the 'lists several specific actions; minor gaps' anchor; not a 5 because areas are framed as nouns rather than fully enumerated concrete actions.	4 / 5
Completeness	Has both a 'what' ('Practical patterns for using fp-ts with React - hooks, state, forms, data fetching') and an explicit 'Use when...' clause; not a 5 because the 'when' references the builder's task rather than explicit user-cue triggers ('when the user mentions...').	4 / 5
Trigger Term Quality	Good natural-term coverage ('React apps', 'functional programming patterns', 'hooks', 'forms', 'data fetching', 'React 18/19', 'Next.js 14/15'); not a 5 because it misses common synonyms/variations a user might say.	4 / 5
Distinctiveness Conflict Risk	'fp-ts with React' is a clear, fairly distinct niche with specific library and version cues; not a 5 because 'building React apps with functional programming patterns' is broad enough to overlap with general React or other FP-in-React skills.	4 / 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 (798 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-react/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.