How do I install the Compose skill?

Run npx skillmds@latest add 1shooperman/compose in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Compose safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Compose?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Compose free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Compose?

1shooperman (@1shooperman) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Compose by 1shooperman — Agent Skill

Name: Compose
Author: 1shooperman

Compose

Draft a new Markdown file for Slack publishing and save it to the XDG cache directory (~/.cache/slack-publish/). Use when the user wants to write or compose a message to send to Slack, e.g. "compose a Slack message", "draft a release announcement for Slack", "write a new post for

1shooperman 45f1a46 2.1 KB Updated Sep 17, 2026

File contents

Arguments

The user invoked this with: $ARGUMENTS

Parse <filename> and optionally <channel> from $ARGUMENTS.

<filename> — name for the draft file, with or without .md extension. If omitted, generate one from the current date: draft-YYYY-MM-DD.md.
<channel> — optional target channel to remember for the publish step.

Cache Directory

Resolve the XDG-compliant cache directory:

CACHE_DIR="${XDG_CACHE_HOME:-$HOME/.cache}/slack-publish"
mkdir -p "$CACHE_DIR"

The draft file path is $CACHE_DIR/<filename>.md.

Workflow

Resolve the cache directory and ensure it exists (run the bash snippet above).
If a draft file already exists at that path, read it and show the user the current content before proceeding.
Ask the user what content they want in the message, or ask them to describe the topic if they haven't already. Help them write clear, well-structured Markdown that will render nicely in Slack.
Write the final Markdown content to the draft file.
Confirm the file was saved and show the full path.
If a <channel> was provided (or the user mentions one), offer to publish immediately:

"Draft saved to $CACHE_DIR/<filename>.md. Publish to <channel> now?"

If the user confirms, invoke the slack-publish:publish skill with the resolved file path and channel.

Markdown Tips

Remind the user of conversions that apply when publishing:

# Heading → bold header line in Slack
**bold** / __bold__ → *bold* (Slack bold)
*italic* → _italic_ (Slack italic)
```code block``` → preserved as-is
- item / 1. item → • item
[label](url) → <url|label>
~~strike~~ → ~strike~

Listing Drafts

If the user asks to list drafts, run:

ls -1t "${XDG_CACHE_HOME:-$HOME/.cache}/slack-publish/"

---name: composedescription: Draft a new Markdown file for Slack publishing and save it to the XDG cache directory (~/.cache/slack-publish/). Use when the user wants to write or compose a message to send to Slack, e.g. "compose a Slack message", "draft a release announcement for Slack", "write a new post for---## ArgumentsThe user invoked this with: $ARGUMENTSParse `<filename>` and optionally `<channel>` from `$ARGUMENTS`.- `<filename>` — name for the draft file, with or without `.md` extension. If omitted, generate one from the current date: `draft-YYYY-MM-DD.md`.- `<channel>` — optional target channel to remember for the publish step.## Cache DirectoryResolve the XDG-compliant cache directory:```bashCACHE_DIR="${XDG_CACHE_HOME:-$HOME/.cache}/slack-publish"mkdir -p "$CACHE_DIR"```The draft file path is `$CACHE_DIR/<filename>.md`.## Workflow1. Resolve the cache directory and ensure it exists (run the bash snippet above).2. If a draft file already exists at that path, read it and show the user the current content before proceeding.3. Ask the user what content they want in the message, or ask them to describe the topic if they haven't already. Help them write clear, well-structured Markdown that will render nicely in Slack.4. Write the final Markdown content to the draft file.5. Confirm the file was saved and show the full path.6. If a `<channel>` was provided (or the user mentions one), offer to publish immediately: > "Draft saved to `$CACHE_DIR/<filename>.md`. Publish to `<channel>` now?" If the user confirms, invoke the `slack-publish:publish` skill with the resolved file path and channel.## Markdown TipsRemind the user of conversions that apply when publishing:- `# Heading` → bold header line in Slack- `**bold**` / `__bold__` → `*bold*` (Slack bold)- `*italic*` → `_italic_` (Slack italic)- ` ```code block``` ` → preserved as-is- `- item` / `1. item` → `• item`- `[label](url)` → `<url|label>`- `~~strike~~` → `~strike~`## Listing DraftsIf the user asks to list drafts, run:```bashls -1t "${XDG_CACHE_HOME:-$HOME/.cache}/slack-publish/"```

Frequently asked questions