{"files":{"SKILL.md":"---\nname: archive-api\ndescription: \"Archive API skill. Use when working with Archive for {year}. Covers 1 endpoint.\"\nversion: 1.0.0\ngenerator: lapsh\n---\n\n# Archive API\nAPI version: 1.0.0\n\n## Auth\nApiKey api-key in query\n\n## Base URL\nhttp://api.nytimes.com/svc/archive/v1\n\n## Setup\n1. Set your API key in the appropriate header\n2. GET /{year}/{month}.json -- archive api\n3. Explore available endpoints below\n\n## Endpoints\n1 endpoint across 1 group. See references/api-spec.lap for full details.\n\n### {year}\n| Method | Path | Description |\n|--------|------|-------------|\n| GET | /{year}/{month}.json | Archive API |\n\n## Common Questions\nMatch user requests to endpoints in references/api-spec.lap. Key patterns:\n- \"Get {year} details?\" -> GET /{year}/{month}.json\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\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 Archive API\n@base http://api.nytimes.com/svc/archive/v1\n@version 1.0.0\n@auth ApiKey api-key in query\n@endpoints 1\n@toc {year}(1)\n\n@endpoint GET /{year}/{month}.json\n@desc Archive API\n@required {year: any # The year (e.g. 2016)., month: any # The month number (e.g. 1 for January).}\n@returns(200) The docs requested.\n\n@end\n"}}