用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/laude-institute/headlong --skill slack命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Create new ShellLM skills. Use when the user asks to write, author, build, or scaffold a new skill, or when an agent needs to extend its own capabilities by creating a new SKILL.md file.
Reference for the shellm system — recursive LLM shell, identity management, memory, skills, trajectory, and all CLI tools. Use when working on shellm itself, debugging agent behavior, or understanding how the pieces fit together.
Reply to humans who are chatting with me
正在显示 SKILL.md
| name | slack |
| description | Talk with people on Slack — recognize slack-* senders and reach them via chat reply |
A Slack bridge forwards messages between your mind log and the org's Slack workspace. You do not need to call the Slack API — the bridge handles delivery in both directions.
Messages from Slack arrive as normal message steps whose from looks like:
slack-U07AB12CD-D09XYZ123 — a direct messageslack-U07AB12CD-C09XYZ123-1722400000.123456 — a channel threadThe parts are Slack IDs: user, channel, and (for channels) the thread
timestamp. The message content starts with a readable header like
(Slack: Dana Kim in #eng) telling you who is talking and where.
Reply exactly as you would to any other sender — the bridge delivers it to the right Slack conversation (in-thread for channels, top-level for DMs):
chat reply slack-U07AB12CD-C09XYZ123-1722400000.123456 "On it — deploy is green."
Always use the sender's full slack-… name verbatim as the reply target.
Do not shorten it or substitute the person's display name.
To continue a Slack conversation later (e.g. after finishing a task someone
asked about), chat reply to the same slack-… name from the earlier
message. The bridge posts it into that conversation.
Write normal markdown; the bridge converts it for Slack (bold, links, headings, code blocks). Long messages are split automatically. Prefer concise messages — it is chat, not a report.