Load to bind an overseer's mailbox to a private Slack channel, run or check the relay, or post an alert or a file to Slack.
70%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Medium
Suggest reviewing before use
Fix and improve this skill with Tessl
tessl review fix ./.agents/skills/slack/SKILL.mdProblems with a kendex-owned skill go through kendex report; check ownership in the file first.
The relay between one checkout's overseer mailbox and one private Slack channel. Mailbox reads use the mailbox package installed beside Slack inside the relay process. Writes use the bound checkout's lane-mail. The relay keeps its own record under tmp/slack/.
.agents/skills/slack/scripts/slack setup [--root ROOT] [--name NAME | --take CHANNEL_ID]
.agents/skills/slack/scripts/slack listen --root ROOT [--root ROOT]... [--once]
.agents/skills/slack/scripts/slack listen --status --root ROOT [--root ROOT]...
.agents/skills/slack/scripts/slack deliver --root ROOT < event.json
.agents/skills/slack/scripts/slack post [--root ROOT] [--channel ID] --text TEXT [--mention] [--file PATH]... [--thread TS] [--update TS]
.agents/skills/slack/scripts/slack read --channel ID (--ts TS | --latest N)
.agents/skills/slack/scripts/slack compact [--root ROOT]...
.agents/skills/slack/scripts/slack install --root ROOT [--root ROOT]... [--print]What each verb does, every setting, and every keyed line: slack --help. Python 3.8 or newer, standard library only.
SLACK_INBOUND=queue before setup and listen. Queue mode needs no app token, opens no socket and reads no channel history. Its worker calls slack deliver --root ROOT. The source is selected once at startup; neither mode falls back to the other. Switching keeps the binding and journal.lane-mail send --delivery-id; who judges a repeat is DEVELOPMENT.md § Constraints.delivered with its Slack ts, mailbox id and path=live|catch-up|queue. Eyes failures print a keyed cause and retry on the next poll; already_reacted settles the mark.references/secret-value.ere. A match is refused, journaled and never sent.chat.postMessage.listen --status shows the running code as code=.SLACK_OWNERS, run slack setup for each bound root: it invites an added owner to the channel and restarts the unit install wrote. A plain restart drops a removed owner but never invites an added one. After changing either token, restart the relay.setup, never a setting. The alert channel is the caller's --channel argument.read --channel needs no binding or owner settings. It uses the same token route as post --channel. --ts reads a message and its replies; --latest N reads the newest positive N top-level messages. Both print oldest first. Each line is slack: ts=TS edited=TS|- bot=ID text=TEXT, with user=ID instead of bot=ID for a user message. An absent author is user=-. text= is the last field; it preserves Slack markup and escapes backslash, newline and carriage return as \\, \n and \r. An empty channel prints nothing and exits 0. API refusals use the existing keyed stderr format and exit 2.kendex.settings.toml and the two tokens, SLACK_BOT_TOKEN and SLACK_APP_TOKEN, in its private env file: kendex.settings.toml.example.markup.py owns outbound tracker links and their representation. The sibling Linear skill's teams keys action reads workspace keys in each root and selects Linear ids. Linear keys and the workspace URL key are cached per root for a day. A missing or failed read leaves Linear ids unlinked with one tracker-links-unavailable notice per root and process.OWNER/REPO#N, or REPO#N and #N in the sending repository. Commit hashes link only when Git finds one commit in that repository. An unresolved reference stays unchanged with one reference-link-unavailable stderr line per distinct reference in an outbound message.slack post keep secret-pattern matches unexpanded for refusal. Other bare tracker ids link before the final secret check and Markdown cap. Existing links, Slack angle tokens, bare URLs, inline code and fenced code stay literal. Never put a tracker id in a code span.slack post text without --file, and the relay's ask, notice and answer posts, go out as standard Markdown, which Slack renders: **bold**, lists, headings, links and code blocks.slack post refuses a final linked body past that cap as text-too-long; send the long part as a file. The relay also refuses oversized new and overdue questions after expansion and secret checks, before sending. Shorten the question or link its detail in a file, issue or report. Reports and answers keep ordered Markdown continuations in the same thread, with visible part numbers.--file or a notice's --attach, is written in standard Markdown like any post. markup.py converts it to Slack's own mrkdwn: headings and bold as *bold*, -, * and + bullet lines as •, links as <URL|LABEL>, and &, < and > escaped except a leading quote marker. Code is escaped, so Slack shows it as typed; Slack angle tokens, bare URLs and any form it does not read, numbered lines included, stay as written. It is outside the 12,000-character cap, and Slack's own message limits still bound it.post --file for related files in one share with one comment. Every file passes the file and secret checks before upload. An input or upload failure shares no partial group. Slack's recipient settings decide notifications.slack listen --status prints one slack: slack-relay=ROOT state=ok|failing|stale|never line per root, with inbound=socket|queue. Queue mode prints connection=none without connection_since, for fresh and stale records alike. Socket mode prints connection=connected|reconnecting|disconnected|unknown and connection_since=, unknown since last_poll for a record an older relay wrote without the connection fields; a never line carries only fix=. A state other than ok carries fix=. A relay reconnecting past the bound the status record states reads failing. The fields of the row: schemas/journal.md § The status record.
vanillagreencom/kendex
3a2f84c
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.