Its confirmation step named a different Slack MCP tool and parameter set
than the thread-reply step below it; both now match what the
`slack-mcporter` table documents.

Assisted-by: Claude Opus 5 via Claude Code

diff --git a/ai/skills/warm-handoff/SKILL.md b/ai/skills/warm-handoff/SKILL.md
index 777e416a..e81e366e 100644
--- a/ai/skills/warm-handoff/SKILL.md
+++ b/ai/skills/warm-handoff/SKILL.md
@@ -51,8 +51,11 @@ Source: https://luckymike.dev/posts/warm-handoffs/
 
 6. **Send on confirmation.** Once approved:
    ```bash
-   mcporter call slack.send_message channel="#target-channel" text="..."
+   mcporter call slack.slack_send_message --args '{"channel_id":"<target-channel-id>","message":"..."}'
    ```
+   The `slack-mcporter` skill defaults to `slack_send_message_draft` instead,
+   because messages posted straight through MCP can't be edited in Slack
+   afterward.
 
 7. **Link back to the original thread.** Reply in the original thread with a link to the handoff message so the person knows where the conversation moved:
    ```bash
diff --git a/ai/skills/web-design/SKILL.md b/ai/skills/web-design/SKILL.md
index 896f5d5f..f7322972 100644
--- a/ai/skills/web-design/SKILL.md
+++ b/ai/skills/web-design/SKILL.md
@@ -9,10 +9,6 @@ These are personal defaults for building web interfaces. When a project
 has its own design system, component library, or established conventions,
 follow those instead.
 
-This skill grows over time. It currently covers semantic HTML, fluid
-layout (Utopia), and interactivity (Alpine.js); add sections as new
-preferences surface.
-
 ## Semantic HTML
 
 Lead with semantic HTML. Reach for meaningful elements — `main`,