컬렉션 framework

주목할 만한 에이전트 프레임워크 및 SDK 기반 | AI Agent Skills

Claude Code, Cursor, Windsurf용 frameworks sdk foundations AI Agent Skills 모음입니다. 개발자 워크플로 자동화에 초점을 둡니다.

이 페이지는 에이전트 시스템의 재사용 가능한 기반인 프레임워크, SDK, 핵심 라이브러리에 초점을 맞춥니다. 유지보수와 확장이 쉬운 구현을 원하는 팀을 위한 내용으로, 명확한 추상화와 일관된 인터페이스, 프로덕션급 아키텍처 패턴을 중시합니다. MCP는 통합 경로 중 하나일 수 있지만, 핵심 관점은 AI 에이전트 스킬을 위한 프레임워크 수준의 엔지니어링입니다.

Primary Install Bridge

Pick One Skill, Then Take the Install Path

This collection should not trap users in comparison mode or pretend to install the whole collection. Its job is to narrow the shortlist to one skill, then send the next click into installation, validation, and rollout. Installation happens on the skill path.

Step 1 / Primary Path

Step 1: Open the installation docs

Move from Agent Framework Tools discovery into the install flow, validation checklist, and first command path before comparing anything else.

Open the Install Path

Best-Fit Next Paths

The Next Click Should Keep Narrowing, Not Reset Back To A Generic Directory

Once the install path is clear, move into the solution, CLI, or editorial surface that best matches this collection. That keeps platform, framework, and operations demand narrowing into a more verifiable high-intent journey.

P1 solution

Agent Workflows Solution

A scenario page for users who already know the workflow problem they need to solve.

High-intent solution pages are safer recovery surfaces than broad skill detail expansion.

P1 solution

Process Automation Solution

A solution page for teams turning SOPs, handoffs, and operations into repeatable AI-assisted execution paths.

Operational intent deserves a stronger bridge than generic tooling lists can provide.

Editorial Proof & Trust Signals

Why This Collection Deserves Priority Attention

Reviewed on 2026-04-17 against framework workflow fit, installation clarity, operator handoff, and platform engineering usefulness. This page is now positioned as an install-first agent framework entry point instead of a broad framework roundup.

We prioritize this page because framework-intent users usually need a shortlist they can install, validate, and carry into real platform delivery loops quickly.

Trust Signals

- Entries are chosen for practical framework workflow value such as reusable abstractions, SDK delivery, platform consistency, and architectural clarity.
- Selection favors tools with public documentation and clear setup paths that teams can validate before wider rollout.
- The page is curated for repeatable platform engineering, not for vague framework keyword coverage or generic repository popularity.

Grouping Logic

- Lead with tools that can enter a framework-centered workflow without adding heavy setup ambiguity.
- Keep the shortlist compact enough for quick comparison while still covering SDKs, abstractions, review, and platform support.
- Use installation as the bridge from framework discovery into validated daily execution.

Maintenance & Review

Last Reviewed: 2026-04-17
Cadence: Re-check when install flow, maintainer posture, or framework workflow relevance changes upstream; otherwise review monthly.
Maintained By: Killer-Skills editorial review within the recovery-focused authority queue.
Verification: Validate installability, operator clarity, workflow fit, and maintainer trust before retaining or adding an entry.

Execution Examples

How These Skills Work Together In Practice

Install one agent framework tool first

Use this page when you want one framework companion that can enter real platform work without turning evaluation into another endless architecture comparison.

1. Open the installation docs before opening more framework-related repositories.
2. Choose one tool that best supports SDK work, abstractions, platform consistency, or architecture delivery.
3. Install it and verify the CLI write path, sync behavior, and first operator checkpoint.
4. Only after the base path works, expand the setup across the wider framework workflow.

Reduce architecture selection drift

Treat the collection as an editorial filter when you need framework-adjacent tools that improve platform confidence without overcomplicating the stack.

1. Check whether the tool has stable ownership and visible install guidance.
2. Review CLI behavior so operators know what will be written and synced.
3. Use one validated path before scaling it to more packages, services, or teammates.
4. Document the chosen framework workflow baseline after the first clean rollout.

After Installation

Supporting Moves After The Install Path Is Clear

Step 2

Step 2: Check CLI write and sync behavior

Confirm what the CLI writes, how sync behaves, and what operators should validate after the install path is clear.

Step 3

Step 3: Cross-check with trusted tools

Use the official trusted collection to sanity-check workflow choices before you standardize a team stack.

Adding an Outbound Event Endpoint

microbus-io

Creates or modify an outbound event endpoint of a microservice. Use when explicitly asked by the user to create or modify an outbound event endpoint of a microservice.

★ 170

⑂ 0

개발자

Modifying a Feature of a Microservice

microbus-io

Your coding agent can already code. Microbus teaches it to master the complex domain of distributed systems — the architecture, the patterns, the operational discipline — and produce enterprise-grade microservices, every time.

★ 170

⑂ 0

개발자

lore-field-repair

lorehq

Guided workflow for diagnosing and fixing harness bugs in deployed instances

★ 16

⑂ 0

인공지능

plutonium

radioactive-labs

High-level guide for working with Plutonium applications - read this first

★ 56

⑂ 0

인공지능

Related Authority Collections

If This Page Is Close, Keep Narrowing With Adjacent Authority Pages

Do not reset back to the generic directory. Move sideways through these adjacent high-intent collections to narrow the shortlist toward the install path that best matches your team.

P1 collection

DevOps Workflow Tools to Install First

An operations-first collection for platform teams choosing release, incident, and automation helpers.

Operational intent is high value and should be routed into curated workflow picks instead of generic tool sprawl.

P1 collection

TypeScript Workflow Tools to Install First

A typed-development collection that helps product teams shortlist TypeScript workflow tools with clear next steps.

TypeScript intent is strong enough to support a dedicated authority page instead of another mixed language roundup.

P2 collection

Community Skills to Install First

A community-tested collection for builders who want reusable skills without falling back to unfiltered repository browsing.

Community demand can still look authoritative when it is filtered through explicit curation and rollout logic.

P1 collection

Gemini Workflow Tools to Install First

A Gemini-specific collection that turns compatibility research into a curated install path for real delivery teams.

Gemini demand is easier to trust when it lands on a curated shortlist instead of a loose compatibility wrapper.

Installation Questions

Answer These Three Questions Before You Install

This collection should not keep users browsing forever. These three questions explain how to shortlist, install, and validate the next step.

이 컬렉션들은 어떤 워크플로를 위해 만들어졌나요?

워크플로 자동화, 프로세스 자동화, 문서 작업, 데이터 워크플로 및 재사용 가능한 스킬 스택을 중심으로 구성되어 있습니다.

컬렉션과 메인 스킬 디렉터리의 차이점은?

스킬 디렉터리는 직접 검색과 필터링에 적합하고, 컬렉션은 완전한 워크플로를 위한 보완적 스킬 묶음을 찾는 데 적합합니다.

이 컬렉션들을 Claude Code나 Cursor에 설치할 수 있나요?

네. 이 컬렉션의 스킬들은 일반적으로 Claude Code, Cursor, Windsurf 및 기타 지원 환경에서 통합 설치 흐름으로 작동합니다.

Additional Recovery Paths

Use These Additional Paths If You Need One More Step To Narrow The Decision

These are the supporting surfaces for this collection after the install direction is clear and the primary next paths have already narrowed the decision.

P1 guide

Official AI Agent Skills Guide

An editorial guide that explains why certain skills are trusted and how to choose among them.

Editorial guides let the site lead with reasoning instead of raw inventory.

P1 solution

Workflow Automation Solution

A use-case page for users searching for repeatable automation patterns instead of one-off tools.

Workflow automation demand is easier to satisfy with curated intent clusters than with flat directory coverage.