Skip to content
Solutioneer

Invoking Skills

Solutioneer supports two entrypoints for every skill. Both end up in the same place — the skill’s intake loop — but the invocation surface is different.

Explicit syntax

Section titled “Explicit syntax”

The explicit form uses a $skill-id prefix followed by an account seed:

$account-intel-brief Outtake.ai
$discovery-context-ingester Outtake.ai
$discovery-question-generator Outtake.ai
$demo-scenario-builder Outtake.ai
$architecture-fit-mapper Outtake.ai
$integration-fit-gap-analyzer Beta Manufacturing
$poc-handoff-orchestrator Acme Health
$security-review-prep Acme Health

Rules:

  • Explicit $skill always wins over inferred routing. Codex will not ask a routing question if you used the explicit form.
  • The token after the skill id is treated as accountSeed.
  • accountSeed may be a company domain, a company name, or a product name.
  • If the explicit form already provides an account seed, the intake loop skips the first question and moves on to the next missing field.

Natural language

Section titled “Natural language”

Any of these phrasings are routed to the correct skill:

Prepare an account brief for Outtake.ai
Build a demo scenario for Outtake.ai selling Solutioneer to a RevOps lead
Can we integrate Solutioneer with Segment and HubSpot?
Turn this discovery and fit-gap into a POC handoff package

Codex infers the skill from intent. The intake loop runs the same way it does for explicit invocations.

Routing rules

Section titled “Routing rules”
  • Only the eight shipped skills are candidates: account-intel-brief, discovery-context-ingester, discovery-question-generator, demo-scenario-builder, architecture-fit-mapper, integration-fit-gap-analyzer, poc-handoff-orchestrator, security-review-prep.
  • If intent is ambiguous between multiple skills, Codex asks one routing question before starting the intake loop. The question is always the minimum needed to disambiguate.
  • If intent maps cleanly to one skill, Codex begins intake immediately.

Account seeds

Section titled “Account seeds”

The accountSeed is how every skill starts. It can be any of:

  • A domain: outtake.ai
  • A company name: Outtake
  • A product name: Solutioneer

If the seed looks like a domain, Codex treats it as account.domain. If it is plain text, Codex treats it as account.name until you clarify. You are not asked to pick between the two.

One-question intake

Section titled “One-question intake”

Every skill’s SKILL.md defines an intake order. Codex walks it one question at a time, asking only the next highest-value missing field. You can see each skill’s intake order on its own doc page:

You are never asked to provide raw JSON, and you are never asked for every field up front.

Section titled “What to read next”