CtrlK
BlogDocsLog inGet started
Tessl Logo

fp-data-transforms

Everyday data transformations using functional patterns - arrays, objects, grouping, aggregation, and null-safe access

48

Quality

51%

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

The canonical home for this skill is fp-data-transforms 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 body is highly actionable with excellent executable examples, but it is markedly verbose — re-teaching basic FP concepts — and monolithic, with no progressive disclosure into reference files despite its length.

Suggestions

Trim or remove the 'Imperative Approach' blocks for trivial operations (map/filter/reduce/spread) that Claude already knows; keep them only where the comparison is genuinely instructive.

Split the fp-ts API tour and the 'Real-World Examples' into separate reference files (e.g. references/fp-ts.md, references/examples.md) and link to them from a leaner overview.

Move content that is pure reference (the fp-ts method catalog) out of the main flow so SKILL.md reads as an overview with one-level-deep pointers.

DimensionReasoningScore

Conciseness

At ~1500 lines it extensively demonstrates imperative for-loops and explains map/filter/reduce/spread/optional-chaining — concepts Claude already knows — so several sections are padded with unnecessary 'Imperative Approach' blocks.

2 / 5

Actionability

It provides complete, executable TypeScript with reusable utilities (pick, omit, groupBy, countBy, sumBy) and concrete normalization/pipeline examples that are copy-paste ready and cover the common cases.

5 / 5

Workflow Clarity

It is a well-organized patterns catalog with a 'When to Use What' decision section, but it contains no multi-step workflows with validation checkpoints; sequence is topical rather than process-oriented.

3 / 5

Progressive Disclosure

No bundle files exist and all content is inlined in one ~1500-line SKILL.md; material that clearly belongs in separate references (the fp-ts API tour, real-world examples) is not split out, and the <50-line exception does not apply.

2 / 5

Total

12

/

20

Passed

Description

50%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 a clear topic and lists specific sub-areas, but it omits any 'Use when…' trigger guidance and relies on category nouns rather than concrete actions, leaving it mid-rubric across all dimensions.

Suggestions

Add an explicit trigger clause, e.g. 'Use when reshaping arrays or objects, normalizing API responses, grouping/aggregating data, or safely accessing nested values.'

Lead with concrete verbs ('Reshape arrays and objects, group and aggregate records, normalize API responses, access nested values safely') to raise specificity.

Include natural user-facing synonyms and file/extension cues where applicable to improve trigger-term coverage.

DimensionReasoningScore

Specificity

It names the domain and several specific sub-areas ('arrays, objects, grouping, aggregation, and null-safe access'), but these are mostly noun-categories rather than the concrete verbs (e.g. 'extract', 'fill', 'merge') that anchor 4 requires.

3 / 5

Completeness

The 'what' is clear ('Everyday data transformations using functional patterns…'), but the 'when' is entirely absent with no explicit trigger guidance, which caps completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Relevant terms like 'grouping', 'aggregation', and 'arrays' appear, but there is no 'Use when…' trigger clause and 'null-safe access' is technical jargon rather than a phrase users naturally say.

3 / 5

Distinctiveness Conflict Risk

'Data transformations' is broad and could overlap with many data-handling skills; the 'functional patterns' qualifier narrows it but meaningful overlap risk remains.

3 / 5

Total

12

/

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