Weekly status report
Write the weekly update from what actually happened (merged work, moved tickets, tracked figures) in the same shape as last week.
In Lobstack: Skills › Library › Add
What your agent will do.
A weekly update is due for a team, a project or a client, or last week's exists and this one has to match it.
- 01
Find last week's report first (in the files, or the last document you posted) and keep its sections and their order. A report that changes shape cannot be compared with itself.
- 02
Gather evidence for the period only: what merged, which tickets closed or moved, what shipped, the figures the report tracks. State the date range you used.
- 03
Write four sections in this order: Done (outcomes, not activity), Numbers (each figure beside last week's, with the change), Blocked (what, on whom, since when), Next (three items at most, each with an owner).
- 04
When a number moved for a dull reason — a holiday, a backfill, a renamed field — say so on the same line.
- 05
Mark a section missing when its source was unavailable. Never fill it from memory or copy last week's.
- 06
With three or more tracked figures, add a line chart of recent weeks in a chart fence.
- 07
Post it as a document titled with the week, then reply with the one sentence a reader should take from it. Ask before sending it to anyone outside this thread.
One page. If it runs long, cut from Done, never from Blocked.
The whole SKILL.md: 37 lines of Markdown.
Add it in the app from Skills › Library, or copy it and paste it into Skills › Add a skill.
---name: weekly-status-reportdescription: "Write the weekly update from what actually happened (merged work, moved tickets, tracked figures) in the same shape as last week."metadata: title: "Weekly status report" category: operations tags: [reporting, status]--- ## When to use this A weekly update is due for a team, a project or a client, or last week's existsand this one has to match it. ## How 1. Find last week's report first (in the files, or the last document you posted) and keep its sections and their order. A report that changes shape cannot be compared with itself.2. Gather evidence for the period only: what merged, which tickets closed or moved, what shipped, the figures the report tracks. State the date range you used.3. Write four sections in this order: Done (outcomes, not activity), Numbers (each figure beside last week's, with the change), Blocked (what, on whom, since when), Next (three items at most, each with an owner).4. When a number moved for a dull reason -- a holiday, a backfill, a renamed field -- say so on the same line.5. Mark a section *missing* when its source was unavailable. Never fill it from memory or copy last week's.6. With three or more tracked figures, add a line chart of recent weeks in a chart fence.7. Post it as a document titled with the week, then reply with the one sentence a reader should take from it. Ask before sending it to anyone outside this thread. One page. If it runs long, cut from Done, never from Blocked.
- Operations
Spreadsheet cleanup
Clean a messy spreadsheet or CSV (headers, types, duplicates, blanks, inconsistent values) into a tidy copy, with a log of every change.
SKILL.md · App - Operations
Onboarding guide
Write an onboarding guide for someone new from the existing docs, repos and chat: day-one setup, who to ask, and a first real task.
SKILL.md · App - Operations
Write a runbook
Turn a task someone does by hand into a runbook: exact steps and commands, a check after each, what to do when one fails, and how to undo it.
SKILL.md · App - Operations
Scheduled check
Run a named checklist on a schedule, compare with the last run, and report only what changed or failed. Never fixes anything on its own.
SKILL.md · App - Engineering
Commit message from a diff
Write a commit message from a diff: a subject line that states what was found, then prose explaining why the change was made.
SKILL.md · App - Engineering
Triage a failing build
Triage a red CI run: find the first real failure, attribute it to a change, and say whether the code is wrong or the runner was.
SKILL.md · App