effect-first-development
Provides a comprehensive guide for implementing Effect-first development practices in production code, ensuring robust error handling and schema management.
Install this skill
Security score
The effect-first-development skill was audited on Jun 15, 2026 and we found 9 security issues across 2 threat categories. Review the findings below before installing.
Categories Tested
Security Issues
Template literal with variable interpolation in command context
| 342 | onNonEmpty: (values) => `count:${A.length(values)}` |
Template literal with variable interpolation in command context
| 387 | running: ({ workerId }) => `running:${workerId}`, |
Template literal with variable interpolation in command context
| 388 | failed: ({ reason }) => `failed:${reason}` |
Template literal with variable interpolation in command context
| 582 | } = dual(2, (self: string, tag: string) => `[${tag}] ${self}`) |
Template literal with variable interpolation in command context
| 699 | yield* Effect.logInfo(`port=${port}`) |
Template literal with variable interpolation in command context
| 700 | yield* Effect.logDebug(`apiKey=${String(apiKey)}`) |
Access to .env file
| 46 | 27. Am I reading config? Use `Config` / `ConfigProvider`, not direct `process.env` in domain code. |
Access to .env file
| 112 | 33. Config should be modeled via `Config` and `ConfigProvider`, not direct `process.env` access in domain services. |
Access to .env file
| 772 | 14. `rg -n "process\\.env" apps packages tooling infra` |