legal-productivity-report

Generates overdue-ticket and team-productivity reports from Jira data filed to SharePoint.

Updated Apr 30, 2026
One-click install
npx skills add https://github.com/myPOStech/mps-legal-legalcopilot-ai --skill legal-productivity-report-mypostech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: legal-productivity-report
Source: https://github.com/myPOStech/mps-legal-legalcopilot-ai/tree/main/skills/legal-productivity-report
Command: npx skills add https://github.com/myPOStech/mps-legal-legalcopilot-ai --skill legal-productivity-report-mypostech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Legal team leads lack visibility into who is overloaded, who is behind on deadlines, and which tickets have slipped, especially since much legal work never appears in Jira. This Skill compiles Jira metrics and manually entered off-Jira hours into a single .docx report filed to SharePoint. ## Core Features & Use Cases - Overdue and workload analysis: Pulls overdue tickets, closed-ticket counts, median time-to-close, and recent status transitions per lawyer via JQL queries. - Off-Jira hours capture: Prompts the report runner for each lawyer's off-Jira hours so invisible work is accounted for without timesheets. - Composite status heuristics: Flags lawyers as AT RISK, OVERLOADED, or OK, with UNDER-UTILISED kept in a private head-of-legal section only. - Use Case: The head of legal runs /legal-report at month end to get a .docx showing 12 overdue tickets, two overloaded lawyers, and the matter types slipping most, filed automatically to SharePoint. ## Quick Start Ask the assistant to run the legal productivity report for the last 30 days and file it to SharePoint.

Frequently Asked Questions about legal-productivity-report

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a legal team productivity report from Jira?

Run the /legal-report command, optionally with a date range like last_7_days, last_30_days, this_quarter, or an explicit YYYY-MM-DD range. The skill queries Jira for overdue and closed tickets, prompts for off-Jira hours, and produces a .docx report filed to SharePoint.

How to track overdue Jira tickets per assignee?

The skill runs a JQL query for tickets with duedate before now and statusCategory not Done, then computes days overdue per assignee. Tickets assigned within the last 24 hours are excluded so new assignees are not unfairly counted.

Can the report account for legal work done outside Jira?

Yes, the skill prompts the person running the report for each lawyer's off-Jira hours, such as calls and unfiled drafting. If skipped, the value is recorded as null and the lawyer's section is tagged as not recorded; hours are never fabricated.

Does the productivity report label underperforming lawyers publicly?

No. The UNDER-UTILISED status never appears in the shareable body of the report. It is surfaced only in a clearly marked private section for the head of legal, since off-Jira work is invisible to Jira metrics alone.

Where is the generated legal report stored?

The rendered .docx is filed to SharePoint under myPOS Legal/Reports/Productivity via the n8n filing workflow, using a synthetic case id based on the date range. A summary is also written to the legal copilot memory file for trend tracking.

What are the limitations of Jira-based productivity metrics?

Jira metrics only capture ticketed work, so velocity and load figures miss calls, informal advice, and unfiled drafting. The report mitigates this with manually entered off-Jira hours, but its accuracy depends on the honesty of that input.