Pontx Hub
Use pontx-hub as the authoritative interface to the curated API catalog. Keep
API metadata out of long-lived context by searching and loading only the
product, endpoint, or schema needed for the current task.
This universal Skill owns catalog-wide discovery and request safety. A
pontx-<apiSlug> product Skill adds only provider-specific integration flows,
best practices, and caveats; it does not replace the current PontxSpec.
Workflow
Search before choosing an API. Natural-language capability, request, and
response questions are supported:
pontx-hub search "<capability>" --json
pontx-hub search "创建任务的入参" --locale zh --json
pontx-hub search "返回 dueDate 的接口" --locale zh --json
Narrow the result type when useful:
pontx-hub search "<field-or-model>" --type schema --json
Inspect the selected stable resource ID:
pontx-hub show endpoint:<api>/<endpoint>
pontx-hub show schema:<api>/<schema>
When provider-specific guidance would help, check the available product
Skills. Explain the benefit and install one only when the user requests or
approves the installation:
pontx-hub skill list
pontx-hub skill install <apiSlug>
Use that product Skill for provider-specific sequencing and caveats, then
return to pontx-hub show for current Endpoint, Schema, and auth details.
For an Endpoint, build and review the exact request without sending it:
pontx-hub <api-collection> preview <api-name> --parameter value --body '<json>'
pontx-hub <api-collection> preview <controller> <api-name> --parameter value --body '<json>'
For GET or HEAD, call only when the user requested execution:
pontx-hub <api-collection> call <api-name> --parameter value
pontx-hub <api-collection> call <controller> <api-name> --parameter value
For POST, PUT, PATCH, or DELETE, show the dry-run result and obtain explicit
user confirmation. Then pass --yes without changing parameters:
pontx-hub <api-collection> call <controller> <api-name> --parameter value --body '<json>' --yes
Generate application code after the request shape is verified. Use the
package and exports reported by the Hub instead of inventing a package or
pinning a stale version:
pontx-hub sdk <api>
pnpm add @pontx/<apiSlug>
Safety
- Never infer approval for a write from a request to inspect, explain, or
preview an API.
- Never print, echo, log, or place credentials directly in command arguments.
- Read credentials from the environment variables named by
show.
- Never call an arbitrary URL or an Endpoint outside the Hub catalog.
- Never treat a product Skill as the source for Endpoint, parameter, Schema,
authentication, package-version, or server metadata; inspect the current
PontxSpec through the Hub.
- Never bypass the separate
preview step for a mutation.
- Treat a changed parameter, body, server, or Endpoint as a new request that
requires another dry-run and confirmation.
- Read references/auth-and-safety.md when
configuring credentials, diagnosing authentication, or executing a mutation.
Output
Prefer --json when consuming CLI output programmatically. Preserve the CLI
exit code and machine-readable error code when reporting failures. Use the
result's match.mode and match.fields to explain whether product, parameter,
request, response, schema, or property metadata produced the match. Use the
Endpoint's published @pontx/<apiSlug> package when generating application
code.
1---2name: pontx-hub3description: Discover, compare, inspect, preview, call, and integrate curated public APIs with Pontx Hub. Use whenever a user asks to find a public API for a task, identify which Endpoint or Schema returns a field, inspect PontxSpec or OpenAPI documentation, install provider-specific Skills, preview a request safely, confirm a mutation, or generate code with a published Pontx SDK.4metadata:5 source: https://skillmd.com/skills/pontjs/pontx-hub6---78# Pontx Hub910Use `pontx-hub` as the authoritative interface to the curated API catalog. Keep11API metadata out of long-lived context by searching and loading only the12product, endpoint, or schema needed for the current task.1314This universal Skill owns catalog-wide discovery and request safety. A15`pontx-<apiSlug>` product Skill adds only provider-specific integration flows,16best practices, and caveats; it does not replace the current PontxSpec.1718## Workflow19201. Search before choosing an API. Natural-language capability, request, and21 response questions are supported:2223 ```bash24 pontx-hub search "<capability>" --json25 pontx-hub search "创建任务的入参" --locale zh --json26 pontx-hub search "返回 dueDate 的接口" --locale zh --json27 ```2829 Narrow the result type when useful:3031 ```bash32 pontx-hub search "<field-or-model>" --type schema --json33 ```34352. Inspect the selected stable resource ID:3637 ```bash38 pontx-hub show endpoint:<api>/<endpoint>39 pontx-hub show schema:<api>/<schema>40 ```41423. When provider-specific guidance would help, check the available product43 Skills. Explain the benefit and install one only when the user requests or44 approves the installation:4546 ```bash47 pontx-hub skill list48 pontx-hub skill install <apiSlug>49 ```5051 Use that product Skill for provider-specific sequencing and caveats, then52 return to `pontx-hub show` for current Endpoint, Schema, and auth details.53544. For an Endpoint, build and review the exact request without sending it:5556 ```bash57 pontx-hub <api-collection> preview <api-name> --parameter value --body '<json>'58 pontx-hub <api-collection> preview <controller> <api-name> --parameter value --body '<json>'59 ```60615. For GET or HEAD, call only when the user requested execution:6263 ```bash64 pontx-hub <api-collection> call <api-name> --parameter value65 pontx-hub <api-collection> call <controller> <api-name> --parameter value66 ```67686. For POST, PUT, PATCH, or DELETE, show the dry-run result and obtain explicit69 user confirmation. Then pass `--yes` without changing parameters:7071 ```bash72 pontx-hub <api-collection> call <controller> <api-name> --parameter value --body '<json>' --yes73 ```74757. Generate application code after the request shape is verified. Use the76 package and exports reported by the Hub instead of inventing a package or77 pinning a stale version:7879 ```bash80 pontx-hub sdk <api>81 pnpm add @pontx/<apiSlug>82 ```8384## Safety8586- Never infer approval for a write from a request to inspect, explain, or87 preview an API.88- Never print, echo, log, or place credentials directly in command arguments.89- Read credentials from the environment variables named by `show`.90- Never call an arbitrary URL or an Endpoint outside the Hub catalog.91- Never treat a product Skill as the source for Endpoint, parameter, Schema,92 authentication, package-version, or server metadata; inspect the current93 PontxSpec through the Hub.94- Never bypass the separate `preview` step for a mutation.95- Treat a changed parameter, body, server, or Endpoint as a new request that96 requires another dry-run and confirmation.97- Read [references/auth-and-safety.md](references/auth-and-safety.md) when98 configuring credentials, diagnosing authentication, or executing a mutation.99100## Output101102Prefer `--json` when consuming CLI output programmatically. Preserve the CLI103exit code and machine-readable error code when reporting failures. Use the104result's `match.mode` and `match.fields` to explain whether product, parameter,105request, response, schema, or property metadata produced the match. Use the106Endpoint's published `@pontx/<apiSlug>` package when generating application107code.