Update to Shape Construction

{
  "description": "Write a short catch-up on one Shape project from its live data - open and critical issues, the latest shift report and any time lost. Use when the user asks for a site update, project catch-up or morning briefing from Shape.",
  "included_files": [],
  "name": "site-briefing",
  "skill_md_contents": "---\nname: site-briefing\ndescription: Write a short catch-up on one Shape project from its live data - open and critical issues, the latest shift report and any time lost. Use when the user asks for a site update, project catch-up or morning briefing from Shape.\n---\n\n# Site briefing\n\nBuild a briefing for one project the user names. Everything comes from Shape's\nread-only tools; never say that anything in Shape was changed.\n\n1. Find the project with `list_projects`. If the name matches more than one\n   project, or none, ask the user which one they mean.\n2. Issues: call `list_issues` for the project. Report how many are open, then\n   name the critical ones and any that are causing a delay, with their issue\n   references.\n3. Site activity: call `list_shift_reports`, then `get_shift_report` and\n   `get_shift_report_sections` for the most recent one. Summarise the work\n   done, how many people were on site and any time lost, with its cause.\n4. Close with up to three points that need attention, each tied to an issue\n   or shift report from steps 2 and 3.\n\nRules:\n\n- Use only what the tools return. If a section has no data, say so in one\n  line rather than guessing.\n- Give dates in the project's timezone (`get_project`).\n- Keep it to about 200 words unless the user asks for more.\n- Leave out email addresses and other personal details the user didn't ask\n  for.\n"
}