CtrlK
BlogDocsLog inGet started
Tessl Logo

fsharp-testing

F# testing patterns with xUnit, FsUnit, Unquote, FsCheck property-based testing, integration tests, and test organization best practices.

67

Quality

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

80%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, concise F# testing reference with excellent executable examples, but it functions as a monolithic inline catalog without progressive disclosure to separate files and without an explicit test-run/validate workflow with checkpoints.

Suggestions

Move the per-tool deep-dive examples (FsCheck generators, WebApplicationFactory integration setup) into reference files linked from a concise overview to improve progressive disclosure.

Add a short 'Test workflow' section with an explicit validate checkpoint, e.g. run 'dotnet test', inspect failures, fix, re-run until green.

DimensionReasoningScore

Conciseness

The body is lean and code/table-driven, assumes Claude knows F# and the libraries, and avoids explaining basic concepts; the one prose note (Unquote's quotation-based failure messages) adds non-obvious value rather than padding.

3 / 3

Actionability

It provides complete, executable F# examples for unit, async, parameterized, property-based, mocking, and integration tests plus concrete 'dotnet test' commands, making the guidance copy-paste ready.

3 / 3

Workflow Clarity

The content is organized as a topical catalog rather than a sequenced multi-step workflow, and lacks explicit validation checkpoints or a feedback loop; the sections progress logically but no checkpoints are signaled.

2 / 3

Progressive Disclosure

Sections are well-organized, but ~280 lines of detail (per-tool code examples, anti-patterns) live entirely inline in a single SKILL.md with no external reference files, and the under-50-line exception does not apply.

2 / 3

Total

10

/

12

Passed

Description

82%

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 specific, well-targeted description with strong trigger terms and a distinct F# testing niche, but it omits explicit 'when to use' trigger guidance, capping completeness. Adding a 'Use when...' clause would round it out.

Suggestions

Add an explicit trigger clause, e.g. 'Use when writing or reviewing F# tests, setting up xUnit/FsCheck test projects, or debugging flaky F# tests.'

Drop the buzzword 'best practices' in favor of a concrete capability to keep every term earning its place.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete capabilities and tools — 'xUnit, FsUnit, Unquote, FsCheck property-based testing, integration tests, and test organization' — rather than vague language, matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

It clearly answers 'what' (F# testing patterns with named tools) but lacks any 'Use when...' clause or equivalent explicit trigger guidance, so per the rubric guidelines completeness is capped at 2.

2 / 3

Trigger Term Quality

Terms like 'F# testing', 'xUnit', 'property-based testing', and 'integration tests' are natural phrases a user would say when needing this skill, giving good coverage rather than just technical jargon.

3 / 3

Distinctiveness Conflict Risk

The F#-specific toolchain (FsUnit, Unquote, FsCheck) carves a clear niche unlikely to trigger for non-F# or generic testing skills.

3 / 3

Total

11

/

12

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
affaan-m/ECC
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.