Analyze P&L and performance by department. Creates departmental reports and comparative analysis with Excel and PowerPoint outputs.
How to install departments?
datarails/dr-claude-code-plugins-re/departments
$npx -y skills add datarails/dr-claude-code-plugins-re --skill departmentsInstalls into the current project.
›Prefer a prompt? Paste this to your agent
Run `npx skills use "https://github.com/datarails/dr-claude-code-plugins-re" --skill "datarails/dr-claude-code-plugins-re/departments"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/datarails/dr-claude-code-plugins-re" that are relevant to the current task. Run `npx skills add "https://github.com/datarails/dr-claude-code-plugins-re"` and select the relevant skills, then follow their instructions.
SKILL.md
| 1 | # Department Analytics Agent |
| 2 | |
| 3 | A specialized agent for analyzing departmental P&L and performance. |
| 4 | |
| 5 | ## Description |
| 6 | |
| 7 | Analyzes financial performance by department. Creates departmental reports for team leads and management. |
| 8 | |
| 9 | Perfect for departmental reviews, budget planning, and performance assessment. |
| 10 | |
| 11 | ## Capabilities |
| 12 | |
| 13 | - Departmental P&L analysis |
| 14 | - Excel department packs |
| 15 | - PowerPoint department reviews |
| 16 | - Comparative analysis |
| 17 | - Per-employee metrics |
| 18 | |
| 19 | ## Data-Scope Rules |
| 20 | |
| 21 | > **Async fetch — aggregations and distinct values run as start → poll.** `start_aggregation_by_id`/`_by_alias` and `start_distinct_values_by_id`/`_by_alias` take the same arguments as the retired blocking calls (dimensions/metrics/filters; table id + field id, or alias + field alias) and return immediately with `{"status": "pending", "handle": {...}}`. Echo that `handle` back verbatim to the matching `get_aggregation_result_by_*` / `get_distinct_values_result_by_*` tool: a `{"status": "running", "retry_after_seconds": N}` response means poll again with the same handle after ~N seconds (≈5s) — it is not an error, and large jobs may take several polls; when ready, the result arrives in the familiar shape (for distinct values, pass `limit` to the result tool). An expired/unknown-handle error means restart with the `start_*` tool. *Transitional fallback:* if the `start_*` tools aren't available on the connector (older server), the blocking twins `get_aggregated_data_by_*` / `get_distinct_values_by_*` still work with the same arguments. |
| 22 | |
| 23 | > **Scenario domain.** Pull distinct values of the scenario field (`start_distinct_values_by_alias`/`_by_id` → poll the matching result tool) — never assume a scenario name exists (`Budget` frequently doesn't; many orgs carry only `{Actuals, Forecast}`). For budget/plan questions, if no budget-like scenario exists, look for a planning-version-like field (alias/name matching `/plan|version|cycle|budget/i`) and use its versions as the plan side; if neither exists, say so and offer a comparison across the scenarios that do exist. |
| 24 | > |
| 25 | > **Period scope.** Default every departmental P&L question to the latest complete fiscal year (or trailing 12 closed months) — never an unscoped all-time total — and label every output with the period + scenario it covers. |
| 26 | |
| 27 | ## Use Cases |
| 28 | |
| 29 | - Monthly department reviews |
| 30 | - Budget planning and analysis |
| 31 | - Department head meetings |
| 32 | - Executive dashboards |
| 33 | |
| 34 | ## Output |
| 35 | |
| 36 | - Excel department analysis |
| 37 | - PowerPoint department review |
| 38 | - Departmental P&L details |
| 39 | - Comparative metrics |
| 40 | |
| 41 | ## Related Agents |
| 42 | |
| 43 | - `/dr-insights` - Trend context |
| 44 | - `/dr-dashboard` - KPI monitoring |
| 45 | - `/dr-reconcile` - Data validation |
Related
6 picksType
- stripe-best-practicesGuides Stripe integration decisions across API selection (Checkout Sessions vs PaymentIntents), Connect platform setup (Accounts v2, controller properties),…Jul 2026
- make-interfaces-feel-betterDesign engineering principles for making interfaces feel polished.Jul 2026
- clerkClerk authentication router. Use when user asks about Clerk CLI operations,Jul 2026
- okx-dex-marketHARD BLOCK — never use for prediction-market/Polymarket UpDown queries; route to okx-dapp-discovery when a named DApp…Jul 2026
- grimoire-polymarketQueries Polymarket market data and CLOB state, and manages CLOB orders via the Grimoire venue CLI wrapper backed by the official Polymarket CLI.May 2026
- clerk-billingClerk Billing for subscription management - render Clerk's PricingTableJul 2026
