agency-sales-data-extraction-agent

Extracts MTD, YTD, and Year End sales metrics from Excel files into PostgreSQL.

Updated Jul 27, 2026
One-click install
npx skills add https://github.com/imMamdouhaboammar/Mimera --skill agency-sales-data-extraction-agent-immamdouhaboammar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agency-sales-data-extraction-agent
Source: https://github.com/imMamdouhaboammar/Mimera/tree/main/.agents/skills/sales-data-extraction-agent
Command: npx skills add https://github.com/imMamdouhaboammar/Mimera --skill agency-sales-data-extraction-agent-immamdouhaboammar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Sales teams receive performance reports as Excel files in varying formats, and manually copying MTD, YTD, and Year End metrics into a database is slow and error-prone. This Skill automates the monitoring, parsing, and persistence of those metrics for live internal reporting. ## Core Features & Use Cases - Automated File Monitoring: Watches designated directories for new or updated .xlsx and .xls files, ignoring temporary Excel lock files and waiting for writes to complete before processing. - Flexible Metric Extraction: Parses all workbook sheets, detects metric type (MTD, YTD, Year End) from sheet names, and maps columns flexibly across revenue, units, deals, and quota variants. - Audited Database Persistence: Bulk inserts validated metrics into PostgreSQL with transactions, matches representatives by email or name, and logs every import with row counts and timestamps. - Use Case: A sales operations team drops weekly regional Excel reports into a shared folder; the agent automatically extracts each representative's revenue and quota attainment, stores them in PostgreSQL, and emits a completion event for downstream dashboards. ## Quick Start Monitor the sales reports folder and extract all MTD, YTD, and Year End metrics from any new Excel files into the database.

Frequently Asked Questions about agency-sales-data-extraction-agent

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

FAQPage Schema
How do I automatically extract sales metrics from Excel files?

Set up a filesystem watcher on the directory where Excel reports arrive, then parse each workbook's sheets and map columns to metrics like revenue, units, and quota. This agent detects metric type from sheet names and bulk inserts validated rows into PostgreSQL.

How to handle Excel files with different column names for the same data?

Use fuzzy column name matching that maps variants like revenue, sales, or total_sales to a single canonical field. The agent applies this flexible schema mapping for revenue, units, deals, and quota columns across differing report formats.

Can the agent process Excel files while they are still being written?

No, it waits for file write completion before processing and ignores temporary Excel lock files prefixed with ~$. This prevents parsing incomplete or corrupted workbooks.

What happens when a sales row cannot be matched to a representative?

Unmatched rows are skipped with a warning rather than inserted. Representatives are matched by email or full name, and every import is logged with rows processed and rows failed for a complete audit trail.

Does the extraction overwrite existing sales metrics in the database?

No, existing metrics are never overwritten without a clear update signal such as a new file version. Inserts use transactions for atomicity, and each metric row records its source file for traceability.