Skip to content
Skills Library
Programming · Tool integration

alapi

/alapi

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

Licence
MIT
Last repository change
23.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
8
Scripts
2
HTML comments
0
URLs in SKILL.md
3
Deprecation

No signals detected. Repository changed on 23.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • 2 scripts in this package. Review them before installing, as Claude may execute them.

Scripts: scripts/alapi_request.py, scripts/generate_references.py

What it does and when to use it

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

Original author description

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

How it works

  1. Overview
  2. Workflow
  3. Authentication
  4. Token Handling
  5. References
  6. Scripts
  7. Response Discipline
Original SKILL.md headings · 63 lines, 378 words
SKILL.md preview
---
name: alapi
description: 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.
---

# 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

1. Confirm whether `ALAPI_TOKEN` is available.
2. If the token is missing, tell the user to request one from `https://apifox.com/apihub/`, then ask them to send it back.
3. 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.
4. Use `references/intent-router.md` first to map a user request to the most likely endpoint with minimal context cost.
5. Open `references/api-catalog.md` only for the exact endpoint you selected.
6. Use `scripts/alapi_request.py` for real calls instead of rewriting HTTP boilerplate.
7. If the OpenAPI source changes, replace `references/openapi-source.json` and rerun `scripts/generate_references.py`.

## Authentication

- ALAPI uses header auth: `token: $ALAPI_TOKEN`
- All endpoints in the bundled OpenAPI spec use `POST`
- All endpoints use `application/json` request 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`: append `export ALAPI_TOKEN='...'` to `~/.zshrc`
  - `bash`: append `export 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 checklist
- `references/intent-router.md`: lowest-cost full routing table from common intent to endpoint
- `references/api-catalog.md`: endpoint-by-endpoint reference including purpose and request schema
- `references/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 bodies
- `scripts/generate_references.py`: regenerate the reference markdown files from `references/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
Files in this package (8)
  • SKILL.md 3 KB
  • agents/openai.yaml 1 KB
  • references/api-catalog.md 392 KB
  • references/auth-and-usage.md 1 KB
  • references/intent-router.md 19 KB
  • references/openapi-source.json 401 KB
  • scripts/alapi_request.py 3 KB
  • scripts/generate_references.py 11 KB

Versions

The database has no other skills named alapi.

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version c68c2dd0a039 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100rc-openapi
    Creates or updates an OpenAPI specification by discovering the project's HTTP endpoints, request schemas, and response models from source. Use to keep an openapi.yaml in sync after API changes, or to generate a spec for an existing service. Do not use for Postman collections…
  • 90asodev-public-api
    Use when the user asks about ASO.dev public APIs, Developer API, Partners API, OpenAPI docs, API keys, integration endpoints, request/response schemas, or how an external system should call ASO.dev outside the local AI Companion MCP.
  • 100rest-api-design
    Design REST API endpoints with Zod validation and OpenAPI documentation. Use when creating new API routes, validating request/response schemas, or updating API documentation. Activates for endpoint design, schema validation, error handling, and API docs.
  • 100rest-api-design
    Design REST API endpoints with Zod validation and OpenAPI documentation. Use when creating new API routes, validating request/response schemas, or updating API documentation. Activates for endpoint design, schema validation, error handling, and API docs.
  • 100api-design
    Defines REST and GraphQL API contracts including endpoints, request/response schemas, auth flows, and versioning strategy. Use when designing a new API, reviewing an API spec, or when the user mentions API design, OpenAPI, or endpoint contracts.
  • 90backend-api-contract
    Designs REST / GraphQL / RPC endpoints — routes, methods, request/response schemas, error envelope, auth, versioning, pagination. Output: OpenAPI/GraphQL SDL fragment or a markdown spec the backend can implement against. Pulled by the `backend` specialist. TRIGGER: "design the…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.