style: prettier-format testsprite-verify.skill.md

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: fyZhang66

skills/testsprite-verify.skill.md

@@ -137,7 +137,7 @@ server-side codegen on the CLI. Read the API surface that changed (OpenAPI, the
 route handler, request/response shapes) and write a pytest-style assertion script
 to a tempfile. **End the file by calling your `test_*` function(s)** — the runner
 executes the file top-to-bottom and does NOT auto-discover/collect test functions
-the way `pytest` does, so a test that is only *defined* (never called) silently
+the way `pytest` does, so a test that is only _defined_ (never called) silently
 passes regardless of its assertions:
 
 ```python
@@ -156,6 +156,7 @@ test_login_rejects_empty_password()
 **Execution environment (backend).** The code runs in a locked-down sandbox with
 only the Python **standard library + `requests` + `pytest` + `numpy` + `scipy`**
 (plus `requests`' own deps like `urllib3`). So:
+
 - **Test the API over HTTP** with `requests` against the target URL — that's what a
   backend test verifies.
 - **Do NOT `import` the project's own source modules** (e.g. `from app.services import …`,