API Designer
Jeffallan/claude-skills
Designs REST and GraphQL APIs from resource modeling to an OpenAPI 3.1 contract, with versioning, pagination and RFC 7807 error handling.
Reference for calling existing HMIS REST APIs. An agent skill from hmislk/hmis.
Install API Usage
$ npx skills add hmislk/hmis --skill api-usage -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install hmislk/hmis api-usage --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/hmislk/hmis.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/api-usage .claude/skills/api-usage && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "api-usage" agent skill from https://github.com/hmislk/hmis/tree/development/.claude/skills/api-usage into .claude/skills/api-usage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "api-usage", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/hmislk/hmis/tree/development/.claude/skills/api-usageType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add hmislk/hmis --skill api-usage -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install hmislk/hmis api-usage --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hmislk/hmis.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/api-usage .agents/skills/api-usage && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "api-usage" agent skill from https://github.com/hmislk/hmis/tree/development/.claude/skills/api-usage into .agents/skills/api-usage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "api-usage", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add hmislk/hmis --skill api-usage -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install hmislk/hmis api-usage --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hmislk/hmis.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/api-usage .cursor/skills/api-usage && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "api-usage" agent skill from https://github.com/hmislk/hmis/tree/development/.claude/skills/api-usage into .cursor/skills/api-usage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "api-usage", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/hmislk/hmis.git --path .claude/skills/api-usage--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add hmislk/hmis --skill api-usage -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install hmislk/hmis api-usage --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hmislk/hmis.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/api-usage .gemini/skills/api-usage && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "api-usage" agent skill from https://github.com/hmislk/hmis/tree/development/.claude/skills/api-usage into .gemini/skills/api-usage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "api-usage", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install hmislk/hmis api-usageInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add hmislk/hmis --skill api-usage -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/hmislk/hmis.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/api-usage .github/skills/api-usage && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "api-usage" agent skill from https://github.com/hmislk/hmis/tree/development/.claude/skills/api-usage into .github/skills/api-usage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "api-usage", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add hmislk/hmis --skill api-usage -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install hmislk/hmis api-usage --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hmislk/hmis.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/api-usage .opencode/skills/api-usage && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "api-usage" agent skill from https://github.com/hmislk/hmis/tree/development/.claude/skills/api-usage into .opencode/skills/api-usage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "api-usage", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
api-usage- GitHub stars
- 236
- Token cost
- ~1.1k tokens
- SKILL.md length
- 462 words
- Files
- 1
- Skills in repo
- 33
- Repo updated
- First seen
- Licence
- GPL-3.0
At a glance
Reference for calling existing HMIS REST APIs. An agent skill from hmislk/hmis.
- Consuming/invoking an HMIS endpoint — verifying data via API during issue investigation
- SKILL.md covers When This Applies, Auth Headers, Response Envelope and Module Index, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Writing a debug curl/script call
What it does
API Usage is an agent skill from hmislk/hmis. Reference for calling existing HMIS REST APIs. Use when consuming/invoking an HMIS endpoint — verifying data via API during issue investigation, writing a debug curl/script call, or checking an endpoint's request/response shape before writing a caller. Covers auth header conventions, the standard response envelope, and the developerdocs/api/using-apis/ module index. For building or extending an endpoint, use api-development instead.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Backend & APIs, covering REST APIs. The repository describes itself as: This is an Open Source Java EE based Hospital Information Management System. The licence is GPL-3.0.
When your agent uses it
- Consuming/invoking an HMIS endpoint — verifying data via API during issue investigation
- Writing a debug curl/script call
- Checking an endpoints request/response shape before writing a caller
Example prompts
- “/api-usage”
What it can do on your machine
Read from SKILL.md and the folder at commit 1820c4a. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are json).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
API Usage loads about 1.1k tokens when it runs. Until then it costs about 112 tokens; SKILL.md has 462 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from hmislk/hmis at commit 1820c4a, republished under its GPL-3.0 licence (© hmislk). 462 words, ~1,089 tokens.
Download SKILL.mdSave it as
.claude/skills/api-usage/SKILL.md (or your agent's skills folder).- name
- api-usage
- description
- Reference for calling existing HMIS REST APIs. Use when consuming/invoking an HMIS endpoint — verifying data via API during issue investigation, writing a debug curl/script call, or checking an endpoint's request/response shape before writing a caller. Covers auth header conventions, the standard response envelope, and the developer_docs/api/using-apis/ module index. For building or extending an endpoint, use api-development instead.
- user-invocable
- true
HMIS API Usage Guide
When This Applies
Any time you need to call an HMIS REST endpoint that already exists — not create one:
- Verifying a bill/payment/balance via the read-only APIs while investigating an issue
- Writing a one-off curl/script call to check data during debugging
- Confirming an endpoint's request/response shape before writing a caller against it
- Wiring an API call into the in-app AI Chat tool-calling flow (
AnthropicApiService)
If you're instead building or extending an endpoint (new @Path class or new method on one),
use the api-development skill — this one has no implementation detail.
Auth Headers
Every request needs an auth header. Which one depends on the module — check the table below before guessing:
| Header | Used by |
|---|---|
Finance | Default for most modules (bills, balances, pharmacy, inward, users, etc.) |
Token | Channel/booking appointments, consultant management |
Config | Reading/updating ConfigOption application settings |
FHIR | FHIR Patient resource endpoints |
| Custom (URL/JSON/Basic) | LIMS lab middleware |
| none | Membership scheme registration/payment (public) |
Send the key as the exact header name above, e.g. Finance: <apiKey>. A 401 Not a valid key
response means the key is invalid, retired, or expired (ApiKey.dateOfExpiary).
Response Envelope
Standard endpoints wrap responses the same way regardless of module:
{"status":"success","code":200,"data":{...}}
{"status":"error","code":400,"message":"..."}POST duplicate-detection endpoints return a bare (non-wrapped) shape instead:
{"status":"already_exists","id":123,"name":"..."}Always check status first, not just HTTP status code — some error conditions still return
HTTP 200 with "status":"error" in the body.
Module Index
developer_docs/api/using-apis/ has one self-contained reference file per module: base path,
auth header, request/response shapes, error codes. Load only the file for the module you
need — don't read the whole directory. Start from
developer_docs/api/using-apis/README.md
for the full, current table (module, file, auth header); it's kept up to date as new API docs
are added, so treat it as the source of truth rather than duplicating the list here.
If you're unsure which module owns the data you need, check README.md's table first — several
files disambiguate related-sounding endpoints (e.g. API_ADMISSION_DETAILS.md is a consolidated
index of which admission-related API to call).
Show full SKILL.md (140 more words)Show less
Verifying Payments and Balances
A common task during issue investigation: confirm a bill's payments produced the correct balance
updates. Don't hand-roll this — follow
API_TESTING_WORKFLOWS.md:
fetch the bill (/api/costing_data/...), pull the matching balance-history endpoint per payment
method (drawer/deposit/staff-welfare/agent), and assert after == before + transactionValue
(with float tolerance, since credit-company payments have no history endpoint and refunds/
cancellations use negative or reversing entries). This same file also covers batch verification
and common troubleshooting symptoms (case-sensitive bill numbers, empty payments[] on
transfer/issue bills, etc.).
General Troubleshooting
| Symptom | Cause / Fix |
|---|---|
401 Not a valid key | Auth key invalid, retired user, or expired — check ApiKey.dateOfExpiary |
404 / entity not found | IDs and bill numbers are often case-sensitive; confirm exact format |
200 with "status":"error" | Check message, not just HTTP status — see Response Envelope above |
| Numeric fields don't match exactly | Use tolerance (abs(a - b) < 0.01) for currency comparisons, not == |
© hmislk, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/api-usage of hmislk/hmis.
Open the folder on GitHubat commit 1820c4a
Compare with similar skills
API Usage next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| API Usage this skillhmislk/hmis | 236 | — | ~1.1k | Automated safety check: Pass | GPL-3.0 | |
| API DesignerJeffallan/claude-skills | 12k | 2 repos | ~2k | Automated safety check: Pass | MIT | |
| Paperclippaperclipai/paperclip | 98k | — | ~9.6k | Automated safety check: Pass | MIT | |
| Nodejs Backend Patternsever-works/ever-works | 158 | 17 repos | ~4k | Automated safety check: Pass | AGPL-3.0 | |
| OpenAPI to MCP Servermcp-use/mcp-use | 11k | — | ~5.2k | Automated safety check: Pass | Apache-2.0 | |
| Use Yaakmountain-loop/yaak | 19k | — | ~1.9k | Automated safety check: Pass | MIT |
Similar skills
Paperclip
paperclipai/paperclip
Interact with the Paperclip control plane API for task coordination and governance.
Nodejs Backend Patterns
ever-works/ever-works
Build production-ready Node.js backend services with Express/Fastify, implementing middleware patterns, error handling, authentication, database integration, and API design best practices.
OpenAPI to MCP Server
mcp-use/mcp-use
Turns an OpenAPI or Swagger spec into an MCP server with the mcp-use TypeScript SDK, mapping each operation to a tool, wiring auth, testing and deploying.
Use Yaak
mountain-loop/yaak
A skill your agent uses when the user mentions Yaak, a Yaak workspace, or the yaak command, or asks to call, hit, or smoke test HTTP/REST endpoints, save or organize API requests for reuse or manual…
RuView CLI, API and WASM
ruvnet/RuView
Covers the RuView `wifi-densepose` command line binary, its Axum REST API and the WebAssembly builds for browsers and ESP32, for embedding or scripting RuView.
More from hmislk/hmis
All 33 skills in this repoApp Configuration
hmislk/hmis
Application configuration options reference for the HMIS project.
Caveman
hmislk/hmis
Ultra-compressed communication mode. An agent skill from hmislk/hmis.
Database Guide
hmislk/hmis
MySQL database development guide for the HMIS project. An agent skill from hmislk/hmis.
Demo Video
hmislk/hmis
A skill your agent uses when asked to make a demo, training, how-to or tutorial video with sound or voice-over showing an HMIS function or configuration (e.g.
Deploy QA
hmislk/hmis
Sync development into QA/testing environment branches (QA1-QA4, local RH staging) via PR + merge on GitHub.
Dev Issue
hmislk/hmis
Run a GitHub issue through its full lifecycle end-to-end: investigate, discuss the approach, gather test context (department/data), implement, rebuild + local redeploy, verify with Playwright and…
Related
Categories
Questions about API Usage
What does API Usage do?
Reference for calling existing HMIS REST APIs. An agent skill from hmislk/hmis. API Usage is an agent skill from hmislk/hmis. Reference for calling existing HMIS REST APIs.
When should I use API Usage?
API Usage fits situations like: consuming/invoking an HMIS endpoint — verifying data via API during issue investigation; writing a debug curl/script call; checking an endpoints request/response shape before writing a caller.
How do I install API Usage in Claude Code?
Run `npx skills add hmislk/hmis --skill api-usage -a claude-code`. Or copy the skill folder (.claude/skills/api-usage in hmislk/hmis) into .claude/skills/api-usage in your project. Claude Code loads it when a task matches its description.
How do I install API Usage in Codex?
Run `npx skills add hmislk/hmis --skill api-usage -a codex`. Or copy the skill folder (.claude/skills/api-usage in hmislk/hmis) into .agents/skills/api-usage in your project. Codex loads it when a task matches its description.
Can I use API Usage in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add hmislk/hmis --skill api-usage -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/api-usage, .gemini/skills/api-usage, .github/skills/api-usage and .opencode/skills/api-usage in your project.
What does API Usage need to run?
SKILL.md names no scripts, command-line tools or credentials: API Usage is instructions for the agent only.
Does API Usage access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is API Usage safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does API Usage use?
API Usage is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does API Usage use?
About 1.1k tokens (SKILL.md is roughly 4.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to API Usage?
Skills that share tags, products or a category with API Usage: API Designer (Jeffallan/claude-skills, 12k stars), Paperclip (paperclipai/paperclip, 98k stars), Nodejs Backend Patterns (ever-works/ever-works, 158 stars) and OpenAPI to MCP Server (mcp-use/mcp-use, 11k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains API Usage?
hmislk (a GitHub organization) maintains it in hmislk/hmis, which has 236 GitHub stars. The repository holds 33 skills in this directory. The repository was last updated on October 7, 2026.
Source: hmislk/hmis on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.