alapi
Skill9 starsChanged 9 months agoMITView on GitHub
Comprehensive ALAPI skill covering the full bundled ALAPI OpenAPI catalog. Use when the user mentions ALAPI, alapi, ALAPI_TOKEN, openapi.json, or an ALAPI path like /api/..., or asks to find which ALAPI API matches a business need, choose between similar ALAPI endpoints, explain request fields, prepare or execute a request, or troubleshoot an ALAPI response. Covers inspirational content, articles, news and hotlists, AI chat/translation/NLP, OCR and document recognition, weather and calendar data, IP/phone/ID/domain/ICP/enterprise lookup and verification, finance/exchange/gold/oil/crypto market data, music/media/video/TTS, URL/QR tools, and related utility APIs.
In this repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- android-app-publisherSkill
- awesome-docsSkill
- calib-pattern-generatorSkill
- deep-thinkSkill
- learning-tutorSkill
- proactive-agentSkill
- research-paper-deep-diveSkill
- send-emailSkill
- shell-shortcutsSkill
- technical-explainer-videoSkill
- tutor-generalSkill
- tutor-math-geometrySkill
- week-report-systemSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. About 0 are common, 7 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Use this skill to work against the full ALAPI OpenAPI catalog without hand-parsing the schema each time.
- Very specific: line 15
If the token is missing, tell the user to request one from https://apifox.com/apihub/, then ask them to send it back.
- Distinctive: line 16
After the user sends the token, persist it to the active shell profile, export it in the current session, and avoid echoing it back in logs.
- Very specific: line 17
Use references/intent-router.md first to map a user request to the most likely endpoint with minimal context cost.
- Very specific: line 19
Use scripts/alapi_request.py for real calls instead of rewriting HTTP boilerplate.
- Very specific: line 20
If the OpenAPI source changes, replace references/openapi-source.json and rerun scripts/generate_references.py.
- Very specific: line 25
All endpoints in the bundled OpenAPI spec use POST
- Very specific: line 26
All endpoints use application/json request bodies
- Distinctive: line 33
If the token is missing:
- Distinctive: line 36
Ask the user to send the token
- Distinctive: line 37
After receiving it, persist it based on the active shell:
- Distinctive: line 42
Do not invent or reuse placeholder tokens for real requests.
- Very specific: line 51
Use rg '^### /api/' references/api-catalog.md to jump to a path quickly.
- Distinctive: line 60
When answering a user with this skill:
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
ALAPI
Overview
Use this skill to work against the full ALAPI OpenAPI catalog without hand-parsing the schema each time. The skill bundles the raw OpenAPI source, a generated endpoint catalog, an auth guide, and a reusable request script.
Workflow
- Confirm whether
ALAPI_TOKENis available. - If the token is missing, tell the user to request one from
https://apifox.com/apihub/, then ask them to send it back. - After the user sends the token, persist it to the active shell profile, export it in the current session, and avoid echoing it back in logs.
- Use
references/intent-router.mdfirst to map a user request to the most likely endpoint with minimal context cost. - Open
references/api-catalog.mdonly for the exact endpoint you selected. - Use
scripts/alapi_request.pyfor real calls instead of rewriting HTTP boilerplate. - If the OpenAPI source changes, replace
references/openapi-source.jsonand rerunscripts/generate_references.py.
Authentication
- ALAPI uses header auth:
token: $ALAPI_TOKEN - All endpoints in the bundled OpenAPI spec use
POST - All endpoints use
application/jsonrequest bodies - Base URL:
https://v3.alapi.cn
Token Handling
Run printenv ALAPI_TOKEN first.
If the token is missing:
- Tell the user to申请或管理 ALAPI token at
https://apifox.com/apihub/ - Ask the user to send the token
- After receiving it, persist it based on the active shell:
zsh: appendexport ALAPI_TOKEN='...'to~/.zshrcbash: appendexport ALAPI_TOKEN='...'to~/.bashrc
- Also export it in the current shell before making API calls
Do not invent or reuse placeholder tokens for real requests.
References
references/auth-and-usage.md: auth model, calling conventions, error-handling checklistreferences/intent-router.md: lowest-cost full routing table from common intent to endpointreferences/api-catalog.md: endpoint-by-endpoint reference including purpose and request schemareferences/openapi-source.json: bundled ALAPI OpenAPI source of truth
Use rg '^### /api/' references/api-catalog.md to jump to a path quickly.
Scripts
scripts/alapi_request.py: send authenticated ALAPI requests with JSON bodiesscripts/generate_references.py: regenerate the reference markdown files fromreferences/openapi-source.json
Response Discipline
When answering a user with this skill:
- State the selected endpoint path explicitly
- Explain why that endpoint matches the request
- Show the required JSON body fields
- Mention that auth is via
ALAPI_TOKEN - Summarize the API response instead of dumping raw JSON unless the user asks for the full payload
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

