uinaf/effect-ts
Implement, debug, refactor, migrate, review, or explain Effect TypeScript code. Use when a task touches `effect` or `@effect/*` APIs, especially services, layers, schemas, runtime wiring, platform or CLI packages, Effect testing, or Promise-to-Effect migration.
98
100%
Does it follow best practices?
Impact
93%
1.16xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that clearly defines both what the skill does and when to use it. It provides specific, concrete actions and rich trigger terms drawn from the Effect TypeScript ecosystem, making it highly distinguishable from general TypeScript or other framework skills. The explicit 'Use when' clause with detailed trigger scenarios ensures reliable skill selection.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: implement, debug, refactor, migrate, review, and explain. Also enumerates specific sub-domains like services, layers, schemas, runtime wiring, platform/CLI packages, testing, and Promise-to-Effect migration. | 3 / 3 |
Completeness | Clearly answers both 'what' (implement, debug, refactor, migrate, review, or explain Effect TypeScript code) and 'when' (explicit 'Use when' clause specifying tasks touching effect or @effect/* APIs with detailed trigger scenarios). | 3 / 3 |
Trigger Term Quality | Includes highly natural trigger terms users would say: 'effect', '@effect/*', 'services', 'layers', 'schemas', 'runtime wiring', 'CLI packages', 'Effect testing', 'Promise-to-Effect migration'. These cover the key vocabulary an Effect TypeScript user would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets the specific Effect TypeScript library ecosystem with named packages (@effect/*), specific concepts (layers, schemas, runtime wiring), and a unique migration path (Promise-to-Effect). Unlikely to conflict with general TypeScript or other library skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill file that is concise, well-structured, and highly actionable. It efficiently routes Claude to the right reference material based on task type, provides concrete code examples demonstrating idiomatic patterns, and establishes clear priorities for information sources. The anti-patterns in the 'Avoid' section add valuable guardrails without being verbose.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient throughout. It assumes Claude knows TypeScript and Effect basics, never explains what Effect is, and every section earns its place with actionable guidance or concrete code examples. | 3 / 3 |
Actionability | Provides executable TypeScript code examples for services, layers, Effect.gen, and Effect.fn patterns. The step-by-step start section gives concrete commands (inspect package.json, run effect-solutions commands), and the topic map provides specific CLI invocations. | 3 / 3 |
Workflow Clarity | The 'Start' section provides a clear 4-step sequence for approaching any Effect task. The 'Read By Task' section acts as a decision tree routing to the right reference. The 'Source Order' section establishes a clear priority hierarchy. For this type of skill (coding guidance, not destructive operations), validation checkpoints aren't critical. | 3 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a concise overview in SKILL.md and well-signaled one-level-deep references to four specific reference files organized by task type. The topic map provides additional navigation via the effect-solutions tool, and external docs are referenced for deeper detail. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
Reviewed
Table of Contents