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

fp-react

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

Quality

74%

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

The canonical home for this skill is fp-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 rich, highly actionable catalog of executable fp-ts + React patterns with clear decision guidance. Its weaknesses are the absence of progressive disclosure (everything is inlined in one large file) and a few pedagogical asides that restate known concepts.

Suggestions

Split deep-dive material (e.g. full RemoteData implementation, Dependency Injection with ReaderTaskEither, React 19 patterns) into one-level-deep reference files under references/ and link to them from SKILL.md to improve progressive disclosure.

Trim teaching asides like 'Why RemoteData Beats Booleans' that restate concepts Claude already knows, keeping only the decision-relevant framing.

Add a brief 'Setup' note (install fp-ts and related libs) near the top so the executable examples are immediately runnable.

Dimension	Reasoning	Score
Conciseness	The body is dominated by executable code with only brief framing prose ('No jargon, just code that works', short section intros), so it is efficient with minor over-explanation (e.g. the 'Why RemoteData Beats Booleans' teaching aside) that could be trimmed; not a 5 because a few pedagogical passages restate concepts Claude already knows.	4 / 5
Actionability	Provides fully executable, copy-paste-ready TypeScript/React examples across the common cases (state with Option, form validation with Either, fetching with TaskEither, RemoteData, stable hooks, DI, React 19 hooks), matching the score-5 anchor.	5 / 5
Workflow Clarity	Patterns are clearly organized into numbered sections with 'Quick Reference' and 'When to Use What' decision tables giving explicit selection guidance; not a 5 because there are no explicit validation/feedback checkpoints, though none are required for these non-destructive patterns.	4 / 5
Progressive Disclosure	Sections are well-structured, but the entire ~780-line guide is inlined in a single SKILL.md with no references to separate files (no references/, scripts/, or assets/ exist), so content that could live one level deep (full RemoteData implementation, DI/ReaderTaskEither, React 19 specifics) is inline, fitting the score-3 anchor.	3 / 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 is specific and distinctive, clearly scoping a niche (fp-ts + React) with good trigger-term coverage. Its main weakness is the missing explicit 'Use when...' trigger clause, which caps completeness at 3.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when building React apps with fp-ts for state, forms, or async data, or when the user mentions fp-ts, Option/Either/TaskEither, or RemoteData in a React context.'

Consider naming the concrete fp-ts constructs users would naturally say (Option, Either, TaskEither, RemoteData, pipe) to broaden trigger-term coverage toward the comprehensive anchor.

Reframe using third-person action verbs (e.g. 'Provides practical patterns...') to keep voice consistent, though the current phrasing is already largely descriptive.

Dimension	Reasoning	Score
Specificity	Names the domain ('using fp-ts with React') and lists several concrete pattern areas — 'hooks, state, forms, data fetching' — which is multiple specific actions with minor coverage gaps, matching the score-4 anchor; not a 5 because these are categories rather than fully enumerated concrete actions.	4 / 5
Completeness	Has a clear 'what' ('Practical patterns for using fp-ts with React - hooks, state, forms, data fetching') but no explicit 'when' / 'Use when...' trigger clause, so per the rubric cap completeness is held at 3; it is not a 4 because the 'when' is entirely absent rather than merely weak.	3 / 5
Trigger Term Quality	Includes natural terms users would say ('hooks', 'state', 'forms', 'data fetching', 'React', 'Next.js', 'fp-ts') with good coverage, but is missing some common synonyms/variations a user might utter, fitting the score-4 anchor rather than the comprehensive score-5 anchor.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche ('fp-ts with React', 'React 18/19, Next.js 14/15') with distinct triggers and minimal overlap risk with other skills, matching the score-5 anchor.	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 (793 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-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.