{"files":{"SKILL.md":"---\nname: onsched-api-utility\ndescription: \"OnSched API Utility API skill. Use when working with OnSched API Utility for utility. Covers 2 endpoints.\"\nversion: 1.0.0\ngenerator: lapsh\n---\n\n# OnSched API Utility\nAPI version: v1\n\n## Auth\nOAuth2\n\n## Base URL\nhttps://sandbox-api.onsched.com/\n\n## Setup\n1. Configure auth: OAuth2\n2. GET /utility/v1/health/heartbeat -- verify access\n3. Explore available endpoints below\n\n## Endpoints\n2 endpoints across 1 group. See references/api-spec.lap for full details.\n\n### Utility\n| Method | Path | Description |\n|--------|------|-------------|\n| GET | /utility/v1/health/heartbeat |  |\n| GET | /utility/v1/health/threadinfo |  |\n\n## Common Questions\nMatch user requests to endpoints in references/api-spec.lap. Key patterns:\n- \"List all heartbeat?\" -> GET /utility/v1/health/heartbeat\n- \"List all threadinfo?\" -> GET /utility/v1/health/threadinfo\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 OnSched API Utility\n@base https://sandbox-api.onsched.com/\n@version v1\n@auth OAuth2\n@endpoints 2\n@toc utility(2)\n\n@endpoint GET /utility/v1/health/heartbeat\n@returns(200) Success\n\n@endpoint GET /utility/v1/health/threadinfo\n@returns(200) {availableCompletionThreads: int(int32), availableWorkerThreads: int(int32), minCompletionThreads: int(int32), minWorkerThreads: int(int32), maxCompletionThreads: int(int32), maxWorkerThreads: int(int32), occupiedCompletionThreads: int(int32), occupiedWorkerThreads: int(int32)} # Success\n\n@end\n"}}