CtrlK
BlogDocsLog inGet started
Tessl Logo

fp-option-ref

Quick reference for Option type. Use when user needs to handle nullable values, optional data, or wants to avoid null checks.

65

Quality

79%

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/skills/fp-option-ref/SKILL.md

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

SKILL.md
Quality
Evals
Security

Quality

Content

88%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.

A tight, well-structured reference card that delivers executable examples across the core Option operations. Its main weakness is one incorrect code snippet and the absence of any progressive-disclosure references for deeper material.

Suggestions

Fix `O.fromPredicate(x > 0)(x)` to a correct predicate form such as `O.fromPredicate((x: number) => x > 0)(x)` so examples are copy-paste accurate.

Consider offloading extended patterns (e.g. traversals, Do-notation, OptionT) into a one-level-deep reference file to keep the overview lean.

Add a brief validation cue for cases where Option is used to guard destructive or batch operations, to strengthen workflow clarity further.

DimensionReasoningScore

Conciseness

The body is lean and code-first with minimal prose ("Option = value that might not exist. Some(value) or None."), assuming Claude's competence and adding no concept padding.

5 / 5

Actionability

Mostly executable copy-paste TypeScript covering create/transform/extract patterns, but `O.fromPredicate(x > 0)(x)` is incorrect (it expects a predicate function, not a boolean), a minor correctness gap.

4 / 5

Workflow Clarity

As a simple single-purpose reference card it is unambiguously organized into Create, Transform, Extract, Common Patterns, and vs Nullable sections with no destructive or batch steps requiring validation.

5 / 5

Progressive Disclosure

Well-organized section headers make navigation easy and the content is appropriately self-contained for a quick reference, but there are no one-level-deep references and the body slightly exceeds the 50-line simple-skill heuristic.

4 / 5

Total

18

/

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.

A compact, third-person description that pairs a clear trigger clause with a specific FP niche. It is held back from a top score by a thin 'what' statement and missing common synonyms like 'Maybe'.

Suggestions

Expand the 'what' to list concrete capabilities (e.g. create, transform, extract, and chain Option values) instead of 'Quick reference for Option type'.

Add common synonyms and library cues such as 'Maybe', 'fp-ts Option', and 'optional chaining alternative' to broaden trigger coverage.

Tighten distinctiveness by naming fp-ts explicitly so it does not collide with generic null-handling skills.

DimensionReasoningScore

Specificity

"Quick reference for Option type" names the domain, and "handle nullable values, optional data, or wants to avoid null checks" gives a few concrete actions, but coverage is not comprehensive and the 'what' is thin.

3 / 5

Completeness

It answers both what ("Quick reference for Option type") and when ("Use when user needs to handle nullable values...") with concrete triggers, but the 'what' side stays generic rather than enumerating capabilities.

4 / 5

Trigger Term Quality

"nullable values, optional data, null checks" are natural phrases a user would say, though common synonyms like "Maybe" or "fp-ts" and file/extension cues are missing.

4 / 5

Distinctiveness Conflict Risk

The Option/nullable niche is fairly distinct with specific triggers, with only minor overlap risk against generic null-handling or fp-ts utility skills.

4 / 5

Total

15

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

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.