How do I install the Tooling Verify API skill?

Run npx skillmds@latest add andrewdryga/tooling-verify-api in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Tooling Verify API safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Tooling Verify API?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Tooling Verify API free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Tooling Verify API?

AndrewDryga (@andrewdryga) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Tooling Verify API by andrewdryga — Agent Skill

Name: Tooling Verify API
Rating: 4.2 (5 reviews)
Author: AndrewDryga

Tooling Verify API

Confirm a function, argument, option, type, callback, or CLI flag actually exists with the signature you think — before you call it. Use whenever you're about to use an API you're not certain of (a Repo/Ecto/Phoenix/Oban/Swoosh function, a mix task, a dependency's option, a runner/CLI flag), or any time you'd otherwise be guessing. Stops hallucinated functions before they're written.

AndrewDryga Updated Sep 22, 2026

File contents

Verify the API — don't invent it

A hallucinated function/arg/flag costs far more than the lookup. When in doubt, check before you write. Stop at the first rung that gives a definitive answer; you rarely need them all. Local sources beat the web — they're exact for the versions this repo actually uses.

The ladder (highest authority first)

This repo — for our own code. The source IS the spec. Grep for the definition, then read it + its @spec/@doc.
```
rg -n 'def fetch_and_update' portal/apps/emisar/lib/emisar/repo.ex
rg -n 'def (for_user|for_api_key)' portal/apps/emisar/lib/emisar/auth/subject.ex
```
For the in-house building blocks (Repo.fetch/list/fetch_and_update, Subject, Authorizer.build/2, the use Emisar, :query|:schema|:changeset macros), the module under lib/emisar/ is the only authority — don't assume Ecto/Phoenix defaults apply.
Dependency source — deps/ (exact, offline, version-matched). The pinned version's real code, not a guess or a newer doc:
```
rg -n 'def fetch\b|@spec fetch' portal/deps/ecto/lib
rg -n 'def (stream|assign_async)\b' portal/deps/phoenix_live_view/lib
```
Confirm the version first if it matters: grep -A1 '"ecto"' portal/mix.lock.
mix help / IEx. Task flags and quick signatures:
```
cd portal && mix help ecto.gen.migration       # a mix task's real args/flags
cd portal && echo 'h Ecto.Query.from' | iex -S mix    # docs for a fn/macro
```
In IEx: h Mod.fun, exports Mod, b Behaviour (behaviour callbacks — useful for the Emisar.Repo.Query/Authorizer callbacks).
HexDocs (web) — last resort, match the version. Only when local source is unclear. Use WebFetch on https://hexdocs.pm/<pkg>/<version>/<Module>.html with the version from mix.lock (a bare /<pkg>/ redirects to latest, which may not be ours).
CLI flags (the runner, MCP bridge, system tools). Never guess a flag:
```
./bin/emisar --help          # and `./bin/emisar <subcmd> --help`
```
Or read the flag definitions in runner/ (Go flag/cobra) / mcp/. For an action's args/opts, the action pack schema is the source of truth, not memory.
Backstop, not first line: cd portal && mix compile --warnings-as-errors. It flags undefined or private functions and wrong arity. Use it to catch a slip — but checking first (rungs 1–2) is cheaper than a failed compile + retry.

The rule

If a check is inconclusive, inspect a narrower source, reproduce the call safely, or use a verified alternative that preserves the requested behavior. Missing evidence is investigation work. Ask the user only when their intent or authority is the missing information. Never write an unverified call and hope it compiles.

---name: tooling-verify-apidescription: Confirm a function, argument, option, type, callback, or CLI flag actually exists with the signature you think — before you call it. Use whenever you're about to use an API you're not certain of (a Repo/Ecto/Phoenix/Oban/Swoosh function, a mix task, a dependency's option, a runner/CLI flag), or any time you'd otherwise be guessing. Stops hallucinated functions before they're written.---# Verify the API — don't invent itA hallucinated function/arg/flag costs far more than the lookup. When in doubt,**check before you write.** Stop at the first rung that gives a definitive answer;you rarely need them all. Local sources beat the web — they're exact for theversions this repo actually uses.## The ladder (highest authority first)1. **This repo — for our own code.** The source IS the spec. Grep for the definition, then read it + its `@spec`/`@doc`. ```sh rg -n 'def fetch_and_update' portal/apps/emisar/lib/emisar/repo.ex rg -n 'def (for_user|for_api_key)' portal/apps/emisar/lib/emisar/auth/subject.ex ``` For the in-house building blocks (`Repo.fetch/list/fetch_and_update`, `Subject`, `Authorizer.build/2`, the `use Emisar, :query|:schema|:changeset` macros), the module under `lib/emisar/` is the only authority — don't assume Ecto/Phoenix defaults apply.2. **Dependency source — `deps/` (exact, offline, version-matched).** The pinned version's real code, not a guess or a newer doc: ```sh rg -n 'def fetch\b|@spec fetch' portal/deps/ecto/lib rg -n 'def (stream|assign_async)\b' portal/deps/phoenix_live_view/lib ``` Confirm the version first if it matters: `grep -A1 '"ecto"' portal/mix.lock`.3. **`mix help` / IEx.** Task flags and quick signatures: ```sh cd portal && mix help ecto.gen.migration # a mix task's real args/flags cd portal && echo 'h Ecto.Query.from' | iex -S mix # docs for a fn/macro ``` In IEx: `h Mod.fun`, `exports Mod`, `b Behaviour` (behaviour callbacks — useful for the `Emisar.Repo.Query`/`Authorizer` callbacks).4. **HexDocs (web) — last resort, match the version.** Only when local source is unclear. Use `WebFetch` on `https://hexdocs.pm/<pkg>/<version>/<Module>.html` with the version from `mix.lock` (a bare `/<pkg>/` redirects to *latest*, which may not be ours).5. **CLI flags (the runner, MCP bridge, system tools).** Never guess a flag: ```sh ./bin/emisar --help # and `./bin/emisar <subcmd> --help` ``` Or read the flag definitions in `runner/` (Go `flag`/cobra) / `mcp/`. For an action's args/opts, the action pack schema is the source of truth, not memory.6. **Backstop, not first line: `cd portal && mix compile --warnings-as-errors`.** It flags `undefined or private` functions and wrong arity. Use it to *catch* a slip — but checking first (rungs 1–2) is cheaper than a failed compile + retry.## The ruleIf a check is inconclusive, inspect a narrower source, reproduce the call safely,or use a verified alternative that preserves the requested behavior. Missingevidence is investigation work. Ask the user only when their intent or authorityis the missing information. Never write an unverified call and hope it compiles.

Frequently asked questions