# Slack Message

> Draft an internal Slack message grounded in current project context and recent workflow. Use when sharing a status update, result, finding, or request with a teammate or internal stakeholder at your org.

- **Type:** Skill
- **Install:** `agentstack add skill-dgilford-ai-science-toolkit-slack-message`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [dgilford](https://agentstack.voostack.com/s/dgilford)
- **Installs:** 0
- **Category:** [AI & ML](https://agentstack.voostack.com/c/ai-and-ml)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [dgilford](https://github.com/dgilford)
- **Source:** https://github.com/dgilford/ai-science-toolkit/tree/main/skills/slack-message

## Install

```sh
agentstack add skill-dgilford-ai-science-toolkit-slack-message
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

You are drafting a first-draft Slack message for the user to review and edit before sending. Synthesize live project context with their direction.

## Live context

```!
echo "=== Recent commits ===" && git log --oneline -5 2>/dev/null || echo "(not a git repo)"
echo "=== Working state ===" && git status --short 2>/dev/null | head -20 || echo ""
echo "=== Directory ===" && basename "$(pwd)"
```

## Interview

Check the user's request against this list. If **any** anchor is missing, ask all missing questions in **one message** — never one at a time.

| # | Question |
|---|---|
| 1 | **Who is this for?** Name/role; DM, team channel, or leadership post? |
| 2 | **What's the purpose?** (status update / share a finding / request review / ask for action / FYI) |
| 3 | **What's the one key thing they need to know?** |
| 4 | **Tone**: casual or professional? Technical or plain language? |
| 5 | **Length**: one-liner, short paragraph, or structured with sections? |
| 6 | **Call to action or deadline?** What, if anything, do you need from them — and by when? |

## Drafting rules

1. Ground the message in the live context above — reference actual recent work, commits, or open changes where relevant (don't invent).
2. Write in the user's voice: direct, no corporate hedging.
3. Use Slack-native formatting: `*bold*`, `_italic_`, bullet lists with `-`, ` ```code``` ` blocks for technical snippets.
4. Scale technical depth to the audience: peer-level can go deep; leadership stays outcome-focused.
5. One message, one point. If the user has multiple asks, flag that and suggest splitting.
6. Always generate a **Title** — a short (≤10 word) subject line that captures the message purpose. Always end the title with 🔽.

## Output

Present the draft with a title line followed by the message body inside a fenced block:

**Title:** 

```

```

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [dgilford](https://github.com/dgilford)
- **Source:** [dgilford/ai-science-toolkit](https://github.com/dgilford/ai-science-toolkit)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-dgilford-ai-science-toolkit-slack-message
- Seller: https://agentstack.voostack.com/s/dgilford
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.