REST 및 GraphQL API 설계 원칙 가이드. 새로운 API 설계, API 스펙 리뷰, API 설계 표준 수립 시 활용. 트리거: "API 설계", "REST", "GraphQL", "엔드포인트 설계", "API versioning", "API 패턴" 안티-트리거: "프론트엔드 UI", "데이터베이스 스키마만", "CSS/스타일링", "배포/인프라"
GitHub repository access in containerized environments using REST API and credential detection. Use when git clone fails, or when accessing private repos/writing files via API.
Use this skill when designing, documenting, or generating REST API specifications using OpenAPI/Swagger. Trigger on keywords like OpenAPI, Swagger, API spec, REST documentation, API schema, request body, response schema, and API client generation. Also apply when adopting design-first API development, validating API contracts, or setting up auto-generated API documentation for FastAPI, Express, or NestJS endpoints. --- # OpenAPI & REST API Design ## When to Use - Documenting REST APIs - Generating API clients - API design-first development - Defining webhook contracts - Establishing pagination, versioning, or auth patterns for a new service ## When NOT to Use - Internal-only scripts or automation that do not expose HTTP endpoints - CLI tools and command-line utilities without a REST interface - GraphQL APIs where a different specification format applies --- ## Core Patterns ### 1. OpenAPI 3.1 Specification Structure A complete spec skeleton showing every top-level section. Use `$ref` to split large specs into per-resource files. ```yaml
Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers. Use when designing new APIs, reviewing API specifications, or establishing... Українською: проектуй API, спроектувати ендпоінт, API дизайн, REST, GraphQL, версіонування API, контракт API, документація API, масштабованість, ресурси, маршрути, HTTP методи, відповідь сервера, структура запиту.
Unity API の探索と実行。u api schema で検索、u api call で任意の public static メソッドを呼ぶ。
Monitor and query Claude Code sessions — list sessions, search conversations, check costs, view AI fluency score, see live running agents. Use when the user asks about their Claude Code usage, costs, session history, or running agents. --- ## You operate the `claude-view` HTTP API **If the claude-view MCP tools are available in your environment, prefer using them instead of curl.** This skill is the fallback for environments without MCP support. claude-view runs a local server on port 47892 (or `$CLAUDE_VIEW_PORT`). All endpoints return JSON (camelCase field names). Base URL: `http://localhost:47892` ## Resolving the server 1. Check if running: `curl -sf http://localhost:47892/api/health` 2. If not running, tell user: `npx claude-view` ## Endpoints | Intent | Method | Endpoint | Key Params | |--------|--------|----------|------------| | List sessions | GET | `/api/sessions` | `?limit`, `?q`, `?filter`, `?sort`, `?offset`, `?branches`, `?models`, `?time_after`, `?time_before` | | Get session detail | GET | `/api/sessions/{id}` | — | | Search sessions | GET | `/api/search` | `?q` (required), `?limit`, `?offset`, `?scope` | | Dashboard stats | GET | `/api/stats/dashboard` | `?project`, `?branch`, `?from`, `?to` | | AI Fluency Score | GET | `/api/score` | — | | Token stats | GET | `/api/stats/tokens` | — | | Live sessions | GET | `/api/live/sessions` | — | | Live summary | GET | `/api/live/summary` | — | | Server health | GET | `/api/health` | — | ## Reading responses All responses are JSON with camelCase field names. Key shapes: **Sessions list:** `{ sessions: [{ id, project, displayName, gitBranch, durationSeconds, totalInputTokens, totalOutputTokens, primaryModel, messageCount, turnCount, commitCount, modifiedAt }], total, hasMore }` **Session detail:** All session fields plus `commits: [{ hash, message, timestamp, branch }]` and `derivedMetrics: { tokensPerPrompt, reeditRate, toolDensity, editVelocity }` **Search:** `{ query, totalSessions, totalMatches, elapsedMs,
Add a new endpoint or endpoints to Ghost's Admin API at `ghost/api/admin/**`.
Design complete API contracts covering endpoints, auth, rate limiting, error handling, retries, circuit breaker and idempotency. Activate when user mentions "api contract", "api design", "endpoint", "webhook", "REST", "GraphQL", "OpenAPI", "design the API".
Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend. --- # API and Interface Design ## Overview Design stable, well-documented interfaces that are hard to misuse. Good interfaces make the right thing easy and the wrong thing hard. This applies to REST APIs, GraphQL schemas, module boundaries, component props, and any surface where one piece of code talks to another. ## When to Use - Designing new API endpoints - Defining module boundaries or contracts between teams - Creating component prop interfaces - Establishing database schema that informs API shape - Changing existing public interfaces ## Core Principles ### Hyrum's Law > With a sufficient number of users of an API, all observable behaviors of your > system will be depended on by somebody, regardless of what you promise in the > contract.
Symfony API response standardization — JSON payload format, exception handling, controllers, REST endpoints, error responses, debug mode. Triggers on: API, endpoint, controller, response, error handling, JSON, REST, API response, exception subscriber, HTTP
백엔드 도메인 knowledge. Node.js/TypeScript API 설계, PostgreSQL/Drizzle ORM, 인증/보안, 캐싱(Redis), 메시지 큐(BullMQ), 동시성, 분산 시스템, 마이크로서비스, 성능 최적화, 장애 대응, 배포, 모니터링 시 활성화. 서버 로직, DB 쿼리, API endpoint 작성/수정/리뷰 시, 백엔드 설계 판단이 필요할 때 사용한다. 사용자가 API endpoint, DB 스키마, 쿼리 최적화, 인증 플로우, 캐시 전략, 큐 처리, 배포 파이프라인, 서버 에러를 언급하면 반드시 이 스킬을 활성화하라. 명시적으로 '백엔드'라고 말하지 않더라도 서버 사이드 로직, 인프라, .controller.ts/.service.ts/.module.ts/.entity.ts 파일을 다루는 작업이면 활성화한다. --- # BE Domain Knowledge 매핑 테이블의 참조 파일에는 프로젝트 고유의 아키텍처 결정, 검증된 패턴, 안티패턴이 담겨 있다. 이를 읽지 않으면 기존 시스템 설계와 충돌하는 코드를 작성하게 되고, 리뷰에서 반려된다. 코드를 작성하거나 리뷰하기 전에 아래 매핑 테이블에서 태스크에 해당하는 파일을 반드시 Read하라. **기본 경로**: `~/.claude/skills/be/` — 아래 테이블의 파일명 앞에 이 경로를 붙여서 Read한다. ## 핵심 원칙 - 시스템 철학: "견고하고 확장 가능한 시스템" - 4대 원칙: 안정성(Reliability), 확장성(Scalability), 관찰 가능성(Observability), 보안(Security) - 기술 스택: TypeScript strict, Node.js, Fastify 5, PostgreSQL 16+, Drizzle ORM, Redis, BullMQ, Pino, Vitest - API 계약: RFC 9457 Problem Details 표준, Breaking change는 versioning - 안티패턴: Happy path만 구현, 추측 기반 최적화, "나중에 보안 처리", 로그 없는 시스템 ## 태스크-지식 매핑 | 태스크 유형 | 판단 기준 | Read할 파일 | |---|---|---| | API 설계/구현 | endpoint 정의·요청/응답 스키마·라우팅 | `api-design.md` + `error-handling.md` | | DB 스키마/쿼리 | 테이블 설계·마이그레이션·raw 쿼리 | `database.md` + `postgresql.md` | | Drizzle ORM 작업 | ORM 스키마·쿼리 빌더·관계 정의 | `drizzle-orm.md` + `database.md` | | 프로젝트 구조/설계 | 디렉토리·모듈·레이어 구조 결정 | `architecture.md` | | 인증/인가/보안 | 로그인·토큰·권한·암호화 | `security.md` + `api-design.md` | | 테스트 작성 | 단위·통합·E2E 서버 테스트 | `testing.md` | | 로깅/모니터링 | 로그 수집·메트릭·알럿·트레이싱 | `observability.md` | | 에러 처리 | 예외 설계·에러 응답·복구 전략 | `error-handling.md` + `observability.md` | | 성능 최적화 | 응답 시간·쓰루풋·병목 해결 | `performance.md` + `nodejs-internals.md` + `postgresql.md` | | 배포/인프라 | CI/CD·컨테이너·환경 설정 | `deployment.md` + `architecture.md` + `observability.md` | | 시스템 설계 | 대규모 아키텍처·서비스 간 통신 | `system-design.md` + `distributed-systems.md` + `microservices.md` | | 캐싱 | Redis·캐시 전략·무효화 정책 | `caching.md` + `performance.md` | | 메시지 큐 | 비동기 처리·이벤트·BullMQ | `message-queues.md` + `distri
Use when managing AI Hub account, API keys, balance, usage, or API endpoints. Use when user says "AI Hub", "add AI credits", "create API key", "check AI usage", "auto-recharge", "AI Hub endpoint", "AI Hub base URL", "how to use AI Hub API", "LLM API", "AI API", "OpenAI compatible", "Anthropic API", "GPT", "Claude", "Gemini", "DeepSeek", or "Grok" in the context of Zeabur.
skill-sample/ ├─ SKILL.md ⭐ Required: skill entry doc (purpose / usage / examples / deps) ├─ manifest.sample.json ⭐ Recommended: machine-readable metadata (index / validation / autofill) ├─ LICENSE.sample ⭐ Recommended: license & scope (open source / restriction / commercial) ├─ scripts/ │ └─ example-run.py ✅ Runnable example script for quick verification ├─ assets/ │ ├─ example-formatting-guide.md 🧩 Output conventions: layout / structure / style │ └─ example-template.tex 🧩 Templates: quickly generate standardized output └─ references/ 🧩 Knowledge base: methods / guides / best practices ├─ example-ref-structure.md 🧩 Structure reference ├─ example-ref-analysis.md 🧩 Analysis reference └─ example-ref-visuals.md 🧩 Visual reference
More Agent Skills specs Anthropic docs: https://agentskills.io/home
├─ ⭐ Required: YAML Frontmatter (must be at top) │ ├─ ⭐ name : unique skill name, follow naming convention │ └─ ⭐ description : include trigger keywords for matching │ ├─ ✅ Optional: Frontmatter extension fields │ ├─ ✅ license : license identifier │ ├─ ✅ compatibility : runtime constraints when needed │ ├─ ✅ metadata : key-value fields (author/version/source_url...) │ └─ 🧩 allowed-tools : tool whitelist (experimental) │ └─ ✅ Recommended: Markdown body (progressive disclosure) ├─ ✅ Overview / Purpose ├─ ✅ When to use ├─ ✅ Step-by-step ├─ ✅ Inputs / Outputs ├─ ✅ Examples ├─ 🧩 Files & References ├─ 🧩 Edge cases ├─ 🧩 Troubleshooting └─ 🧩 Safety notes
Skill files are scattered across GitHub and communities, difficult to search, and hard to evaluate. SkillWink organizes open-source skills into a searchable, filterable library you can directly download and use.
We provide keyword search, version updates, multi-metric ranking (downloads / likes / comments / updates), and open SKILL.md standards. You can also discuss usage and improvements on skill detail pages.
Quick Start:
Import/download skills (.zip/.skill), then place locally:
~/.claude/skills/ (Claude Code)
~/.codex/skills/ (Codex CLI)
One SKILL.md can be reused across tools.
Everything you need to know: what skills are, how they work, how to find/import them, and how to contribute.
A skill is a reusable capability package, usually including SKILL.md (purpose/IO/how-to) and optional scripts/templates/examples.
Think of it as a plugin playbook + resource bundle for AI assistants/toolchains.
Skills use progressive disclosure: load brief metadata first, load full docs only when needed, then execute by guidance.
This keeps agents lightweight while preserving enough context for complex tasks.
Use these three together:
Note: file size for all methods should be within 10MB.
Typical paths (may vary by local setup):
One SKILL.md can usually be reused across tools.
Yes. Most skills are standardized docs + assets, so they can be reused where format is supported.
Example: retrieval + writing + automation scripts as one workflow.
Some skills come from public GitHub repositories and some are uploaded by SkillWink creators. Always review code before installing and own your security decisions.
Most common reasons:
We try to avoid that. Use ranking + comments to surface better skills:
