Agent skill
slack-communication
Policies for Slack communication via MCP tools. Use when interacting with Slack channels, threads, DMs, or composing Slack messages. Provides bilingual communication rules, AI disclosure requirements, and message composition guidelines.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/slack-communication
SKILL.md
Slack Communication Policies
AI Disclosure
All messages sent via Claude MUST include an AI disclosure footer. Append the following to every message payload:
- English messages:
_This message was composed and posted by Claude on behalf of [user]._ - Japanese messages:
_このメッセージはClaudeが[user]の代理で作成・投稿しました。_ - Bilingual messages: Include both disclosures
Bilingual Policy
Japanese Messages
- Use desu/masu form as default
- Match the honorific level (keigo) of the conversation participants
- Keep technical terms in English (e.g., "deploy", "PR", "CI/CD") when that is the channel norm
- When the thread is new or the language is ambiguous, ask the user which language to use
Confirmation Requirement
Never send a message without explicit user approval. The workflow is:
- Draft the message with AI disclosure footer appended
- Present the complete message to the user
- Send only after explicit approval
Mark as Read Policy
- After sending a reply via
/reply-to-slack: the REPLY subagent marks the channel/thread as read - After completing a Slack task without a reply (e.g., processed externally): the main session marks the channel/thread as read using
mcp__slack__conversations_mark - Case 3 items (conversation completed): ask the user to confirm, then mark as read
Anti-Patterns
- Sending messages without AI disclosure footer
- Sending without user confirmation
- Replying in a different language than the conversation thread
- Using
conversations_unreads-- too slow on large workspaces. Useconversations_search_messageswithto:me,@<username>, andfilter_users_with/filter_threads_onlyinstead
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?