procurement-dashboard-snapshot

Writes live procurement data as JSON snapshots to gbrain for dashboard tabs.

1|Updated Jun 21, 2026
One-click install
npx skills add https://github.com/tapway/shogun-os --skill procurement-dashboard-snapshot-tapway
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: procurement-dashboard-snapshot
Source: https://github.com/tapway/shogun-os/tree/main/skills/procurement/procurement-dashboard-snapshot
Command: npx skills add https://github.com/tapway/shogun-os --skill procurement-dashboard-snapshot-tapway

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml, and includes scripts (resource) components.

What problem does it solve? Procurement dashboards often display stale mock data because there is no automated bridge between live inventory, purchase order, and vendor records and the dashboard backend. This Skill closes that gap by computing the full 5-tab dashboard payload and writing it as JSON snapshots that the dashboard reads automatically. ## Core Features & Use Cases - Five Snapshot Writers: Generates inventory, purchase-orders, vendors, stock-movements, and accounting-bridge JSON snapshots covering all dashboard tabs (Pulse, Inventory Catalog, Stock Movements, PO & Vendors, Accounting Bridge). - Idempotent and Empty-Brain-Safe: Every run fully recomputes and overwrites each snapshot; an empty brain produces zeroed payloads and exits cleanly without crashing. - Flexible Triggers: Run via the /refresh-procurement-dashboard slash command, a daily 7AM cron before standup, or manually with a --dry-run flag to preview payloads. - Use Case: After a bulk inventory update, run the snapshot writer so the procurement dashboard immediately reflects current SKU counts, open PO values, vendor scorecards, and accounting sync status. ## Quick Start Ask the procurement agent to refresh the dashboard snapshots now, or run the write_snapshots.py script with the --dry-run flag to preview the JSON payloads before writing them to gbrain.

Frequently Asked Questions about procurement-dashboard-snapshot

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

FAQPage Schema
How do I refresh a procurement dashboard with live data?

Run the write_snapshots.py script or trigger the /refresh-procurement-dashboard slash command. It reads inventory, purchase orders, vendors, and stock movements from the brain, then writes five JSON snapshot files the dashboard backend reads automatically.

What data does the procurement dashboard snapshot include?

Snapshots cover five tabs: inventory valuation and SKU catalog, purchase order pipeline and executive approval queue, vendor scorecards and spend concentration, stock movement audit with shrinkage flags, and accounting bridge sync status.

Does the snapshot writer work when the procurement gateway is down?

Yes, it degrades gracefully. The standalone script reads the brain directory directly using the same frontmatter parsing pattern as the MCP tools, and if data is absent it writes zeroed snapshots and exits with code 0 instead of crashing.

Can I preview dashboard snapshots without writing them?

Yes, run write_snapshots.py with the --dry-run flag. It prints each computed JSON payload to stdout without writing any files, letting you verify the data before committing snapshots to gbrain.

When should I not use point-in-time dashboard snapshots?

Avoid snapshots for real-time streaming updates, since they only capture data at run time. ABC Pareto analysis is also excluded because it is computed client-side from the sku_catalog, and individual item lookups belong in dedicated item management tools.