一键导入
Meeting prep for the next day's calendar, posted to a Slack Canvas.
npx skills add https://github.com/leighmcculloch/dotfiles --skill prep-daily复制此命令并粘贴到 Claude Code 中以安装该技能
Meeting prep for the next day's calendar, posted to a Slack Canvas.
npx skills add https://github.com/leighmcculloch/dotfiles --skill prep-daily复制此命令并粘贴到 Claude Code 中以安装该技能
| name | prep-daily |
| description | Meeting prep for the next day's calendar, posted to a Slack Canvas. |
Prepare a meeting-prep briefing for my meetings tomorrow (the next calendar day after this task runs) and prepend it to a Slack Canvas. Each run starts fresh with no memory of prior runs, so follow these steps end to end. I am leigh@stellar.org.
Write to the canvas using standard markdown. Prepend a new dated section at the very TOP of the canvas (latest entry always on top). Use a ## header for the day, formatted with the weekday and full date, e.g. ## Thursday, June 4, 2026.
Under the date header, one ### block per meeting in chronological order, structured like this:
### 9:00–9:30 AM — [Meeting title]
**Attendees:** Name, Name, Name
**Agenda:** ([agenda doc](url))
- Planned topic / discussion point
- Another topic
**Prior action items:**
- Action item text — Owner: Name
- Another action item — Owner: Name
**Context:**
- Short pointer to what an attendee is tracking or cares about ([#channel](slack-url))
- Another concise point ([thread](slack-url))
Formatting and link rules (important — links must render as clickable in Slack):
[label](url). This is what renders as a clickable link in a Slack Canvas. Do NOT use Slack mrkdwn <url|label> in the canvas — it does not render there.#channel, thread, or a person's name) so the canvas is easy to scan and navigate.### block per meeting.slack_update_canvas. Do NOT create a new canvas each run — update this existing one.slack_send_message, posting the full canvas URL on its own line so Slack auto-links it and I can click straight through.Create GitHub issues with context from linked issues/PRs
Create a GitHub pull request with AI-generated title and description based on the diff
A briefing for the day.
Pick a random small unassigned GitHub issue from a locally checked-out repo, implement it with an agent team, code-review and iterate until clean, then Slack DM the PR. Use when asked to "find an issue and fix it", "tackle an issue", "pick up an issue", or run autonomously on whatever's open.
Create a git branch with a concise kebab-case name describing the pending changes
Review a PR with the code-review skill, then post that feedback as inline draft comments with the pr-draft-comment skill. Use when asked to review a PR and leave the findings as pending/draft inline comments.