fsharp-testing

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

Quality

82%

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

Quality

Content

76%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 highly actionable, well-organized reference with executable F# examples for every major testing scenario. Its weakness is workflow clarity: destructive/batch testing flows lack explicit validation or feedback-loop checkpoints, which caps that dimension.

Suggestions

Add an explicit validation/retry loop for integration and coverage runs (e.g. 'After dotnet test --collect, verify coverage meets threshold; if not, add cases and re-run') to lift workflow_clarity above the destructive/batch cap of 3.

Trim the framework-stack table's Purpose column or merge it into prose, since xUnit/FsUnit/Unquote roles are largely restated in the code sections that follow.

Add a brief 'Flaky test debugging' checklist under When to Activate to turn that activation trigger into a concrete, sequenced workflow.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with sectioned, copy-ready examples and tables, but the framework-stack table and a few prose lines restate tool purposes Claude already knows; minor trimming would reach 5.	4 / 5
Actionability	Provides fully executable, copy-paste-ready F# examples across unit, async, theory, property-based, mocking, and integration-test cases, plus concrete dotnet CLI commands covering the common workflows.	5 / 5
Workflow Clarity	Test categories and the running-tests commands are sequenced, but there are no validation checkpoints or feedback loops for batch/destructive operations (e.g. coverage runs, integration DB resets), and the cap for missing validation in such contexts holds it at 3.	3 / 5
Progressive Disclosure	Well-organized into clearly signaled sections (unit, property, mocking, integration, organization) with a single-level Related Skills pointer; no bundle files exist, so structure rather than file references drives the score, leaving it just short of 5.	4 / 5
	Total	16 / 20 Passed

Description

88%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 strong, specific description that names concrete tools and actions while providing an explicit 'Use when' trigger. Minor synonym/extension coverage and adjacent-skill overlap keep trigger quality and distinctiveness just below maximum.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions across a comprehensive toolset — xUnit, FsUnit, Unquote, FsCheck, integration tests, and test organization — matching the 'multiple specific concrete actions; comprehensive coverage' anchor.	5 / 5
Completeness	Explicitly states what it does ('F# testing patterns with xUnit, FsUnit, Unquote, FsCheck, integration tests, and test organization best practices') and when to use it ('Use when writing F# tests with xUnit, FsUnit, Unquote, or FsCheck'), satisfying both what and when with concrete triggers.	5 / 5
Trigger Term Quality	Includes natural terms users would say ('writing F# tests', 'xUnit', 'FsCheck', 'integration tests') with good coverage, but lacks common synonyms or file extensions (e.g. '.fs', 'property tests') that would push it to 5.	4 / 5
Distinctiveness Conflict Risk	Carves a clear F#-testing niche with distinct tool triggers and minimal conflict risk, though it borders on overlap with a generic 'csharp-testing' companion skill, keeping it just below 5.	4 / 5
	Total	18 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Path: skills/fsharp-testing/SKILL.md
Commit: 06c5e11

Reviewed: 3 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.