菜单
Reference for the Lidarr v1 REST API. Use when adding, debugging, or extending Lidarr API calls (new endpoints on LidarrClient, query/command payloads, response schemas).
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Launch, build, run, start, screenshot, or smoke-test the Librariarr Next.js webapp end-to-end. Use when asked to run librariarr, bring up the dev stack, take a screenshot of the dashboard or any UI page, verify a change in the running app, or check that the app boots cleanly.
Generate a new Next.js API route with project boilerplate (auth, validation, sanitize, Prisma). Use when creating new API endpoints.
Generate an integration test for an API route with all required mocks and boilerplate. Use when creating tests for API endpoints.
Quick reference for all Librariarr project conventions and patterns. Consult when writing or reviewing code to verify correct patterns.
Create a Prisma migration file for schema changes. Required for production — db push only works in dev. Use after modifying schema.prisma.
Scaffold a complete new feature end-to-end (Prisma model, migration, schemas, API routes, tests). Use for new CRUD resources or features that span multiple layers.
| name | lidarr-api |
| description | Reference for the Lidarr v1 REST API. Use when adding, debugging, or extending Lidarr API calls (new endpoints on LidarrClient, query/command payloads, response schemas). |
Fetch the Lidarr v1 OpenAPI spec from:
https://raw.githubusercontent.com/lidarr/Lidarr/master/src/Lidarr.Api.V1/openapi.json
All endpoints are under /api/v1/* (note: v1, not v3 like Radarr/Sonarr). Auth is the X-Api-Key: <apiKey> header.
The spec is large — do not load it whole into context. Use curl + jq to extract only what you need:
curl -s <url> | jq '.paths | keys'curl -s <url> | jq '.paths."/api/v1/artist"'curl -s <url> | jq '.components.schemas.ArtistResource'curl -s <url> | jq '[.paths | to_entries[] | select(.value | .. | .tags? // [] | index("Artist")) | .key]'