Skip to content
Solutioneer

Composio API Key

Composio powers every skill’s external writeback path. Without it, skills still run — they just return artifacts in chat instead of pushing them to Google Docs, Confluence, Linear, or GitHub.

1. Create a Composio account

Section titled “1. Create a Composio account”

Go to composio.dev and sign up. The signup flow lands you in the dashboard.

2. Generate an API key

Section titled “2. Generate an API key”

In the Composio dashboard:

  1. Open Settings → API Keys (or Developers → API Keys, depending on the current dashboard layout).
  2. Click Create API Key.
  3. Give the key a recognizable name — e.g. solutioneer-local.
  4. Copy the key. It starts with cmp-.

3. Add the key to .env

Section titled “3. Add the key to .env”

In the repo root:

Terminal window
cp .env.example .env

Then set the key:

Terminal window
COMPOSIO_API_KEY=cmp-...

Solutioneer also respects .env.local and process.env. Whichever file you use, the variable name must be exactly COMPOSIO_API_KEY.

4. Verify

Section titled “4. Verify”

From the repo root:

Terminal window
npm run doctor

The doctor should report COMPOSIO_API_KEY as present.

How Composio is used inside skills

Section titled “How Composio is used inside skills”

Composio is the writeback layer. The flow, every time, is:

  1. You ask for an external write (“push this brief to Confluence”, “create a Linear project for this POC plan”).
  2. Codex confirms that you want the external write.
  3. Codex confirms the target destination.
  4. Codex verifies that COMPOSIO_API_KEY is present.
  5. Codex verifies that the required toolkit is connected.

If the toolkit is not connected, you see a Connect now / Skip decision point. Connect now opens Composio’s hosted login flow in a browser tab (when available) and waits for the connection to become active. Skip keeps the workflow chat-only.

Writes are always confirmation-based. Codex does not execute the write before the connection is active.

Toolkits per skill

Section titled “Toolkits per skill”

The toolkits each skill can use are declared in its manifest.json:

SkillToolkits
Account Intel Briefgooglesuper (Docs), confluence
Demo Scenario Buildergooglesuper (Docs + Sheets), github
Integration Fit Gap Analyzerlinear, confluence, googlesuper, github
POC Handoff Orchestratorlinear, confluence, googlesuper, github

Specific tool slugs

Section titled “Specific tool slugs”

For reference, the Composio tool slugs Solutioneer is allowed to call (from tools/composio/slugs.ts):

  • GOOGLESUPER_CREATE_DOCUMENT_MARKDOWN
  • GOOGLESUPER_CREATE_GOOGLE_SHEET1
  • GOOGLESUPER_ADD_SHEET
  • GOOGLESUPER_CREATE_SPREADSHEET_ROW
  • LINEAR_CREATE_LINEAR_ISSUE
  • LINEAR_SEARCH_ISSUES
  • LINEAR_CREATE_LINEAR_PROJECT
  • LINEAR_CREATE_PROJECT_MILESTONE
  • LINEAR_CREATE_PROJECT_UPDATE
  • CONFLUENCE_CREATE_PAGE
  • CONFLUENCE_UPDATE_PAGE
  • GITHUB_CREATE_AN_ISSUE
Section titled “What to read next”

Connect the toolkits you actually need. Each one is its own OAuth flow:

Or go deeper on behavior: