sandbaseai/sandbase-skills / marketing/test-driven-development
test-driven-development
VerifiedPlan, implement, or review test driven development work in an existing codebase with compatibility, security, and verification controls. Use when the user explicitly requests test driven development work.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 3.0 KB |
| references/sandbase-api-map.md | markdown | 1.3 KB |
references/sandbase-api-map.md
View on GitHub# SandBase Test Driven Development API Map
Core Test Driven Development work remains local. SandBase is optional and is used only for current external documentation, repository evidence, or explicitly requested model inference.
| Tool name | Use it for |
|---|---|
| `sandbase_discover` | Find current capabilities by task rather than assuming a provider or endpoint. |
| `sandbase_inspect` | Read the live input schema, coverage, limits, output shape, price, and execution template. |
| `sandbase_run` | Execute a user-approved capability with the exact discovered name and schema-defined arguments. |
| `sandbase_run_get` | Poll the same asynchronous run until it completes or fails. |
| `sandbase_runs` | Recover recent run status or reconcile observed cost without submitting a duplicate. |
| `sandbase_account` | Check balance before an approved multi-call batch. |
Before `sandbase_run`, present the selected endpoint, important inputs, current pricing, planned call count, and total estimate or uncertainty. Discovery and inspection are not permission to execute a paid call.
Capability availability changes. Do not hard-code model names, provider parameters, prices, output URLs, or result schemas. Prefer an existing dedicated integration or user-provided API access when it already covers the request.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 470k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 470k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 470k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |