CtrlK
BlogDocsLog inGet started
Tessl Logo

fp-backend

Functional programming patterns for Node.js/Deno backend development using fp-ts, ReaderTaskEither, and functional dependency injection

51

Quality

57%

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

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

SKILL.md
Quality
Evals
Security

Quality

Content

53%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 skill is a rich, actionable fp-ts pattern library with strong code examples, but it is monolithic: all content is inlined in SKILL.md with no progressive disclosure, and destructive/database workflows lack explicit validation checkpoints. Tightening and splitting into reference files would substantially raise quality.

Suggestions

Split large topical sections into one-level-deep reference files (e.g. references/testing.md, references/error-handling.md, references/db.md) and link to them from a concise overview in SKILL.md.

Add explicit validation checkpoints to database/transaction workflows (e.g. verify rows exist before debit/credit, assert balance invariants, re-check after commit) to lift workflow_clarity above the destructive-operations cap.

Fix and complete the broken logWithContext snippet and any partial templates so all code blocks are genuinely copy-paste ready.

DimensionReasoningScore

Conciseness

The body is mostly efficient code with little basic-concept padding, but at ~1300 lines all inlined it is long and could be tightened; small explanatory passages like 'The ReaderTaskEither type is the backbone...' add modest overhead.

3 / 5

Actionability

Provides extensive concrete, executable TypeScript across services, DI, Prisma wrappers, transactions, middleware, error handling, and tests; a few snippets are incomplete or broken (e.g. the logWithContext body has a malformed call), preventing a 5.

4 / 5

Workflow Clarity

Patterns are well-organized by topic but there is no explicit multi-step workflow with validation checkpoints, and database/transaction operations lack validate-then-proceed feedback loops, which caps this at 3 per the rubric.

3 / 5

Progressive Disclosure

Everything lives in a single ~1300-line SKILL.md with no references/ or bundle files; large sections (testing, error handling, db, middleware) clearly belong in separate one-level-deep reference files but are inlined.

2 / 5

Total

12

/

20

Passed

Description

61%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 niche-distinct, naming concrete technologies and patterns, but it omits any explicit 'when to use' trigger guidance, which limits completeness. It reads as a capability statement rather than a trigger-equipped skill description.

Suggestions

Add an explicit 'Use when...' clause naming concrete trigger phrases, e.g. 'Use when building type-safe Node.js/Deno backends with fp-ts, modeling effects with ReaderTaskEither, or doing functional dependency injection.'

Include a few natural synonyms or file/extension cues users might say (e.g. 'functional backend', 'RTE', 'fp-ts services') to broaden trigger coverage from 4 to 5.

Lead with concrete actions (e.g. 'Build, compose, and test type-safe backend services...') rather than 'patterns for', to lift specificity above 3.

DimensionReasoningScore

Specificity

Names the domain ('Node.js/Deno backend development') plus specific techniques ('fp-ts, ReaderTaskEither, and functional dependency injection'), but describes patterns/tools rather than concrete actions, so coverage is not comprehensive.

3 / 5

Completeness

The 'what' is clear (FP patterns for backend dev via fp-ts), but there is no 'Use when...' clause or equivalent trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Includes natural keywords a user would say ('functional programming', 'Node.js', 'Deno', 'backend', 'dependency injection') alongside fp-ts-specific terms; a few common synonyms or phrasings are missing.

4 / 5

Distinctiveness Conflict Risk

The fp-ts / ReaderTaskEither niche is fairly distinct from general TypeScript or backend skills, with only minor overlap risk against broad Node/Deno skills.

4 / 5

Total

14

/

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 (1335 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.