Business Idea Evidence Validator

---
name: business-idea-evidence-validator
description: "Evaluate a business idea against current problem, competitor, demand, and trend evidence."
---

# Business Idea Evidence Validator

Evaluate a business idea against current problem, competitor, demand, and trend evidence.

## Required Aident Actions

- <action-tag>composio:exa_tools:exa_search</action-tag> (required inputs: query): Web search via the Exa engine. Returns ranked results with optional per-result text/highlights/summary (set the nested `contents` object). For agent workflows prefer `contents.highlights=true` - 10× fewer tokens than...
- <action-tag>composio:serpapi_tools:serpapi_trends_search</action-tag> (required inputs: query): Fetches Google Trends data; returns relative 0–100 interest indices (not absolute volumes) meaningful only when comparing queries within the same request. The `query`'s format (single/multiple terms) must comply with...

Use Aident Loadout to read the current Action schema before constructing inputs. Check the required integration connection in Aident Vault. If an Action is billable or mutating, run Aident preflight, show the affected target and quoted cost or risk, and wait for explicit user confirmation before execution.

## Workflow

1. Confirm the requested outcome, source material, destination, audience, constraints, and acceptance criteria.
2. Apply the source-derived guidance below to create a concrete plan. Resolve ambiguity before invoking an Action.
3. Select only the Aident Actions whose documented effect directly advances the requested outcome. Do not invoke every listed Action by default.
4. Inspect the current schema and prepare the minimum valid input for each selected Action.
5. Preflight each selected Action. Execute it only after any required confirmation, in dependency order, and carry returned IDs or asset URLs into later steps.
6. Verify the returned IDs, URLs, statuses, or artifacts against the acceptance criteria. Report partial completion precisely and do not repeat paid or mutating calls blindly.

## Source-Derived Guidance

- Turn the idea into explicit hypotheses about the customer, painful problem, current alternatives, differentiation, willingness to pay, geography, and decision horizon.
- Use composio:exa_tools:exa_search to gather current primary or high-quality evidence for the problem, competitors, substitutes, pricing, and buyer behavior.
- Use composio:serpapi_tools:serpapi_trends_search to test whether relevant search interest is growing, stable, declining, seasonal, or too sparse to interpret.
- Return evidence for and against each hypothesis, source links, confidence, unresolved assumptions, and the smallest next validation experiment. Do not fabricate market size or present search interest as proof of willingness to pay.

## Execution Boundaries

- Treat upstream provider-specific commands as background knowledge only. Execute the workflow through the exact Aident Actions above.
- Never request raw credentials in chat. Use Aident Vault connection flows for required accounts.
- Preserve user-provided wording, brand constraints, rights restrictions, and target identifiers. Do not invent authorization.
- Stop when a required integration is disconnected, preflight rejects the input, the target is ambiguous, or the user declines a required confirmation.

## Output

Return the execution plan, selected Action names, confirmed targets, Aident result identifiers or asset URLs, verification evidence, and any remaining blocked step.

## Attribution

This Skill adapts the reviewed upstream workflow. See [UPSTREAM.md](UPSTREAM.md) for the pinned source and [LICENSE.txt](LICENSE.txt) for the preserved license.