Verified:GitHub

cost-extract

Extract Azure cost anomaly data from Outlook emails and Jira tickets into GitLab CSVs.

Updated Jul 22, 2026

Search Tags:#azure #csv #jira #gitlab #extraction #outlook #cost anomaly

One-click install

npx skills add https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc --skill cost-extract-trigent-software-pvt-ltd

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: cost-extract
Source: https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc/tree/main/plugins/cost-anomalies/skills/cost-extract
Command: npx skills add https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc --skill cost-extract-trigent-software-pvt-ltd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Azure cost anomaly alerts arrive scattered across Outlook emails and Jira tickets, making it hard to maintain a consolidated, queryable record of cost spikes and drops across subscriptions and resource groups. ## Core Features & Use Cases - Dual-source extraction: Parse cost anomaly alerts from Outlook emails and Jira tickets (daily, weekly, and monthly) in a single run, or target one source with --email or --jira. - Incremental sync with coverage tracking: Resume from the last extracted date using a _index.json cursor in the GitLab repository, with gap detection and overlap advisories. - Note enrichment: Attach human explanations from reply emails and Jira comments (optionally reading attachments) to each anomaly row. - Use Case: Run a weekly sync to append all new Azure cost anomalies from the past week into per-resource-group CSV files in the trigent1/devsecops/cost-anomalies GitLab project, deduplicated and schema-migrated automatically. ## Quick Start Ask the assistant to extract cost anomalies from last week, for example: run cost-extract for last week across both email and Jira sources.

Frequently Asked Questions about cost-extract

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

FAQPage Schema

How do I extract Azure cost anomaly alerts from Outlook emails?▼

Run the skill with the --email flag to search Outlook for "Cost anomaly detected" messages, parse subscription and resource group tables from each body, and append rows to per-resource-group CSVs in GitLab. Without flags it extracts from both email and Jira.

How do I sync Jira cost anomaly tickets into CSV files?▼

Use the --jira flag to query DEVSECOPS tickets via JQL for daily, weekly, and monthly cost anomaly issues, parse their anomaly tables, and write rows keyed by subscription, resource group, and resource name. Use --ticket to process a single ticket.

Does the extraction avoid duplicating already-collected anomalies?▼

Yes. A _index.json file in the GitLab repository tracks email_covered and jira_covered date ranges, so runs resume from the last covered date. Rows are also deduplicated against existing CSVs by date and observed_at or source key.

Can I filter cost extraction to a specific Azure subscription or date range?▼

Yes. Use --subscription to limit extraction to one subscription and --since/--until or natural ranges like "last week" or "June 1 - June 19" for dates. Subscription-filtered runs do not advance the global coverage cursor.

Why are baseline_usd and comparison_usd empty in extracted email rows?▼

Email alerts do not include absolute RG cost figures, so those columns are left empty at extract time. They are populated later by the companion cost-investigate skill when it fetches azure-cost data.