AGENT SKILL

friday

End-of-week wrap-up for the weekly report. Use on Fridays, when closing out the week, or when the user says "friday", "week close", or "wrap up week".

License 许可
MIT
所属仓库
caezium/skills
最近更新
2026-08-24
Stars
★ 3
Forks
0

01 前言 Front Matter

name
friday
description
End-of-week wrap-up for the weekly report. Use on Fridays, when closing out the week, or when the user says "friday", "week close", or "wrap up week".
allowed-tools
Read, Edit, Glob, Grep, mcp__playground-slack-mcp__get_messages

03 SKILL.md 正文

Friday Wrap-Up

Help complete the weekly report with wins, blockers, and carry-forward items.

Context: Zone Separation

The weekly report has two zones: manual (human-written) and auto-generated (skill output). This skill only writes into the auto-generated zone under ## Friday Wrap-Up. It never touches manual sections (Focus, Log, Decisions Made).

Steps

  1. Find current week's report in YYYY/w##-mm-dd/weekly-report-*.md

  2. Scan for incomplete tasks:

    • Check all - [ ] items in Time Blocks section
    • Check meeting notes in the week folder for unchecked Next Steps
    • List what's incomplete
  3. Prompt for Wins (interactive mode):

    • Review the Log section for accomplishments
    • Ask user to confirm or add wins
  4. Prompt for Blockers (interactive mode):

    • Ask if anything is stuck or waiting on others
  5. Populate Carry Forward:

    • Move incomplete Time Block items to Carry Forward
    • Add any incomplete meeting action items
    • Use Tasks emoji format for due dates: 📅 YYYY-MM-DD
    • Ask if anything else should carry over (interactive mode)
  6. Scan Slack for decisions:

    • Use mcp__playground-slack-mcp__get_messages with action: my_messages
    • Time range: This week (Monday to Friday)
    • Pattern match for decision language:
      • "decided to", "decision:", "the call is"
      • "agreed on", "agreed to", "we'll go with"
      • "chose to", "choosing", "selected"
      • "approved", "signed off on"
      • "not doing", "won't pursue", "deprioritizing"
      • "the plan is", "moving forward with"
      • "resolved to", "committed to"
    • Present decisions not already in weekly report's Decisions Made table
    • Ask user if any should be logged (interactive mode)
    • Skip gracefully if Slack MCP unavailable
  7. Summarize the week: wins count, blockers count, items carrying forward.

Output Format

All Friday-generated content goes under a single ## Friday Wrap-Up heading. This separates auto-generated content from manually written sections. Use ### subheadings within it.

When updating the report, do NOT write into existing sections like ## Wins or ## Blockers. Instead, write under ## Friday Wrap-Up (before any ## Daily Roundup sections).

## Friday Wrap-Up

### Wins
- Win from this week
- Another win

### Blockers
- Blocker identified
- Another blocker

### Carry Forward

_From W##:_
- [ ] Incomplete item from Time Blocks 📅 2025-01-10
- [ ] Action item from meeting

_From W##:_ (prior weeks, if carrying forward)
- [ ] Older incomplete item

### Slack Decisions
| Date | Channel | Decision | Logged? |
|------|---------|----------|---------|
| M/DD | #channel | Decision summary | ? |

Slack Decisions Prompt (interactive mode)

When Slack decisions are found, prompt user:

#### Slack Decisions to Log?

Found decision language in Slack this week:

- **#[channel]** ([date]): "[Decision quote]"
  - Project: [[likely-project]]
  - Add to weekly report? [Y/N]

- **DM with [person]** ([date]): "[Decision quote]"
  - Project: [unclear]
  - Add to weekly report? [Y/N]

Notes

  • Don't remove checked items from Time Blocks (they're a record)
  • Ask before adding items to Carry Forward when running interactively (user may want to drop them)
  • Keep summaries concise: one line per item
  • Add 📅 due dates to carried items when there's a clear deadline
  • All output must go under ## Friday Wrap-Up. Never write directly into manually curated sections (Focus, Log, Decisions Made)
  • When running headlessly (via automation), make best judgment on what to include without prompting

04 同仓库更多 Skills

caezium
caezium/skills

writing-for-agents

Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.

内容创作者写作与文案
★ 3
caezium
caezium/skills

wrangler

Cloudflare Workers CLI for deploying, developing, and managing Workers, KV, R2, D1, Vectorize, Hyperdrive, Workers AI, Containers, Queues, Workflows, Pipelines, and Secrets Store. Load before running wrangler commands to ensure correct syntax and best practices. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.

后端与接口
★ 3
caezium
caezium/skills

workers-best-practices

Reviews and authors Cloudflare Workers code against production best practices. Load when writing new Workers, reviewing Worker code, configuring wrangler.jsonc, or checking for common Workers anti-patterns (streaming, floating promises, global state, secrets, bindings, observability). Biases towards retrieval from Cloudflare docs over pre-trained knowledge.

★ 3
caezium
caezium/skills

wizard

Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.

★ 3
caezium
caezium/skills

why

Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available evidence sources, searches each relevant category, and returns a cited read on decisions and tradeoffs. Use how for runtime behavior.

★ 3
caezium
caezium/skills

week-prep

Generate a briefing with calendar, tasks, and attention flags. Use for "week prep", "briefing", or "what's on this week".

Skill与智能体开发
★ 3