business-api-context
Skill26 starsChanged 9 days agoMITView on GitHub
What the API of the system under test MEANS to the business: every endpoint group, who calls it and why, what it changes, which auth level and role it needs, the business flows that cross several endpoints, error semantics and the external integrations behind them. Load it whenever a task touches an API test, a request or response, an auth or permission question, a status code that looks wrong, contract coverage, or asks which endpoint does what, even when nobody says 'API map'. Reads its map through `bun run context:map business-api-context`. Pure knowledge plus a self-update proposal path: NOT the OpenAPI contract itself (that is the schema), NOT for running a QA stage, NOT for entities (business-data-context) or user journeys (business-e2e-context).
- Reads credentials
In this repository30 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- acliSkill
- agentic-qa-coreSkill
- agentic-qa-onboardSkill
- bug-screenshot-annotationSkill
- business-data-contextSkill
- business-domain-contextSkill
- business-e2e-contextSkill
- evidence-artifactSkill
- exploratory-testingSkill
- framework-developmentSkill
- git-flow-masterSkill
- infra-contextSkill
- iql-contextSkill
- jira-administrationSkill
- judgment-daySkill
- orca-orchestrationSkill
- project-contextSkill
- project-discoverySkill
- pr-review-leadSkill
- regression-testingSkill
- session-handoffSkill
- shift-left-testingSkill
- sprint-conductorSkill
- sprint-testingSkill
- test-automationSkill
- test-documentationSkill
- test-framework-adaptationSkill
- xray-cliSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 1 is distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 18
DO: read the map through bun run context:map business-api-context (or --section <id> for one endpoint group).
- Very specific: line 19
DO: treat a placeholder map as "no map".
- Very specific: line 20
DO: take field names, types and required flags from the schema ([API_TOOL] schema read, api/schemas/), and the MEANING from the map.
- Distinctive: line 21
WHEN a session observes something that contradicts a section (a status, a field, an auth rule): PROPOSE the one-section edit with its …
- Very specific: line 22
DO NOT: write anywhere but this skill's own references/.
- Very specific: line 23
DO NOT: copy map content into this SKILL.md.
- Very specific: line 24
Before a step that uses api-schema (verifying a section) or diagrams (redrawing a figure), run the point-of-use check in …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
business-api-context
Kind
contextwith a declared write scope (agentic-qa-core/references/skill-composition-strategy.md§2b). Delivered once by upstream as a placeholder, then owned by the project: the map inside is this project's synthesis. Procedure:agentic-qa-core/references/business-context-maps.md.
Compact Rules
- DO: read the map through
bun run context:map business-api-context(or--section <id>for one endpoint group). NEVER readreferences/business-api-map.htmlraw: its SVG is most of the bytes and none of the facts. - DO: treat a placeholder map as "no map". Say so and hand the user
project-contextmodeapi; never answer API questions as if the API were empty. - DO: take field names, types and required flags from the schema (
[API_TOOL]schema read,api/schemas/), and the MEANING from the map. On a conflict the schema wins for shape, the running API wins for behaviour. - WHEN a session observes something that contradicts a section (a status, a field, an auth rule): PROPOSE the one-section edit with its evidence to the user (or to the conductor when you are a supervised worker), apply it only on approval. Procedure:
references/refresh.md. - DO NOT: write anywhere but this skill's own
references/. No Jira, no.context/, no other skill, noapi/schemas/, no product code. - DO NOT: copy map content into this SKILL.md. Judgment goes in
## Rulesorreferences/gotchas.md, dated and measured. - Before a step that uses
api-schema(verifying a section) ordiagrams(redrawing a figure), run the point-of-use check inagentic-qa-core/references/preflight-gate.md§8.
Read full SKILL.md when: building a briefing for an API-level dispatch, deciding whether a section is stale, or proposing an edit to the map.
What this skill knows
One aspect of the system under test: its API as a business surface. Which endpoint groups exist and what each one is for, who is allowed to call them, what they change, how a multi-call flow chains them, what each error means to a user, and which third parties sit behind them. Loading it changes what the agent KNOWS; the only thing it ever does is propose an edit to its own map.
Sources of truth (cited, never copied)
| Source | What lives there | Role |
references/business-api-map.html | the synthesis, one <section> per fact unit (overview, auth-model, journey-<slug>, architecture, integrations, cross-references), plus discovery-gaps | this skill's map (read via bun run context:map) |
the OpenAPI contract ([API_TOOL] schema read, api/schemas/ after bun run api:sync) | paths, methods, payload shapes | wins for shape |
the running API of the active environment (curl, agentic-qa-core/references/api-testing-doctrine.md) | real statuses and bodies | wins for behaviour |
project-context mode api | the generator that CREATEs the map and UPDATEs its stale sections | owns regeneration |
Rules (judgment, dated)
(none yet: each rule carries YYYY-MM-DD · rule · measured: how)
Not here
- Payload schemas and types → the OpenAPI contract and
api/schemas/. - Entities, state machines and triggers →
business-data-context. - User journeys and the feature catalog →
business-e2e-context. - Tokens and credentials →
.envandbun run api:login, never a map.
References
references/business-api-map.html— the map (generated; read through the reader).references/refresh.md— the self-update procedure and this aspect's staleness signals.references/gotchas.md— measured traps in reading this project's API.
Refinements
Lessons land as proposals per agentic-qa-core/references/skill-refinement-protocol.md, never as direct edits.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

