| name | TODO-name-this-skill |
| description | TODO. One line. Say what the Skill does and that it only summarizes. The description is how Cowork decides when to run this and how a teammate would run it without asking you. Keep the words "summary only; never sends or posts." |
TODO: title your digest Skill
Use this scaffold to build the Skill you will schedule. Fill in every TODO. Keep the rules at the bottom. Do not put any passwords, tokens, or private data in this file. A Skill holds instructions, not secrets.
What this Skill does
TODO: in one or two lines, say that it reads this week's outputs and produces a short readiness digest saved to this folder.
Steps
- Read these files in the working folder:
- TODO: list the four files in
inputs/week-outputs/ by name.
- For each file, write a short status.
- TODO: say how long each status should be (2 to 3 lines).
- Quote the budget numbers exactly.
- TODO: name which figures to quote word for word from the budget summary (total and percent committed), so they can be checked against the source.
- Add a top-risks list.
- TODO: say to pull the risks from the statuses above.
- Name next Friday's focus.
- TODO: say to point at what still has to happen before launch week.
- Save the result.
- TODO: name the output file (for example,
friday-digest.md) and say to save it in this folder.
Rules (keep these)
- Summary only. Do not send, post, email, or write anywhere outside this folder.
- Quote the budget figures exactly so they can be verified against the source file.
- This Skill is safe to schedule only while these rules hold.
