project-checkin
Use when posting a recurring project check-in, morning status update, or daily standup-style message for a project or channel — gather schedules, thread context, and open decisions first, then post a tight check-in with deadline countdowns.
- License 许可
- Apache-2.0
- 最近更新
- 2026-10-02
- Stars
- ★ 6
- Forks
- 3
01 前言 Front Matter
- name
- project-checkin
- metadata
- { "tags": "check-in, status, project, recurring, standup", "version": "1.0.0", "display_name": "Project Check-in" }
- description
- Use when posting a recurring project check-in, morning status update, or daily standup-style message for a project or channel — gather schedules, thread context, and open decisions first, then post a tight check-in with deadline countdowns.
02 资源文件 1
- 参考文档references/example.md598 B
03 SKILL.md 正文
Goal
Run a recurring check-in the team actually reads: current state, open decisions, live deadlines — nothing else.
Steps
- Gather state before writing a word: active schedules, the channel/thread since the last check-in, workspace facts and graph commitments, and the open-decision list from the previous check-in.
- Lead with a one-line project state: "On track for the 24th" or "At risk — decision 2 is the blocker."
- Enumerate open decisions as a SHORT numbered list. Restate each one verbatim from the prior check-in until it closes — same wording, same number, so nobody has to diff yesterday's message.
- Put a countdown on every live deadline: "7 days to June 18."
- If a target is at risk, offer the slip explicitly and make accepting it cheap: "totally fine to slip to Thursday — say the word."
- Close with exactly one concrete turnaround promise: "Revised timeline posted here by 2pm."
Rules
- Never pad. If nothing changed, the whole check-in is one line: "No movement since yesterday — decisions 1 and 2 still open."
- New information goes at the top, standing items below it.
- Decisions and deadlines come from gathered state, never from memory of what "should" be open.
- One turnaround promise, not a list of intentions — and keep it.
See references/example.md for a complete example check-in.
04 同仓库更多 Skills
demo-skill
Use when the user asks to run the demo analysis workflow on a dataset.
youtube-transcript
Use when asked to get a transcript, extract key points, or summarize a YouTube video — given a YouTube URL.
weekly-status-report
Use when asked to compile a weekly status update, team recap, or progress report from recent channel activity, tasks, or notes.
weekly-channel-digest
Use when asked to digest a channel's week, recap what happened in a channel, catch someone up on a channel, or post a recurring "this week in
thread-recap
Use when asked to recap this thread, summarize the discussion above, TL;DR a long thread, or pull the decisions and action items out of the conversation right here — work from the live Slack thread in front of you and post a tight recap back into it.
theme-factory
Use when asked to create, adapt, or apply a visual theme — color palette, typography system, component tokens — for a product, document, or presentation.