Skip to content

sandbaseai/sandbase-skills / research/startup-research

startup-research

Verified

Research startups and emerging companies with funding data, team composition, product positioning, market traction, and news coverage. Combines Apollo firmographics, LinkedIn team data, and web intelligence for comprehensive startup due diligence.

FileKindSize
SKILL.mdskill md2.2 KB
references/sandbase-api-map.mdmarkdown1.1 KB
---
name: startup-research
description: "Research startups and emerging companies with funding data, team composition, product positioning, market traction, and news coverage. Combines Apollo firmographics, LinkedIn team data, and web intelligence for comprehensive startup due diligence."
---

# Startup Research

Research startups and emerging companies with funding data, team composition, product positioning, market traction, and news coverage. Combines Apollo firmographics, LinkedIn team data, and web intelligence for comprehensive startup due diligence. Read [the API map](references/sandbase-api-map.md) before selecting a capability.

## Call SandBase capabilities

Use the capability identifiers below as discovery hints, not MCP tool names. Find the matching endpoint with `sandbase_discover(q: "<provider and capability>")`; use its returned `name` in `sandbase_inspect(name: "<returned name>")`. Read `inputSchema`, pricing, and `execute_as`, then call `sandbase_run` using `execute_as.arguments.name` and schema-defined `arguments`. If a `run_id` is returned, poll `sandbase_run_get(run_id: "<returned run_id>")` within the task budget until `completed` or `failed`; report pending or failed runs without resubmitting them automatically.

## Capability identifiers

- `apollo_company_enrich`
- `apollo_company_news_search`
- `linkedin_web_v2_company_profile`
- `linkedin_web_v2_company_posts`
- `tavily_search`
- `exa_search`

## Workflow

1. Understand the user's research question, target, and context.
2. Resolve each selected capability with `sandbase_discover`, then inspect the returned `name` with `sandbase_inspect` to confirm the schema and pricing.
3. Follow `execute_as` with `sandbase_run`; collect async results with `sandbase_run_get` as described above.
4. Synthesize findings into a clear, evidence-backed answer.
5. Cite sources, note evidence gaps, and separate observations from interpretations.

## Guidelines

- Always call `sandbase_inspect` before using any capability.
- Cite sources and preserve attribution (URLs, usernames, dates, metrics).
- Separate factual observations from analysis and recommendations.
- If data is unavailable, note the gap and continue with available evidence.
- Read-only research only. Never take actions on platforms.
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 322kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 322kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 322kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 198kUpdated Claude CodeCodexVerifiedInstall