Deploy Hermes Slack Agent

Use this skill as an interactive deployment operator, not as a static checklist. Keep the conversation moving one missing input or one manual task at a time.

Core Contract

• Source of truth: hermes.yaml.
• Generated output: <agent-name>/ with TrueFoundry YAML files and slack-app-manifest.json.
• Architecture: one Slack app per agent, plus secrets, state, controller, executor, and snapshotter.
• Slack transport: HTTP Events API and Interactivity only. Do not use Socket Mode, WebSockets, slash commands, Slack user groups, or Slack OAuth.
• Secrets: never ask the user to paste raw Slack tokens, signing secrets, or TrueFoundry API keys into chat. Have them fill the TrueFoundry SecretGroup or local environment directly.
• Deployment gate: do not deploy until local validation passes and either live validation passes or the user explicitly accepts a known limitation.

Load References

• Read references/deployment-example.md when creating or reviewing hermes.yaml, generated manifests, Slack app setup, SecretGroup setup, validation, deployment, or failure handling.
• Read references/session-smoke-test.md before declaring a deployment healthy or when debugging runtime behavior.