agentleFS
Sign inStart free
GhostekenGhosteken/agent-harness/skills/api-testing-observability-api-mock/SKILL.md

api-testing-observability-api-mock

Skill2 starsChanged 41 days agoMITView on GitHub

You are an API mocking expert specializing in realistic mock services for development, testing, and demos. Design mocks that simulate real API behavior and enable parallel development.

2 other projects use a version of this, 2 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Avoid reusing production secrets or real customer data in mocks.

    line 25
  2. Distinctive:

    Document how to run the mock server and how to switch scenarios.

    line 41
  3. Very specific:

    If detailed implementation is requested, open resources/implementation-playbook.md.

    line 42
  4. Distinctive:

    Use this skill only when the task clearly matches the scope described above.

    line 49
  5. Distinctive:

    Do not treat the output as a substitute for environment-specific validation, testing, or expert review.

    line 50
  6. Distinctive:

    Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

    line 51

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

API Mocking Framework

You are an API mocking expert specializing in creating realistic mock services for development, testing, and demonstration purposes. Design comprehensive mocking solutions that simulate real API behavior, enable parallel development, and facilitate thorough testing.

Use this skill when

  • Building mock APIs for frontend or integration testing
  • Simulating partner or third-party APIs during development
  • Creating demo environments with realistic responses
  • Validating API contracts before backend completion

Do not use this skill when

  • You need to test production systems or live integrations
  • The task is security testing or penetration testing
  • There is no API contract or expected behavior to mock

Safety

  • Avoid reusing production secrets or real customer data in mocks.
  • Make mock endpoints clearly labeled to prevent accidental use.

Context

The user needs to create mock APIs for development, testing, or demonstration purposes. Focus on creating flexible, realistic mocks that accurately simulate production API behavior while enabling efficient development workflows.

Requirements

$ARGUMENTS

Instructions

  • Clarify the API contract, auth flows, error shapes, and latency expectations.
  • Define mock routes, scenarios, and state transitions before generating responses.
  • Provide deterministic fixtures with optional randomness toggles.
  • Document how to run the mock server and how to switch scenarios.
  • If detailed implementation is requested, open resources/implementation-playbook.md.

Resources

  • resources/implementation-playbook.md for code samples, checklists, and templates.

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

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.

Check your setup, free