Skip to content

sandbaseai/sandbase-skills / marketing/backtesting-frameworks

backtesting-frameworks

Verified

Apply backtesting frameworks in reproducible local data workflows with version-aware APIs, explicit assumptions, and validation. Use when the user chooses backtesting frameworks or its strengths fit the task.

FileKindSize
SKILL.mdskill md3.3 KB
references/sandbase-api-map.mdmarkdown1.3 KB

references/sandbase-api-map.md

View on GitHub
# SandBase Backtesting Frameworks API Map

Core Backtesting Frameworks work remains local. SandBase is optional and is used only for an explicitly requested external dataset or model inference step that is not part of the local analysis.

| 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.
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 321kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 321kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 321kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 321kUpdated Claude CodeCodexVerifiedInstall