Skills Overview

Solutioneer ships eight skills. Each one is narrow, chat-native, and shares the same intake rules, grounding rules, and writeback rules. Picking the right skill is usually a matter of picking the right stage of the pre-sales motion.

The eight skills

Skill	Use it for	Reach for it when
Account Intel Brief	Pre-call research	You are about to meet a new account and need a cited snapshot, stack signals, likely initiatives, and a question bank.
Discovery Context Ingester	Fact-sheet creation	Your source material is messy, duplicated, or private, and you need one normalized view before downstream work.
Discovery Question Generator	Discovery planning	You already have context and need stakeholder questions, signal checks, and red flags for the next call.
Demo Scenario Builder	Tailored demo prep	You have an account in mind, a persona, and a product pitch, and you need a narrative, talk track, objections, and seed data.
Architecture Fit Mapper	Solution mapping	You need a diagram, blockers, and validation plan grounded in fact-sheet context and docs.
Integration Fit Gap Analyzer	Cited integration assessment	A prospect asks “do you support X” and you need a defensible support / workaround / gap / unknown matrix with citations.
POC Handoff Orchestrator	Pre-sales to delivery handoff	Discovery and fit-gap are done, and you need a POC plan, architecture note, milestones, and risk register for the delivery team.
Security Review Prep	Security response prep	The customer is moving into security review and you need a control matrix, follow-ups, and escalation gaps.

The canonical chain

These skills are designed to compose. The output of one becomes context for the next. The usual path across a deal is:

1. Discovery Context Ingester creates the reusable fact sheet when source material is messy.
2. Account Intel Brief grounds you in the account.
3. Discovery Question Generator turns the fact sheet into the next-call plan.
4. Demo Scenario Builder reuses that brief to build the demo, so you do not re-research the account.
5. Architecture Fit Mapper turns that context into a solution map and validation plan.
6. Integration Fit Gap Analyzer answers the integration questions surfaced in discovery or during the demo.
7. POC Handoff Orchestrator consumes everything above to produce the delivery-ready package.
8. Security Review Prep packages the same context for customer security review.

Each skill is explicit about what prior context it reuses. When you have a prior brief or fit-gap in chat, Solutioneer will prefer it over new research before falling back to Firecrawl.

Flow and architecture

The same chain as a dependency graph. Arrows show the prior artifact a downstream skill prefers to consume.

flowchart TD
  Sources(("pasted notes · URLs · slack · gmail · drive · hubspot · granola"))

  subgraph Discovery["Discovery"]
    direction TB
    DCI["discovery-context-ingester"]
    AIB["account-intel-brief"]
    DQG["discovery-question-generator"]
  end

  subgraph Solutioning["Solutioning"]
    direction TB
    DSB["demo-scenario-builder"]
    AFM["architecture-fit-mapper"]
    IFGA["integration-fit-gap-analyzer"]
  end

  subgraph Handoff["Handoff"]
    direction TB
    PHO["poc-handoff-orchestrator"]
    SRP["security-review-prep"]
  end

  Sources --> DCI
  DCI --> DQG
  DCI --> AIB
  AIB --> DSB
  DCI --> AFM
  IFGA --> AFM
  DCI --> IFGA
  AIB --> IFGA
  AFM --> PHO
  IFGA --> PHO
  DSB --> PHO
  AFM --> SRP
  DCI --> SRP

  Firecrawl[/"Firecrawl
grounding"/]
  Composio[/"Composio
ingestion + writeback"/]

  Firecrawl -. grounds .-> AIB
  Firecrawl -. grounds .-> IFGA
  Firecrawl -. grounds .-> AFM
  Firecrawl -. grounds .-> SRP
  DCI -. ingests .-> Composio
  PHO -. publishes .-> Composio
  SRP -. publishes .-> Composio

  classDef skill fill:#1c2a24,stroke:#7fb56a,stroke-width:1px,color:#e6f2dc;
  classDef provider fill:#2a2516,stroke:#c9a34a,stroke-width:1px,color:#f0e0b4;
  classDef source fill:#101713,stroke:#4d6a5a,color:#aec7b7;
  class DCI,AIB,DQG,DSB,AFM,IFGA,PHO,SRP skill
  class Firecrawl,Composio provider
  class Sources source

The ingester sits at the root because every downstream skill works better from a normalized fact sheet. The two providers (Firecrawl for grounding, Composio for ingestion and writeback) are cross-cutting — they augment individual skills rather than sitting in the chain.

What every skill shares

• One-question intake. No forms, no JSON.
• Chat-only by default. Save and external writeback are opt-in.
• Cited or unknown. Unsupported claims are labelled, not invented.
• Same input shape. account, objective, notes, artifactRefs, destinations, providerMode.
• Same provider rules. Firecrawl for grounded research, Composio for external writeback, both optional and gracefully degraded.

What each skill does not do

• It does not run skills from outside the eight shipped ones.
• It does not silently save files or push to external systems.
• It does not freehand account facts, vendor claims, integration support claims, or product and security assertions.

Pick a skill to read in depth:

• 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