{"files":{"SKILL.md":"---\nname: top-stories\ndescription: \"Top Stories API skill. Use when working with Top Stories for {section}.{format}. Covers 1 endpoint.\"\nversion: 1.0.0\ngenerator: lapsh\n---\n\n# Top Stories\nAPI version: 2.0.0\n\n## Auth\nApiKey api-key in query\n\n## Base URL\nhttp://api.nytimes.com/svc/topstories/v2\n\n## Setup\n1. Set your API key in the appropriate header\n2. GET /{section}.{format} -- top stories\n3. Explore available endpoints below\n\n## Endpoints\n1 endpoint across 1 group. See references/api-spec.lap for full details.\n\n### {section}.{format}\n| Method | Path | Description |\n|--------|------|-------------|\n| GET | /{section}.{format} | Top Stories |\n\n## Common Questions\nMatch user requests to endpoints in references/api-spec.lap. Key patterns:\n- \"Get {section}.{format} details?\" -> GET /{section}.{format}\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 Top Stories\n@base http://api.nytimes.com/svc/topstories/v2\n@version 2.0.0\n@auth ApiKey api-key in query\n@endpoints 1\n@toc {section}.{format}(1)\n\n@endpoint GET /{section}.{format}\n@desc Top Stories\n@required {section: any # The section the story appears in., format: any # if this is JSONP or JSON}\n@optional {callback: any # The name of the function the API call results will be passed to. Required when using JSONP. This parameter has only one valid value per section. The format is {section_name}TopStoriesCallback.}\n@returns(200) An array of articles\n\n@end\n"}}