{"files":{"SKILL.md":"---\nname: debian-code-search\ndescription: \"Debian Code Search API skill. Use when working with Debian Code Search for search, searchperpackage. Covers 2 endpoints.\"\nversion: 1.0.0\ngenerator: lapsh\n---\n\n# Debian Code Search\nAPI version: 1.4.0\n\n## Auth\nApiKey x-dcs-apikey in header\n\n## Base URL\nhttps://codesearch.debian.net/api/v1\n\n## Setup\n1. Set your API key in the appropriate header\n2. GET /search -- searches through source code\n3. Explore available endpoints below\n\n## Endpoints\n2 endpoints across 2 groups. See references/api-spec.lap for full details.\n\n### Search\n| Method | Path | Description |\n|--------|------|-------------|\n| GET | /search | Searches through source code |\n\n### Searchperpackage\n| Method | Path | Description |\n|--------|------|-------------|\n| GET | /searchperpackage | Like /search, but aggregates per package |\n\n## Common Questions\nMatch user requests to endpoints in references/api-spec.lap. Key patterns:\n- \"Search search?\" -> GET /search\n- \"Search searchperpackage?\" -> GET /searchperpackage\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 Debian Code Search\n@base https://codesearch.debian.net/api/v1\n@version 1.4.0\n@auth ApiKey x-dcs-apikey in header\n@endpoints 2\n@toc search(1), searchperpackage(1)\n\n@group search\n@endpoint GET /search\n@desc Searches through source code\n@required {query: str # The search query, for example `who knows...` (literal) or `who knows\\.\\.\\.` (regular expression). See https://codesearch.debian.net/faq for more details about which keywords are supported. The regular expression flavor is RE2, see https://github.com/google/re2/blob/master/doc/syntax.txt}\n@optional {match_mode: str(literal/regexp)=regexp # Whether the query is to be interpreted as a literal (`literal`) instead of as an RE2 regular expression (`regexp`). Literal searches are faster and do not require escaping special characters, regular expression searches are more powerful.}\n@returns(200) All search results\n@errors {403: The x-dcs-apikey header was either not set at all, or contained an invalid (no longer valid?) API key. Please see https://codesearch.debian.net/apikeys/ for obtaining a key.}\n\n@endgroup\n\n@group searchperpackage\n@endpoint GET /searchperpackage\n@desc Like /search, but aggregates per package\n@required {query: str # The search query, for example `who knows...` (literal) or `who knows\\.\\.\\.` (regular expression). See https://codesearch.debian.net/faq for more details about which keywords are supported. The regular expression flavor is RE2, see https://github.com/google/re2/blob/master/doc/syntax.txt}\n@optional {match_mode: str(literal/regexp)=regexp # Whether the query is to be interpreted as a literal (`literal`) instead of as an RE2 regular expression (`regexp`). Literal searches are faster and do not require escaping special characters, regular expression searches are more powerful.}\n@returns(200) All search results\n@errors {403: The x-dcs-apikey header was either not set at all, or contained an invalid (no longer valid?) API key. Please see https://codesearch.debian.net/apikeys/ for obtaining a key.}\n\n@endgroup\n\n@end\n"}}