菜单
Search for an API or service that can perform a task. Use when the user asks to find, search for, compare, price, or choose an API, provider, integration, or paid service — including phrasings like "is there an API for", "what's the cheapest way to", or "find me a service that".
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/nitrographtech/claude-plugins --skill discover-services命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Use Nitrograph when the user asks to find, search for, compare, price, or inspect an API or service that can perform a task — including paid and agent-payable services on x402, MPP, and similar rails. Also covers reading a service's call card before calling it, and reporting whether a call worked.
Use Nitrograph when the user asks to find, search, query, inspect, compare, or call an API/service for a task. Applies to agent service discovery, MCP tools, x402/MPP services, the Nitrograph TypeScript harness, raw HTTP API use, and reporting service outcomes.
正在显示 SKILL.md
| name | discover-services |
| description | Search for an API or service that can perform a task. Use when the user asks to find, search for, compare, price, or choose an API, provider, integration, or paid service — including phrasings like "is there an API for", "what's the cheapest way to", or "find me a service that". |
Converted from the /discover command. OpenAI plugins have no slash commands,
so the same behaviour is a skill the model triggers from intent.
nitrograph_discover in
natural language — do not reduce it to keywords, the ranking is semantic.filters unless the user explicitly constrained the search by a
payment rail, a category, a price ceiling, or a trust floor.related_results separate and clearly lower-confidence. Do not promote
them into the main recommendations.has_more and the user wants more options, call
nitrograph_discover again with the same query and offset advanced past
what was already shown. Do not repeat the identical call.slug and call
nitrograph_service_detail, passing the user's original task as task so
the endpoint options are ranked for it.If the user (or the model on the user's behalf) actually calls one of these
services afterwards, record what happened with nitrograph_report_outcome.
That is what keeps the rankings honest for the next search. Report only real
successes and real provider failures, with a generalized diagnosis — never raw
request or response data.
If a search reports that the limit for the current window has been reached, say so plainly and stop. Do not retry in a loop and do not look for a way around it.