status-report
The status-report skill summarises where work stands. It reports on a single project, one client or the whole workspace, over a period you choose. Every report ends with an Engine Health section that shows whether anyone changed a critical engine file.
When Claude Uses It
Section titled “When Claude Uses It”Claude loads the skill when you ask for a status report or a progress update. You can also type /status-report to start it directly.
The /status command gives its own overview of all projects from the project register, with the same Engine Health section. Use /status for a quick view of everything. Ask for a status report when you want a written report on one project, one client or one period. See /status.
How It Works
Section titled “How It Works”- Claude sets the scope. It confirms whether the report covers one project, a client portfolio or the whole workspace. It also confirms the period, such as this week or dates you give.
- Claude gathers the information. It scans the relevant project folders, reads recent README updates, and looks for completed deliverables, open action items and blockers.
- Claude writes the report. It includes a summary, a breakdown by project, completed work, work in progress, upcoming deadlines, and blockers or risks.
- Claude presents it. You read it in the conversation, and Claude offers to save it to
Documentation/Reports/.
The Two Report Formats
Section titled “The Two Report Formats”A project status report gives the period and a short summary. It lists completed, current and upcoming work, then a table of blockers with their impact and proposed resolution, and the next steps.
A workspace status report gives the period and a table of active projects with their client, status and next milestone. It then lists completed work and the main activities, a table of upcoming deadlines, and any notes.
Engine Health
Section titled “Engine Health”At the end of every report, Claude runs the health check.
bash Infrastructure/Scripts/update-engine.sh --healthThe check compares each critical engine file with the copy published for the engine version your workspace runs. It changes none of your files and reports one of these results.
| Result | What it means |
|---|---|
| All critical files intact | Every critical file matches the published copy |
| Warning, with a list of files | Someone changed or deleted those files locally. The next /update puts the published copy back, and for settings.json it restores the missing engine permissions or hooks |
| Not checked, with a reason | Claude could not reach the published copy, for example when you are offline |
| Unable to read manifest | The engine manifest file is missing or unreadable |
If you see a warning, the next update overwrites the changes in those files. Move the change into a companion file instead, as described in Engine Protection.
Where It Takes Its Context
Section titled “Where It Takes Its Context”The skill reads the organisation name from .claude/company/overview.md for the report header and key contacts from .claude/company/team.md. It follows the Content Defaults rule for tone and the File Conventions rule for where to save reports.
Customising the Skill
Section titled “Customising the Skill”The skill file is .claude/skills/status-report/SKILL.md. It is a customisable engine file, so your edits survive /update through a three-way merge.
To add your own material, create a references/ folder inside .claude/skills/status-report/. It can hold branded report templates, the measures you track, billing summary formats or distribution lists.