Skip to content

[slack] Use readable profile names in drafts#213

Draft
Aismit wants to merge 1 commit intomainfrom
aismit/FS-slack-readable-draft-names
Draft

[slack] Use readable profile names in drafts#213
Aismit wants to merge 1 commit intomainfrom
aismit/FS-slack-readable-draft-names

Conversation

@Aismit
Copy link
Copy Markdown
Collaborator

@Aismit Aismit commented Apr 30, 2026

Summary

  • Update the Slack outgoing-message skill so slack_send_message_draft draft bodies use resolved, human-readable Slack profile names instead of raw user IDs or <@U...> mention markup.
  • Keep explicit Slack mention syntax for direct sends, scheduled messages, and canvases where it is needed to create real mentions.
  • Align the shared Slack markdown reference and outgoing-message skill metadata with the new draft-specific behavior.

Why

Drafts are review surfaces, and raw Slack IDs are hard for humans to read. This change makes draft text readable while preserving notification-capable mention syntax for actual Slack writes.

Simple Explanation

Before, the drafting guidance treated drafts like sent messages, so a draft could show something like <@U123456>. Now drafts should say the person's readable Slack name, while sent messages can still use Slack's special mention code when a real tag is needed.

Validation

  • git diff --check
  • ruby -e 'require "yaml"; YAML.load_file("plugins/slack/skills/slack-outgoing-message/agents/openai.yaml"); puts "ok"'

No runtime tests were run because this is a docs/skill-instructions-only change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant