{"files":{"SKILL.md":"---\nname: feature-flags-api\ndescription: \"Feature Flags API skill. Use when working with Feature Flags for flags. Covers 2 endpoints.\"\nversion: 1.0.0\ngenerator: lapsh\n---\n\n# Feature Flags API\nAPI version: 1.0.0\n\n## Auth\nApiKey token in query\n\n## Base URL\nNot specified.\n\n## Setup\n1. Set your API key in the appropriate header\n2. GET /flags -- evaluate feature flags (get)\n3. Explore available endpoints below\n\n## Endpoints\n2 endpoints across 1 group. See references/api-spec.lap for full details.\n\n### Flags\n| Method | Path | Description |\n|--------|------|-------------|\n| GET | /flags | Evaluate Feature Flags (GET) |\n| GET | /flags/definitions | Get Feature Flag Definitions |\n\n## Common Questions\nMatch user requests to endpoints in references/api-spec.lap. Key patterns:\n- \"List all flags?\" -> GET /flags\n- \"List all definitions?\" -> GET /flags/definitions\n- \"How to authenticate?\" -> See Auth section above\n\n## Response Tips\n- Check response schemas in references/api-spec.lap for field details\n- Error responses include status codes and descriptions in the spec\n\n## References\n- Full spec: See references/api-spec.lap for complete endpoint details, parameter tables, and response schemas\n\n> Generated from the official API spec by [LAP](https://lap.sh)\n","references/api-spec.lap":"@lap v0.3\n# Machine-readable API spec. Each @endpoint block is one API call.\n@api Feature Flags API\n@version 1.0.0\n@auth ApiKey token in query\n@endpoints 2\n@toc flags(2)\n\n@endpoint GET /flags\n@desc Evaluate Feature Flags (GET)\n@required {token: str # Your project token, context: str # URL-encoded JSON object containing evaluation context with distinct_id (required) and optional device_id and custom_properties object}\n@returns(200) {flags: map} # Success\n@errors {400, 401, 403}\n\n@endpoint GET /flags/definitions\n@desc Get Feature Flag Definitions\n@required {token: str # Your project token}\n@returns(200) {flags: [map]} # Success\n@errors {401, 403}\n\n@end\n"}}