CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

typescript-testing

Select and run TypeScript SDK verification for packages, examples, type checks, linting, builds, Vitest suites, Effect v4 CLI tests, and runtime E2E tests. Use when adding tests, diagnosing TypeScript CI, choosing a focused test command, validating TypeScript package changes, or writing/porting CLI tests against effect@^4.1.0 and @effect/vitest. Do not use for Python-only checks.

Quality

100%

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

100%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 model lean skill body: pure navigational overview with precisely conditioned pointers to real, one-level-deep reference files and no redundant teaching material. Structure, signaling, and token efficiency all sit at the top anchors.

DimensionReasoningScore

Conciseness

The ~10-line body contains zero padding and zero explanation of concepts Claude already knows; every line either states the skill's purpose or routes to a reference with a precise condition. It matches the "every token earns its place" anchor, not the 4 anchor, since nothing can be trimmed without losing information.

5 / 5

Actionability

Directives are concrete and executable with exact paths: "Read `references/test-commands.md` before running broad checks or adding new test coverage" and "Read `references/effect-v4-cli.md` before writing or modifying tests under `ts/packages/cli/test/`". Per the rubric's instruction-skill note, absence of inline code is not penalized when guidance is this specific and fully covers the two common workflows.

5 / 5

Workflow Clarity

This is a simple single-purpose skill under 50 lines whose only workflow is conditional routing to the right reference, and that routing is unambiguous (broad checks → test-commands.md; CLI test changes → effect-v4-cli.md). No destructive or batch operations are involved, so no validation checkpoints are required.

5 / 5

Progressive Disclosure

A clear one-line overview plus two well-signaled, one-level-deep references, both verified to exist in the bundle; each states when to read it, and the second summarizes its contents ("it.effect/layer(...) conventions, explicit per-service test layers..., and the @effect/platform-bun subpath-import rule"). The cross-link from test-commands.md to effect-v4-cli.md is a sibling reference, not a nested pointer chain.

5 / 5

Total

20

/

20

Passed

Description

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

An exemplary description: it states a comprehensive set of concrete capabilities in third-person/imperative voice, provides explicit and natural trigger phrases for each use case, and adds a clear exclusion boundary. No vagueness, padding, or over-claims are present.

DimensionReasoningScore

Specificity

"Select and run TypeScript SDK verification for packages, examples, type checks, linting, builds, Vitest suites, Effect v4 CLI tests, and runtime E2E tests" enumerates multiple specific concrete actions covering the full verification surface of the domain. It exceeds the 4 anchor because coverage is comprehensive rather than leaving minor gaps.

5 / 5

Completeness

It explicitly answers both what (the enumerated verification types) and when ("Use when adding tests, diagnosing TypeScript CI, ..."), with an additional negative boundary ("Do not use for Python-only checks"). Both halves are concrete and explicit, matching the top anchor exactly.

5 / 5

Trigger Term Quality

"Use when adding tests, diagnosing TypeScript CI, choosing a focused test command, validating TypeScript package changes, or writing/porting CLI tests against effect@^4.1.0 and @effect/vitest" supplies the natural phrases a user would say for every major use case, plus technology-specific identifiers (Vitest, E2E, effect@^4.1.0). It is not the 4 anchor because no common variation of this domain's vocabulary is missing.

5 / 5

Distinctiveness Conflict Risk

The niche is clearly pinned to Effect v4, @effect/vitest, Vitest, and CLI test porting, with an explicit exclusion clause for Python-only checks. Triggers are distinct and overlap risk with generic testing skills is minimal.

5 / 5

Total

20

/

20

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

Validation for skill structure

No warnings or errors.

Repository

ComposioHQ/composio

Path

.agents/skills/typescript-testing/SKILL.md

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.