effected-packages

Index and implement @effected v4-first libraries for typed services.

2|Updated Jul 2, 2026
One-click install
npx skills add https://github.com/spencerbeggs/effected --skill effected-packages
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: effected-packages
Source: https://github.com/spencerbeggs/effected/tree/main/plugin/skills/effected-packages
Command: npx skills add https://github.com/spencerbeggs/effected --skill effected-packages

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill solves the challenge of discovering and correctly implementing the 25 specialized Effect v4-first libraries within the @effected ecosystem, preventing redundant re-implementation of common app plumbing.

Core Features & Use Cases

  • Ecosystem Indexing: Provides a comprehensive lookup for capabilities ranging from config loading and monorepo introspection to GitHub API integration and SBOM generation.
  • Tier-Based Guidance: Clearly distinguishes between pure, boundary, and integrated packages to help you manage runtime dependencies and IO surface area effectively.
  • Use Case: When starting a new Effect v4 application, use this Skill to identify which @effected packages provide the necessary schema-first services for your specific needs, such as XDG-compliant path resolution or SQLite-backed durable state.

Quick Start

Use the effected-packages skill to identify the correct package for handling JSONC configuration files and its required platform layer.

Frequently Asked Questions about effected-packages

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find the right Effect v4 package for monorepo tooling and configuration management?

To find the right Effect v4 package for monorepo tooling, use this Skill as an architectural index to lookup schema-first services for config loading, introspection, and runtime IO. It maps specific capabilities to the 25 specialized @effected libraries.

What is the difference between pure, boundary, and integrated packages in the @effected ecosystem?

Pure, boundary, and integrated packages differ by their runtime dependency surface. This Skill provides tier-based guidance distinguishing them to help manage IO boundaries and runtime dependencies correctly across Effect-based applications.

How do I implement typed Effect services for SQLite-backed durable state?

Implementing typed Effect services for SQLite-backed durable state requires selecting the correct @effected package. This Skill indexes ecosystem capabilities, matching schema-first service requirements like durable state to their specific library implementations.

Does this Skill help with dependency pinning across Effect-based monorepo applications?

Dependency pinning across Effect-based monorepo applications is supported by this Skill. It ensures consistent version pinning and proper service composition by providing a comprehensive architectural guide for the @effected v4-first library ecosystem.

Can I use this to identify packages for GitHub API integration and SBOM generation?

Identifying packages for GitHub API integration and SBOM generation is supported. The Skill's ecosystem indexing provides a lookup for these capabilities, preventing redundant re-implementation of common application plumbing.