> open agents/development/api-tester/SOUL.md
> cat identity rules capabilities
Api Tester SOUL.md
Api Tester is a development SOUL.md template built for coding, testing, documentation, review, and software delivery assistants..
# Probe - The API Tester
CATEGORY
Development
ROLE_FOCUS
Development SOUL.md Template
FILE_PATH
agents/development/api-tester/SOUL.md
SOURCE_TYPE
awesome-openclaw-agents catalog
What This Template Type Covers
This page is a dedicated landing URL for the Api Tester SOUL.md pattern. It gives users and search engines one stable page for this specific template type instead of hiding everything behind a single filter UI.
Focuses on engineering workflow clarity, tool boundaries, and reliable output formats.
Authorship Note
This page is an indexed preview, not an original authored template by this site. Template authorship remains with the original source, and this page exists to organize discovery, show a partial preview, and link back to the source file.
SOUL.md Preview
Open raw sourceCore Identity
Responsibilities
Do:
Don't:
Typical Use Cases
Start a api tester agent with a clearer identity and operating boundary.
Benchmark this development template against other roles before customizing your own SOUL.md.
Use it when you need stronger defaults for development work.
What To Look For In This SOUL.md
Best For
People searching for a named SOUL.md type, a shareable prompt starter, or a category-specific agent configuration page.
Likely Sections
Identity, philosophy, rules, skills, constraints, escalation rules, and response formatting tuned for api tester workflows.
FAQ
What is the Api Tester SOUL.md template used for?
Api Tester is a development SOUL.md template used to define identity, operating rules, and expected behavior for that specific agent role.
Does this page show the real Api Tester SOUL.md content?
Yes. This page renders parsed preview sections from the original SOUL.md source file and links back to the source file for the full document.
How should I customize the Api Tester SOUL.md template?
Keep the role identity and core operating rules that match your use case, then adapt tone, boundaries, tools, and escalation rules to your own workflow.