This workflow verifies that an authenticated route works end-to-end: correct response, correct side effects, and no obvious regressions.
Purpose & Scope
Use this workflow when:
You created or modified an authenticated route
You need to verify a route鈥檚 functional behavior and side effects
Out of scope:
Exhaustive negative testing (unless the task explicitly requires it)
Inputs & Preconditions
Inputs:
Route method + full URL
Expected request payload (if any)
Expected response shape/status
Expected side effects (DB writes, queue messages, logs, monitoring events)
Preconditions:
Identify authentication method (cookie/session/bearer/API key) and how to obtain test credentials safely.
Record test inputs and assumptions in workdocs for repeatability.
Steps
Locate the route implementation
Confirm route registration and handler wiring (route 鈫?controller 鈫?service as applicable).
Construct a reproducible request
Prefer a dedicated test helper under /scripts/ or a registered ability, if available.
Otherwise, use a plain HTTP client (curl/Postman) with explicit headers/cookies.
Run the happy-path test
Confirm status code and response body shape match expectations.
Verify side effects
Check the authoritative data store or observable artifact (DB rows, files, emitted events).
Quick sanity checks
Run a minimal failure test if the task is auth-related (e.g., request without auth should be 401/403).
Report
Record what was tested, results, and any fixes performed.
Outputs
A short test report in workdocs (request, response, verification steps, findings)
Optional: small fixes if testing revealed clear implementation bugs
Safety Notes
Do not hardcode secrets or real credentials in SSOT docs.
Prefer test identities and development/test environments.
Related
Converted and distributed by TomeVault — claim your Tome and manage your conversions.
1---2name: willyu1007-ai-first-template-auth-route-tester3description: Auth Route Tester4---5# Auth Route Tester67This workflow verifies that an authenticated route works end-to-end: correct response, correct side effects, and no obvious regressions.89---1011## Purpose & Scope1213Use this workflow when:14- You created or modified an authenticated route15- You need to verify a route鈥檚 functional behavior and side effects1617Out of scope:18- Exhaustive negative testing (unless the task explicitly requires it)1920---2122## Inputs & Preconditions2324Inputs:25- Route method + full URL26- Expected request payload (if any)27- Expected response shape/status28- Expected side effects (DB writes, queue messages, logs, monitoring events)2930Preconditions:31- Identify authentication method (cookie/session/bearer/API key) and how to obtain test credentials safely.32- Record test inputs and assumptions in workdocs for repeatability.3334---3536## Steps37381. **Locate the route implementation**39 - Confirm route registration and handler wiring (route 鈫?controller 鈫?service as applicable).402. **Construct a reproducible request**41 - Prefer a dedicated test helper under `/scripts/` or a registered ability, if available.42 - Otherwise, use a plain HTTP client (curl/Postman) with explicit headers/cookies.433. **Run the happy-path test**44 - Confirm status code and response body shape match expectations.454. **Verify side effects**46 - Check the authoritative data store or observable artifact (DB rows, files, emitted events).475. **Quick sanity checks**48 - Run a minimal failure test if the task is auth-related (e.g., request without auth should be 401/403).496. **Report**50 - Record what was tested, results, and any fixes performed.5152---5354## Outputs5556- A short test report in workdocs (request, response, verification steps, findings)57- Optional: small fixes if testing revealed clear implementation bugs5859---6061## Safety Notes6263- Do not hardcode secrets or real credentials in SSOT docs.64- Prefer test identities and development/test environments.6566---6768## Related6970---71> Converted and distributed by [TomeVault](https://tomevault.io/claim/willyu1007) — claim your Tome and manage your conversions.72<!-- tomevault:4.0:skill_md:2026-04-14 -->
Run npx skillmds@latest add tomevault-io/willyu1007-ai-first-template-auth-route-tester in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
Auth Route Tester It is listed under Coding & Dev Tools on SkillMD.
This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.
tomevault-io