Effect
Apply Effect v4 conventions for services, layers, tagged errors, boundary runners, resources, retries, deadlines, HTTP, and tests. Use when writing or reviewing TypeScript that imports effect, adds a service or error class, chooses where to run a program, bounds external I/O, or tests Effect code.
Install
npx skills add jpoehnelt/skills --skill effectgit clone --depth 1 https://github.com/jpoehnelt/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/effect ~/.claude/skills/effectPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Effect v4 Assumes Effect v4 (the `effect@4.0.x` line, including its release candidates). Effect 3 differs in names and modules (`Context.Tag`, `Effect.catchAll`, `@effect/platform`); do not mix the two. Read the installed version before using an API you have not seen in the repo, and follow the repo's AGENTS.md where it differs from this skill: a repo rule or a documented exception wins. Repo facts (from AGENTS.md): pinned Effect version and how bumps land, import policy (deep imports, `effect/unstable/*` barrels), boundary runners and the shared `ManagedRuntime`, the house error file, Effect lint gates, test runner and helpers, check and test commands. ## Boundaries A boundary is where a Promise or process exit is the contract: an HTTP or route handler, a framework load or action, a Durable Object method, a queue or workflow step body, an extension or CLI entrypoint. Everything else returns an Effect under its own name and composes with `yield*`. - Run programs only at boundaries, through the repo's runner and one `ManagedRuntime` per process (`NodeRuntime.runMain` for Node entrypoints). No `Effect.runPromise`/`runSync`/`runFork` in domain code outside tests. - No `fooEffect` twin, no Promise wrapper lifted back with `Effect.promise`, no runner's Promise re-entered as an Effect. - Browser code may import pure modules (`Schema`, `Option`, `Data`, `Result`) but never runs a program that needs services.
Details
- Skill name
effect- Repository
- jpoehnelt/skills
- Path
effect/SKILL.md- License
- MIT
- Repo updated
- 12 November 2026
FAQ
What does the Effect skill do?
Apply Effect v4 conventions for services, layers, tagged errors, boundary runners, resources, retries, deadlines, HTTP, and tests. Use when writing or reviewing TypeScript that imports effect, adds a service or error class, chooses where to run a program, bounds external I/O, or tests Effect code.
How do I install the Effect skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add jpoehnelt/skills --skill effect. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Effect popular?
It lives in jpoehnelt/skills, which has 23 GitHub stars and 1 forks.
Related skills
Agents Correct
23jpoehnelt/skills
Find the mistakes agents keep repeating in a repo and make each one impossible, trying architecture first, then types, lint, tests, and docs last. Use when the operator keeps correcting the same mistake, or for /agents-correct.
Agents Create Verification Skill
23jpoehnelt/skills
Generate a project-local verify skill that drives the app like a user through a browser with Playwright, a CLI, or HTTP. Use for /agents-create-verification-skill, "make a verify skill for this repo", or when a project has no scripted way to prove UI, CLI, or service behavior.
Agents Reflect
23jpoehnelt/skills
After a work session, review what went wrong and right and turn each lesson into a concrete edit to an existing skill or AGENTS.md line. Use when the user says "reflect" or /agents-reflect.
Eng Blast Radius
23jpoehnelt/skills
Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it is safe because of by running real code. Use when asked for the "blast radius of X" or "what could this break", or when reviewing a small diff you do not trust.
Comms How
23jpoehnelt/skills
Explain how a subsystem works, its architecture, runtime flow, and where new code belongs. Use for "how does X work", walkthroughs before changing something, and placement or ownership questions like "where should this live" or "which package owns this". Use comms-why for motivation.
Isms P Audit
9basejb/isms-p-audit-skill
ISMS-P 인증 사전 점검을 위한 코드/IaC 정적 분석 스킬. 사용자가 "ISMS 점검", "ISMS-P 준비", "보안 감사", "통제항목 점검", "개인정보보호 감사", "정보보호 인증 준비"를 언급하거나, NestJS/ Spring/Django/Rails 같은 백엔드 프로젝트에서 IAM·로깅·암호화·접근통제 미흡 사항을 식별해 달라고 요청할 때 호출한다. Glob/Grep/Read로 코드와 Terraform/CloudFormation/Kubernetes 매니페스트를 스캔해 ISMS-P 통제항목과 매핑된 리스크 보고서를 생성한다. EN: Static analysis skill for ISMS-P (Korean Personal Information & Information Security Management System) pre-audit. Triggers on phrases like "ISMS audit", "ISMS-P readiness", "security compliance check", "Korean privacy audit". Scans source code and IaC to map findings to ISMS-P controls and
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.