agentleFS
upex-galaxyupex-galaxy/agentic-qa-boilerplate/.agents/skills/business-api-context/SKILL.md

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

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
  1. Very specific:

    DO: read the map through bun run context:map business-api-context (or --section <id> for one endpoint group).

    line 18
  2. Very specific:

    DO: treat a placeholder map as "no map".

    line 19
  3. Very specific:

    DO: take field names, types and required flags from the schema ([API_TOOL] schema read, api/schemas/), and the MEANING from the map.

    line 20
  4. Distinctive:

    WHEN a session observes something that contradicts a section (a status, a field, an auth rule): PROPOSE the one-section edit with its …

    line 21
  5. Very specific:

    DO NOT: write anywhere but this skill's own references/.

    line 22
  6. Very specific:

    DO NOT: copy map content into this SKILL.md.

    line 23
  7. Very specific:

    Before a step that uses api-schema (verifying a section) or diagrams (redrawing a figure), run the point-of-use check in …

    line 24

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

business-api-context

Kind context with 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 read references/business-api-map.html raw: 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-context mode api; 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, no api/schemas/, no product code.
  • DO NOT: copy map content into this SKILL.md. Judgment goes in ## Rules or references/gotchas.md, dated and measured.
  • Before a step that uses api-schema (verifying a section) or diagrams (redrawing a figure), run the point-of-use check in agentic-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)

SourceWhat lives thereRole
references/business-api-map.htmlthe synthesis, one <section> per fact unit (overview, auth-model, journey-<slug>, architecture, integrations, cross-references), plus discovery-gapsthis 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 shapeswins for shape
the running API of the active environment (curl, agentic-qa-core/references/api-testing-doctrine.md)real statuses and bodieswins for behaviour
project-context mode apithe generator that CREATEs the map and UPDATEs its stale sectionsowns 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 → .env and bun 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.