SkillsAdd

getsentry/junior · Archived

slack-development

Implement Slack bot behavior with correct Slack-documented message formats, inbound mention/event routing, and long-running task UX.

First seen Apr 28, 2026

Installation

$ npx skills add getsentry/junior --skill slack-development
View on skills.sh ↗ GitHub repository ↗

Summary

  • Implement Slack bot behavior with correct Slack-documented message formats, inbound mention/event routing, and long-running task UX.
  • Use when asked to "format Slack messages", "fix Slack markdown", "debug thread mentions", "improve Slack bot UX", "add streaming in Slack", or "build Slack Chat SDK behavior".
  • Covers mrkdwn quirks, Events API payload patterns, routing guardrails, and Chat SDK implementation patterns.

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

pi-agent-integration Same source · more installs
getsentry/junior

Integrate the latest `@earendil-works/pi-agent-core` APIs into an app, library, runtime, or age…

8 installs
public-docs Same source · more installs
getsentry/junior

Create and maintain public, user-facing product documentation for this repo's `packages/docs` a…

8 installs
nitro Same source · more installs
getsentry/junior

Build and deploy universal JavaScript servers with Nitro v3.

8 installs
slack-msw-tests Same source
getsentry/junior

Author Slack HTTP integration tests using the repository MSW harness and fixture factories. Use…

6 installs

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

agent-browser Shared topics
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
azure-diagnostics Shared topics
microsoft/azure-skills

Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe …

568.9K installs
azure-validate Shared topics
microsoft/azure-skills

Pre-deployment validation for Azure readiness. Run deep checks on configuration, infrastructure…

567.7K installs
azure-rbac Shared topics
microsoft/azure-skills 489K installs
supabase-postgres-best-practices Shared topics
supabase/agent-skills

Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill …

391.6K installs
building-native-ui Shared topics
expo/skills 59.2K installs

Also in this package

Other skills from getsentry/junior.

npx skills add getsentry/junior
pi-agent-integration 8 public-docs 8 nitro 8 slack-msw-tests 6 vercel-sandbox 5 vercel-queues 5 deslop 3 junior-qa 3

Browse all from getsentry/junior

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 337
License LICENSE
Default branch main
Open issues 116
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 7,795 B
  • docs SUMMARY.md 442 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 6 installs

SKILL.md

Implement Slack-facing behavior with predictable formatting, inbound routing, and responsive long-running UX.

Step 1: Classify the requested change

Determine which category applies before writing code:

Category Typical request Primary reference
Output formatting "Fix markdown", "why does Slack render this weirdly?" ${CLAUDESKILLROOT}/references/slack-output-formatting.md
Slack event payloads "What does Slack send?", "why did raw event parsing fail?" ${CLAUDESKILLROOT}/references/slack-inbound-message-formats.md
Chat SDK payload contract "What fields do handlers actually receive?", "which fields are reliable in onSubscribedMessage?" ${CLAUDESKILLROOT}/references/chat-sdk-payload-contract.md
Thread routing "Passive detector skips thread replies", "reply/no-reply logic is wrong" ${CLAUDESKILLROOT}/references/slack-thread-routing.md
Assistant-thread APIs "Why does assistant.threads.setStatus fail?", "should this DM have assistant status/title?", "does Chat tab DM count as an assistant thread?" Read Slack docs for assistantthreadstarted, assistantthreadcontextchanged, message.im, and assistant.threads.* first, then load ${CLAUDESKILLROOT}/references/assistant-thread-apis.md and ${CLAUDESKILL_ROOT}/references/chat-sdk-payload-contract.md
Long-running behavior "No feedback while it runs", "show progress", "stream output" ${CLAUDESKILLROOT}/references/chat-sdk-patterns.md
Multiple categories Change touches formatting, routing, and/or runtime UX Read only the needed references above

If the request is ambiguous, ask one focused question and continue after clarification.

Step 2: Load only relevant references and implement

Use the selected reference files as the implementation guide. Keep SKILL.md high-level and put details in references.

Slack assistant-thread guardrails:

  1. Use Slack's current inbound event payload as the source of truth for assistant-thread API calls. For non-DM message events, use the live channel plus threadts ?? ts. For message.im, require the live channel and explicit threadts. For lifecycle events, use assistantthread.channelid and assistantthread.threadts.
  2. Do not invent assistant-thread identifiers from persisted state unless Slack's docs explicitly require it.
  3. Separate reply continuity from assistant-thread API eligibility. A stored root timestamp can be valid for reply threading without being valid for assistant.threads.*.
  4. Treat assistantthreadstarted and assistantthreadcontext_changed differently. Context changes can refresh prompts/context, but should not clobber a conversation-specific thread title back to a generic default.
  5. Conversation-specific thread titles should come from the earliest human message the runtime actually knows about for that thread, using the lightweight title model. Do not base titles on assistant reply text or a later follow-up.
  6. Title generation may run in parallel with the main assistant turn, but it must not delay assistant reply generation or visible reply delivery.
  7. Assistant status is best effort. Do not make Slack status writes part of the critical path for tool/model execution.
  8. If debugging a live repro through the example app, verify whether the app is executing packages/junior/dist/* output before trusting source edits against runtime behavior.

Step 3: Enforce project conventions

When modifying this repository:

  1. Keep tool behavior aligned with AI Gateway primitives already in use.
  2. Avoid reintroducing deprecated custom search integrations when Gateway-native tools exist.
  3. Preserve webhook waitUntil behavior so long-running handlers finish after HTTP response.

Step 4: Validate before finalizing

Use this checklist:

  • Rendering: message examples render correctly in Slack (mrkdwn expectations, escapes, mentions/links).
  • Inbound formats: routing uses documented Chat SDK payload fields first; raw Slack parsing only when necessary.
  • Thread routing: explicit bot mention paths bypass passive no-reply classification.
  • Assistant threads: assistant.threads.* calls use the live inbound assistant-thread context; non-DM message events may use threadts ?? ts, message.im must carry explicit threadts, and runtime code does not synthesize DM assistant roots for status/title updates.
  • Accessibility: block messages include an adequate top-level fallback text strategy.
  • Latency UX: user sees immediate feedback for long-running tasks.
  • Streaming/progress: behavior is observable during tool/model execution, not only at completion.
  • Failure mode: errors return actionable responses rather than silent stalls.