Name: fp-async
Rating: 51.2 (1 reviews)
Author: administrakt0r

Blog Docs Log in Get started

fp-async

Practical async patterns using TaskEither - clean pipelines instead of try/catch hell, with real API examples

Quality

57%

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

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

Quality

Content

61%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 highly actionable with comprehensive, executable fp-ts examples, but it is a monolithic file with redundant before/after repetition and no progressive disclosure via reference files. Splitting the bulk API examples into separate files and trimming the repeated summary would improve conciseness and navigation.

Suggestions

Move the Prisma, file-operations, and Express examples into separate reference files (e.g., references/api-examples.md) and signal them from a concise overview in SKILL.md.

Remove or compress the final 'Before/After Summary' since it restates patterns already demonstrated in sections 1-4, saving tokens.

Add a brief validation/error-handling checkpoint note for the batch (traverseArray) and retry examples to strengthen workflow clarity.

Dimension	Reasoning	Score
Conciseness	Mostly code-driven and lean, but the closing 'Before/After Summary' repeats patterns already shown in sections 1-4 and includes mild motivational padding, so it could be tightened.	3 / 5
Actionability	Extensive copy-paste-ready TypeScript covering wrapping, chaining, parallelism, retry-with-backoff, Prisma repositories, and Express handlers, with a quick-reference table of common cases.	5 / 5
Workflow Clarity	Sections are logically numbered, but as a patterns catalog there are no explicit validation checkpoints or feedback loops, and the batch (traverseArray) and retry examples lack validation guidance.	3 / 5
Progressive Disclosure	A single ~950-line SKILL.md with no bundle files; the full API examples (Prisma, file ops, Express) and quick-reference card are inlined rather than split into one-level-deep reference files.	2 / 5
	Total	13 / 20 Passed

Description

53%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 conveys the skill's purpose and library focus concisely, but lacks an explicit 'when to use' trigger clause and leans on technical jargon over natural user phrasing. Adding a 'Use when...' clause with synonyms like 'fp-ts' and 'error handling' would raise completeness and trigger-term quality.

Suggestions

Add an explicit 'Use when...' clause naming concrete trigger phrases (e.g., 'Use when building async pipelines with fp-ts, handling errors without nested try/catch, or replacing promise chains with TaskEither').

Broaden trigger terms with synonyms users would naturally say, such as 'fp-ts', 'functional programming', and 'error handling', not just 'TaskEither'.

List a couple more concrete actions (e.g., 'retry with backoff', 'parallel fetch', 'typed error recovery') to strengthen specificity.

Dimension	Reasoning	Score
Specificity	Names the domain ('Practical async patterns using TaskEither') with 1-2 concrete actions ('clean pipelines', 'real API examples'), but is not comprehensive on capabilities.	3 / 5
Completeness	Has a clear 'what' but no 'Use when...' clause or equivalent trigger guidance, capping completeness at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	Includes some natural user terms ('async', 'try/catch') and the recognizable keyword 'TaskEither', but leans on technical jargon and misses common synonyms like 'fp-ts' and 'error handling'.	3 / 5
Distinctiveness Conflict Risk	The 'TaskEither' construct gives the skill a clear niche with minimal conflict risk, with only minor overlap with closely related fp-ts/async skills.	4 / 5
	Total	13 / 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 (967 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-async/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.