CtrlK
BlogDocsLog inGet started
Tessl Logo

fp-react

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

56

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

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

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

SKILL.md
Quality
Evals
Security

Quality

Content

63%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 highly actionable, well-organized catalog of fp-ts/React patterns with strong executable examples and clear decision tables. It is held back by some over-explanation of known concepts and a monolithic structure with no progressive disclosure into separate reference files.

Suggestions

Move detailed pattern sections (RemoteData, Dependency Injection, React 19) into reference files and keep SKILL.md as a concise overview with one-level-deep links.

Trim conceptual BAD/GOOD explanations of ideas Claude already knows (referential equality, impossible states) and keep only the code that demonstrates the pattern.

Define or stub the referenced helpers (submitToServer, saveTodo, Spinner, ErrorMessage) so examples are fully copy-paste runnable.

DimensionReasoningScore

Conciseness

The body is mostly executable code with brief framing, but sections like "Why RemoteData Beats Booleans" and the BAD/GOOD re-render comparisons explain concepts Claude already knows (state machines, referential equality), fitting the "mostly efficient but could be tightened" anchor.

3 / 5

Actionability

Abundant complete, copy-paste TypeScript examples with imports across all major patterns; minor gaps from undefined helpers (submitToServer, saveTodo, Spinner, ErrorMessage) keep it just below fully executable.

4 / 5

Workflow Clarity

A well-organized pattern catalog sequenced basics-to-advanced with a Quick Reference table and a "When to Use What" decision table providing clear selection guidance; no destructive/batch operations require validation checkpoints.

4 / 5

Progressive Disclosure

The skill is a ~780-line monolithic SKILL.md with no bundle files or external references; it is well-sectioned internally but content that could live in separate reference files (e.g. RemoteData, React 19 patterns) is fully inlined.

3 / 5

Total

14

/

20

Passed

Description

66%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 distinct, naming a clear niche and four capability areas with natural trigger terms. Its main weakness is the absence of an explicit "Use when..." trigger clause, which caps completeness.

Suggestions

Add an explicit "Use when..." clause, e.g. "Use when building React apps with fp-ts for state, forms, or async data fetching."

Include a few more natural trigger synonyms (e.g. "functional programming", "monadic state") to broaden keyword coverage.

Consider mentioning runtime validation libraries (io-ts/zod) in the description since they are covered in the body.

DimensionReasoningScore

Specificity

Names the domain (fp-ts with React) and lists four concrete capability areas — "hooks, state, forms, data fetching" — which matches the "lists several specific actions" anchor, though they are categories rather than the fully concrete actions a 5 requires.

4 / 5

Completeness

The "what" is clear (practical fp-ts patterns for React across four areas) but there is no "Use when..." clause or equivalent trigger guidance, so completeness is capped at 3 per the rubric.

3 / 5

Trigger Term Quality

Includes natural terms users would say (fp-ts, React, hooks, forms, data fetching) plus version synonyms (React 18/19, Next.js 14/15); a few natural variations like "functional programming" are missing, keeping it below 5.

4 / 5

Distinctiveness Conflict Risk

"fp-ts with React" is a distinct niche with version scoping; minor overlap risk with general React or TypeScript skills keeps it just below a 5.

4 / 5

Total

15

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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
Reviewed

Table of Contents

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.