sandbaseai/sandbase-skills / marketing/listicle-blog-writer
listicle-blog-writer
VerifiedResearch and write evidence-backed listicles, product roundups, and best-of comparisons with optional SandBase SERP, page, review, and screenshot evidence. Use for ‘best tools’, ‘top products’, roundup, SEO, GEO, or answer-engine content; do not use for an unresearched promotional ranking presented as independent advice.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 7.9 KB |
| references/sandbase-api-map.md | markdown | 2.0 KB |
references/sandbase-api-map.md
View on GitHub# SandBase Listicle Research API Map
This Skill uses SandBase's six MCP orchestration tools for optional live research. The available SERP, keyword, scraping, review, and screenshot capabilities are discovered at runtime so the installed Skill does not depend on a frozen provider schema.
| Tool name | Use it for |
|---|---|
| `sandbase_discover` | Find current organic SERP, related-query, page extraction, public review, and webpage screenshot candidates. |
| `sandbase_inspect` | Read a candidate's current schema, market controls, result limits, output shape, price, and execution mode. |
| `sandbase_run` | Execute an approved research or screenshot capability with exact schema-defined arguments. |
| `sandbase_run_get` | Poll the same asynchronous research run ID until completion or failure. |
| `sandbase_runs` | Recover recent result status or reconcile actual cost; it does not start research. |
| `sandbase_account` | Check available balance before an approved multi-call research batch. |
## Capability selection
Search separately for the evidence needed. Useful starting phrases include `google organic serp`, `related keywords`, `scrape markdown`, `page screenshot`, and the name of a public review source. Inspect serious candidates immediately before execution and follow the returned `execute_as` template.
Prefer one reusable SERP response over repeated category searches. Fetch or screenshot individual product pages only when that evidence is part of the requested deliverable. Official pages support first-party feature and pricing claims but must not be presented as independent reviews.
## Paid-call boundary
Discovery and inspection do not authorize paid research. Before `sandbase_run`, show the endpoint names, important inputs, current prices, expected call count, and total estimate or uncertainty. One confirmation may cover a clearly enumerated batch.
Preserve returned run IDs and poll asynchronous work with `sandbase_run_get`. Do not create replacement calls while a run is pending. Use `sandbase_runs` only for recovery or cost reconciliation.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| add-product-e2e-evalpaperclipai/paperclipAdd or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| diagnose-why-work-stoppedpaperclipai/paperclipCompatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| fix-failed-paperclip-runpaperclipai/paperclipDiagnose and fix failed, stuck, slow, or incorrectly blocked Paperclip tasks and runs. Use with a task/run URL or failure report to trace the root cause, prove a regression red then green, check second-order effects, verify the real workflow, and deliver a PR with passing checks. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |