audit-discoverability
Audit whether agents would find and pick an AI plugin or MCP server when a user asks: how its listing and MCP tool descriptions answer target prompts, with a labelled simulated pick against rivals. Use when asked to audit a plugin or MCP server, when agents ignore a plugin, to check prompts people should use it for against rivals, for AEO for plugins, to grade a pasted tool list or tools against a rival's, to check whether an app can be reached in a country, or to fix MCP tool descriptions and annotations such as readOnlyHint. Not for writing store copy.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 1.6k
- Forks
- 491
01 前言 Front Matter
- name
- audit-discoverability
- license
- MIT
- description
- Audit whether agents would find and pick an AI plugin or MCP server when a user asks: how its listing and MCP tool descriptions answer target prompts, with a labelled simulated pick against rivals. Use when asked to audit a plugin or MCP server, when agents ignore a plugin, to check prompts people should use it for against rivals, for AEO for plugins, to grade a pasted tool list or tools against a rival's, to check whether an app can be reached in a country, or to fix MCP tool descriptions and annotations such as readOnlyHint. Not for writing store copy.
- compatibility
- Needs network access, and one of Node.js for npx, the OpenApps MCP server or a tool that fetches URLs.
02 资源文件 8
- 许可证LICENSE.txt1.1 KB
- 参考文档references/api.md1.5 KB
- 参考文档references/cli.md2.0 KB
- 参考文档references/data.md4.5 KB
- 参考文档references/listing.md2.5 KB
- 参考文档references/mcp.md2.2 KB
- 参考文档references/simulated-pick.md4.5 KB
- 参考文档references/tools.md4.4 KB
03 SKILL.md 正文
Audit discoverability
A question such as "how do I figure out what's wrong?" or "what do I need?" is a request to run these steps on this repo, so run them instead of explaining them.
Read at each step
| Step | Read |
|---|---|
| 1 | .agents/plugin-stack.md if present, references/data.md |
| 1, 3 | references/listing.md |
| 2, 4 | references/tools.md |
| 5 | references/simulated-pick.md |
Steps
- Fix the scope. The plugin, 5-10 target prompts and 3-5 competitors. Done when each is named and at least half the prompts aren't drafted, or the report says coverage is circular.
- Can it be reached at all? Done when the listing, the server and the target country are each marked, with
checked_atprinted beside any stored status. A failed mark is fix #1, and every later step is labelledconditional on fixing reachability. - Audit the listing's words. Done when every target prompt is marked covered or missed, with the competitors that cover it.
- Audit the tools. Read them from
mcp_toolset_get, the repo's server code, ortools/listoutput the user pastes. Done when every tool has a verdict on saying what it does, when to use it, and its annotations. With none of the three, say so in the report and go to step 5. - Run the simulated pick. Done when each prompt has a pick, its reason and a run count, labelled as a simulation.
- Report. Ranked fixes. Done when every fix names a target prompt it should help and every number has its date and basis. If
.agents/plugin-stack.mdexists, addaudit-discoverability: <today>, top fix: <fix>under Runs without asking, in your own words.
Report order
- Any
Degraded:lines, thenThis simulation is not informative for this setif a control failed. Baseline:thebestchart place from the plugin'slistings_searchrow, withmeta.as_of, so the next run has something to compare.- Fixes, ranked: reachability, tool text that risks store review, prompts the plugin won and should have lost, then missed prompts, sourced ones before drafted ones. A tool fix gives the replacement text. A listing fix names the missing words and the field, and leaves the copy to
optimize-listing. With no listing yet, namesubmit-plugin. - Evidence: the coverage line, the tool verdicts, the picks with their label, the real-assistant line and what the simulation can't tell you.
04 同仓库更多 Skills
worktable-review-with-annotations
Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.
worktable-find-and-synthesize-context
Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.
worktable-create-or-update-docs
Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.
worktable-create-or-manage-records
Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.
worktable-create-or-manage-interactive-html
Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.
worktable-collaborate-threads
Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.