Slack app

The Claresia Slack app is the end-user surface for Slack workspaces. End users invoke skills as slash commands, get responses rendered with Block Kit, and click through to Hub records.

Install

The app is published to the Slack App Directory under Claresia · Agent Operations Platform.

To install for your workspace:

1. Workspace owner navigates to https://slack.com/apps/A_CLARESIA
2. Click Add to Slack
3. Approve the OAuth scopes (see below)
4. Slack redirects back to Claresia Onboarding Portal Step 6

OAuth scopes requested

Scope	Why
commands	Register /claresia slash command
chat:write	Post Claresia skill responses
chat:write.public	Post in public channels without joining
users:read	Read user profile for archetype mapping
users:read.email	Email-based user matching
app_mentions:read	Listen for @Claresia mentions
channels:read	List channels the bot can post into

Claresia uses least-privilege — no channels:history, no groups:history, no files:read. The app does not crawl your Slack content.

Slash commands

The single canonical command is /claresia. Sub-commands are skill IDs:

/claresia pipeline-hygiene
/claresia incident-postmortem INC-2026-04-1873
/claresia standup-notes

If invoked without a skill, opens an autocomplete picker showing all skills entitled to the user’s archetype.

Skill invocation flow

sequenceDiagram
    participant U as User in Slack
    participant S as Slack
    participant CB as Claresia Bot
    participant LLM as LLM (Claude/GPT/etc.)
    participant H as Hub

    U->>S: /claresia incident-postmortem
    S->>CB: slash command webhook
    CB->>U: ephemeral message (params form via Block Kit)
    U->>CB: submits form (Block Kit modal)
    CB->>LLM: invoke skill
    LLM-->>H: write output + telemetry
    LLM-->>CB: response payload
    CB->>S: post Block Kit message in channel
    S->>U: render Block Kit response

Block Kit response (per skill)

{
  "blocks": [
    {
      "type": "header",
      "text": { "type": "plain_text", "text": "Incident Postmortem — INC-2026-04-1873" }
    },
    {
      "type": "section",
      "text": { "type": "mrkdwn", "text": "*Summary*\nA firmware regression in..." }
    },
    {
      "type": "section",
      "fields": [
        { "type": "mrkdwn", "text": "*Cost:*\n$0.04" },
        { "type": "mrkdwn", "text": "*Latency:*\n2.3 s" },
        { "type": "mrkdwn", "text": "*Tokens:*\n4823 in / 1421 out" }
      ]
    },
    {
      "type": "actions",
      "elements": [
        {
          "type": "button",
          "text": { "type": "plain_text", "text": "View record" },
          "url": "https://hub.dainese.claresia.com/records/rec_abc123"
        },
        {
          "type": "button",
          "text": { "type": "plain_text", "text": "Re-run" },
          "value": "rerun:gatespic.incident-postmortem"
        }
      ]
    }
  ]
}

Workspace install vs Enterprise Grid

Tier	Install scope
Standard / Plus	Per-workspace install via App Directory
Enterprise Grid	Org-wide install via Enterprise admin → propagates to all workspaces

For Enterprise Grid customers, Claresia recommends org-wide install so the slash command is consistent across every workspace.

Authentication

Slack OAuth → Claresia exchanges the Slack user.email for a tenant-scoped JWT (no separate login).

For tenants requiring MFA, the user completes MFA via the IdP’s web flow once per session, after which slash commands run silently.

Mode C considerations

The Slack app’s bot infrastructure is hosted by Claresia (the bot needs to receive Slack webhook callbacks at a Slack-reachable URL). In Mode C:

• The bot itself runs in Claresia Cloud
• The skill invocation routes through the customer’s LLM tenant
• The Hub write goes to the customer-cloud Hub via the tenant’s mTLS endpoint
• Only telemetry envelope reaches Claresia Cloud

Common gotchas

Symptom	Cause	Fix
/claresia not found	App not installed in workspace	Re-install from Slack App Directory
Slash command times out	Skill latency > 3s (Slack’s slash command timeout)	Claresia handles this with the response_url callback pattern automatically; if timeout messages persist, check status page
Block Kit renders broken	Slack client < BLK 1.5	Update Slack desktop / web client
User sees skills they shouldn’t	Cached old archetype mapping	Republish in Command Center → Distribution → Slack
Org-wide install fails	Enterprise Grid admin OAuth scope missing	Grant admin.apps:write and re-install

Reference

• Slack Block Kit reference
• Slack OAuth scopes
• Slack slash commands