Menu
Ground one external service in its real behaviour by reading the provider's official docs and determining its access shape, before any probe code is written.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Compile the contract set in your head — simulate how the real application would run from the specs, and disprove (or confirm) it works before any source .py is written.
Author test stub files (.pyi) whose signatures express the domain, relationships, and compositions, as the first contract surface.
Funnel level 3 — identify building-block names and rough boundaries only, and run gap analysis.
Funnel level 1 — establish the big picture with seven broad questions, applying CIT, Laddering, and CI Perspective throughout.
Squash-merge the feature commits into dev, regenerate docstrings, and verify the whole suite plus whole-suite stubtest are clean.
Publish the delivered batch as release notes, a PR to main, or a tagged release.
| name | research-provider |
| description | Ground one external service in its real behaviour by reading the provider's official docs and determining its access shape, before any probe code is written. |
~/.secrets/<project>.env), request/response shape, and both success and failure modes. Per [[software-craft/secrets-and-config]] the agent names the variable and instructs the user where to set it; it never holds or prints the value.