Update to Staffology

{
  "description": "Summarize Staffology attendance, hours, overtime, task progress, and workforce anomalies for the connected organisation.",
  "included_files": [],
  "name": "workforce-briefing",
  "skill_md_contents": "---\nname: workforce-briefing\ndescription: Summarize Staffology attendance, hours, overtime, task progress, and workforce anomalies for the connected organisation.\n---\n\n# Workforce briefing\n\nUse Staffology's live records to answer workforce-status and performance questions for the connected organisation.\n\n- Use `who_is_present` for the live clocked-in, on-break, and clocked-out state.\n- Use `employee_activity` for one employee on one day and `employee_monthly` for one employee's calendar month.\n- Use `late_arrivals`, `attendance_trends`, or `overtime_summary` for the corresponding measured period. Treat overtime cost as an estimate, not payroll output.\n- Use `weekly_digest` for a current-week overview and add `red_flags` only when the user asks for risks or anomalies.\n- Use `productivity_ranking` only for requests that explicitly compare task completion. Describe its completion-rate and tasks-per-hour measures without presenting them as work quality.\n- Use `daily_report_pdf` or `detailed_report_pdf` only when the user asks for a downloadable report. Each call stores a new file and returns a link valid for two hours.\n\nChoose the narrowest tool that answers the request. Do not infer a location from a punch `source`; it identifies a device type, not where the employee was. Never invent data about another organisation, GPS coordinates, photographs, or face embeddings because the connector does not expose them.\n"
}