# Slack Construct

> Standing context for Slack rooms — mention-driven engagement, room canvases, owner-presence access, and DM history. Ships as instructions.md composed into the group's CLAUDE.md at spawn; there is no workflow to invoke.

- Skill: `tenequm/slack-construct` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add tenequm/slack-construct`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tenequm/slack-construct/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Integrations & APIs
- Author: tenequm (https://skillmd.com/u/tenequm)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/tenequm/slack-construct

---


# Slack construct — standing context

A carrier for standing context, not an on-demand workflow. The payload is
`instructions.md` in this directory: the Slack room, canvas, access, and
DM-history rules an agent needs the moment it wakes in a Slack conversation.
The host composes every container skill's `instructions.md` into each group's
CLAUDE.md at spawn (`src/claude-md-compose.ts`), so from inside a session
those rules are already standing instructions — nothing to load or run here.

Two scope notes for maintainers:

- Skill fragments compose into **every** group, regardless of the group's
  `cli_scope`. The content therefore never names host-CLI (`ncl`) commands —
  groups with CLI access get that guidance from the CLI module's own
  instructions fragment, which the host includes only where `ncl` is enabled.
- Detailed canvas *editing* discipline lives in the `canvas-work` skill; the
  fragment here only carries the always-on rules (read-before-edit, section
  ops, comment behavior) at summary level.