effect-v4

Write, review, or upgrade Effect v4 code in the Composio CLI, cli-keyring, and json-schema-to-effect-schema packages, all pinned exactly to effect@4.0.0-rc.112 — Context.Service and explicit layers, Schema.TaggedError and typed recovery, the effect/unstable/cli command surface, and the vendored effect source oracle. Use when writing or reviewing Effect v4 code, answering a v4 API question, working in effect/unstable/cli, defining a Context.Service service, modeling an error with Schema.TaggedError, bumping the Effect prerelease pins, or verifying an unfamiliar API against ts/vendor/effect. Do not use for CLI command UX/wiring design (use cli-command) or CLI E2E tests (use cli-e2e).

Quality

89%

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

78%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 well-structured, actionable skill body: dense non-negotiables, concrete verification commands, and clean progressive disclosure into real reference files, with only minor room to tighten phrasing and add an explicit validation retry loop.

Suggestions

Add an explicit validate→fix→retry loop in the Verification section (e.g., 'If typecheck or check-examples.mjs fails, fix the offending file/reference and re-run until clean') to reach the top workflow_clarity anchor.

Trim the parenthetical justification on Effect.fn ('worth it for service members and combinator callbacks that should be attributable in error reports') to keep conciseness at the lean anchor.

Consider a one-line 'Why pinned' rationale is already present — verify no other asides can be shortened to lift conciseness to 5.

Dimension	Reasoning	Score
Conciseness	Lean and information-dense with no padding or explanation of concepts Claude already knows; the only minor trim opportunity is the parenthetical on Effect.fn ('worth it for service members...'), so it sits just below the fully lean anchor.	4 / 5
Actionability	Provides concrete executable commands (pnpm typecheck, pnpm --filter @composio/cli test, node .agents/skills/effect-v4/scripts/check-examples.mjs) and specific API guidance (Effect.gen, Context.Service, Schema.TaggedError, Effect.catchTag/catchTags/Match, Effect.tryPromise({ try, catch })), with minor gaps left to the references.	4 / 5
Workflow Clarity	The Verification section sequences concrete commands (typecheck → test → validate:agent-skills → validate:skill-routing → check-examples.mjs) with a 'trust the file and fix the reference' correction note, but lacks an explicit validate→fix→retry loop, so it is a step short of the top anchor.	4 / 5
Progressive Disclosure	SKILL.md is a concise overview pointing to three well-signaled, one-level-deep references (core-patterns.md, cli-surface.md, upgrade-workflow.md), each summarized in the 'Read next' list and verified to exist, with content appropriately split across files.	5 / 5
	Total	17 / 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.

A high-quality description: concrete actions, natural trigger phrases, explicit what/when guidance, and clear disambiguation from neighboring skills, all in concise third-person voice.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions across the domain — 'Write, review, or upgrade Effect v4 code', 'defining a Context.Service service', 'modeling an error with Schema.TaggedError', 'bumping the Effect prerelease pins', 'verifying an unfamiliar API' — giving comprehensive concrete coverage rather than vague claims.	5 / 5
Completeness	Explicitly answers both what ('Write, review, or upgrade Effect v4 code... Context.Service... Schema.TaggedError...') and when ('Use when writing or reviewing Effect v4 code, answering a v4 API question...'), plus negative-scope guidance.	5 / 5
Trigger Term Quality	Includes natural phrases a user would actually say — 'writing or reviewing Effect v4 code', 'answering a v4 API question', 'working in effect/unstable/cli', 'bumping the Effect prerelease pins' — with good synonym coverage (write/review/upgrade).	5 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (Effect v4 pinned to 4.0.0-rc.112 in specific packages) and explicitly disambiguates from sibling skills — 'Do not use for CLI command UX/wiring design (use cli-command) or CLI E2E tests (use cli-e2e)' — minimizing conflict risk.	5 / 5
	Total	20 / 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
relative_links	Relative link issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: ComposioHQ/composio
Path: .agents/skills/effect-v4/SKILL.md
Commit: 7a63e5a

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