# cloud-cost-digest

Adopt this skill: https://proskills.md/skills/other/kesslernity-awesome-copilot-cowork-bots-packs-finance-finops-cloud-cost-digest-s

Page: https://proskills.md/skills/other/kesslernity-awesome-copilot-cowork-bots-packs-finance-finops-cloud-cost-digest-s
This document is the public skill bundle for that page. It contains SKILL.md and every helper file the catalog carries. No login is required.

## File: packs/finance-finops/cloud-cost-digest/skill/SKILL.md
size: 3232
sha: bd68ca0a62282994adfd528609510c6df5aec61d
upstream: https://github.com/kesslernity/awesome-copilot-cowork-bots/blob/main/packs/finance-finops/cloud-cost-digest/skill/SKILL.md

```text
---
name: cloud-cost-digest
description: Turns cloud billing exports and provider alert emails into a short digest of what moved, what is anomalous and what to ask an owner about. Use when the user asks about cloud spend, what changed on the bill, why costs went up, to prepare a FinOps review, or to explain a cost spike.
---

# Cloud Cost Digest

Explains what moved on the bill, with the question to ask each owner.

## Inputs
- A billing export the user supplies, through **Excel**
- Provider alert and budget emails, through **Email**
- `references/config.md` for the materiality floor, owner mapping and the comparison period

## Procedure
1. **Load the export.** Without it, say so and stop. Alert emails alone cannot produce a digest;
   they can produce an alert summary, which is a different and lesser thing.
2. **Compare** the current period against the comparison period in config, by service and by the
   tag or account that config names as the ownership dimension.
3. **Surface only movement above the materiality floor**, in absolute and percentage terms both.
   A 400% rise on 12 units of currency is noise and must not lead the digest.
4. **For each movement, state** the service, the owner from the mapping, the absolute change, the
   percentage, and whether anything in the mailbox explains it: a deployment notice, a budget
   alert, a migration thread.
5. **Separate facts from inference explicitly.** "Spend rose 38%" is a fact from the export.
   "Likely the new environment stood up on the 14th" is an inference and must be labelled.
6. **Write** the digest and attach the per-service table.

## Output
Digest, in this order: total for the period against comparison; the three largest movements with
owner and probable cause; anomalies with no explanation found; then the full table.

| Service | Owner | This period | Comparison | Change | Change % | Explanation | Evidence |

## Definition of done
Every movement above the floor appears, every one names an owner or says OWNER UNKNOWN, and every
explanation is labelled fact or inference.

**A flat month is a result.** Say "no movement above the floor" and stop.

## When there is no data
- No export: stop, say what is needed.
- Tags missing so ownership cannot be derived: produce the digest with OWNER UNKNOWN and say how
  many rows that affects. Do not guess an owner from a service name.
- Comparison period incomplete: state the actual dates compared.

## Boundaries
- Never state a forecast as a commitment.
- Never recommend terminating, resizing or deleting a resource. Surface the movement and the
  question; the owner decides.
- The provider's own billing console is the source of truth. This reads an export.
- Never share account identifiers outside the organization.
- **Read only, and draft only.** This skill reads an export and writes a digest for the user. It
  never opens a ticket, never emails an owner, and never changes a budget or an alert. Sending
  the digest to anyone is the user's action, behind the normal approval prompt.

## Self-check
- Is every percentage paired with an absolute, so small numbers cannot lead?
- Is every explanation labelled fact or inference?
- Did I avoid recommending any change to a resource?
```

## File: packs/finance-finops/cloud-cost-digest/skill/references/config.md
size: 339
sha: 3e074ff3a246c87f805ad0fa6404a61fb6aa5e2f
upstream: https://github.com/kesslernity/awesome-copilot-cowork-bots/blob/main/packs/finance-finops/cloud-cost-digest/skill/references/config.md

```text
# Cloud Cost Digest config
- `materiality_floor: 500`        # currency units of absolute change. Below this, ignore
- `comparison: previous calendar month`
- `ownership_dimension: tag:owner` # or account, subscription, resource group

## Owner mapping
Used when the ownership dimension is missing or unreadable.
- (tag value) -> (person)
```

## File: README.md
upstream: https://github.com/kesslernity/awesome-copilot-cowork-bots/blob/main/README.md

```text
# Copilot Cowork Bots

Agent designs that work inside the Microsoft 365 boundary: your identity, your permissions, your
approval gates, your audit trail.

[![GitHub stars](https://img.shields.io/github/stars/kesslernity/awesome-copilot-cowork-bots?style=flat-square)](https://github.com/kesslernity/awesome-copilot-cowork-bots/stargazers)
[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg?style=flat-square)](LICENSE)
[![23 bots in 8 packs](https://img.shields.io/badge/bots-23%20in%208%20packs-blue.svg?style=flat-square)](#the-catalog)
[![One-page PDF per bot](https://img.shields.io/badge/guides-one%20page%20per%20bot-orange.svg?style=flat-square)](guides/)

> 🌐 **Prefer the web version?** All 23 bots on one page, nothing to clone, every guide
> downloadable: **[kesslernity.com/cowork-bots](https://www.kesslernity.com/cowork-bots?utm_source=github&utm_medium=readme&utm_campaign=cowork_bots_repo&utm_content=hero_site)**

Cowork can send an email, post in Teams, create a document and run a multistep job while you are
not watching. That is useful and it is also the reason every bot here ships **read-and-prepare
first**, with sending, posting and deleting behind an approval you give each time. The governance
is not a disclaimer at the bottom of this file. It is the design.

The designs are adapted from patterns proven in **Grok Bot**, which is reached through X
Subscription tiers and Cursor plans and runs on Cursor-operated infrastructure. Credit where it is
due: their documentation's discipline, automate preparation before execution, define the no-data
case, create a routine only once failure cases are defined, is better than most material written
about Copilot. What changed in the move is set out honestly in
[docs/conversion-guide.md](docs/conversion-guide.md), including the four of their seven published
roles that **do not port at all**.

Not affiliated with, or endorsed by, Microsoft, xAI or Cursor.

**Start here, free:** [Copilot on One Page](https://www.kesslernity.com/copilot-on-one-page?utm_source=github&utm_medium=readme&utm_campaign=cowork_bots_repo&utm_content=hero)
is the four-step loop every bot below sits on top of. One page, printable. Turning Cowork on for
the first time rather than installing a bot into it? The
[Day-0 Readiness Gate](https://www.kesslernity.com/copilot-day0-readiness?utm_source=github&utm_medium=readme&utm_campaign=cowork_bots_repo&utm_content=day0)
is the eight pass-or-fail checks to settle first.

---

## What you need

- A **Microsoft 365 Copilot** license, and **Cowork enabled by your admin**. Since general
  availability that means usage-based billing switched on plus a **spending policy that selects
  Cowork**, in Microsoft 365 admin center, Copilot, Cost management. The per-agent allow list
  from the preview is deprecated.
- 🔴 **That policy is an access control, not only a budget.** Anyone in its scope can use Cowork
  however small the limit; a one-credit limit still grants access. Enforcement is asynchronous,
  so a cap is a boundary rather than an instant stop.
- Cowork bills **Copilot Credits**: model responses, tool and skill calls and browser tasks all
  count.
- Cowork is limited to **Anthropic-supported regions**.
- **Cowork runs on mobile; uploaded custom skills do not.** Install and run these on a laptop.

## Install a bot in about two minutes

1. Download the bot's `.zip` from [`dist/`](dist/).
2. In Cowork, open **Customize** in the **left navigation**, then the **Skills** tab.
3. Select the arrow next to **Add**, then **Upload skill**, and choose the file.
4. Cowork validates it and saves it to your OneDrive at `/Documents/Cowork/skills/`.
5. **Start a new conversation.** Skills are discovered when a session begins, so one already open
   will not see it.

Then open the bot's `skill/references/config.md`, which is where the thresholds, names and
projects live. One skill serves many people because that file differs.

**Read before you upload.** Microsoft's own note: a skill runs as instructions to the AI, so
only upload skills from sources you trust, and Microsoft does not validate custom skills created
by users. Everything here is plain text; open the zip and read `SKILL.md` first. It takes about
two minutes.

**Test before you schedule.** Run a skill once on a quiet period and read what comes back before
anyone puts it on a clock. After editing `references/config.md`, re-upload or edit in place, then
start a **new** conversation: changes apply to new sessions only.

Full detail, including the manual OneDrive route: [docs/install.md](docs/install.md).

## Sending one to a colleague

[`guides/`](guides/) holds a one-page PDF for every bot, written for someone who has never
heard of Cowork: what it is, what this bot does, the five steps to install it, and what it will
never do without asking. Start with
[`00-start-here.pdf`](guides/00-start-here.pdf), or send
[`all-bots.pdf`](guides/all-bots.pdf) for the lot.

They are generated from the `SKILL.md` files, so they cannot quietly drift from the skills they
describe. How that works, and the two blocks that are written by hand instead:
[guides/README.md](guides/README.md).

## The budget nobody mentions

You can hold **50 custom skills** but only **25 scheduled prompts**. Skills are cheap, schedules
are scarce. Every bot here runs on demand, and a schedule is optional unless the bot card argues
for one. Installing all 23 costs under half your skill allowance.

## AI at Work newsletter, and a free course

📬 **AI at Work** is a biweekly briefing on Microsoft Copilot and enterprise AI: verified news,
tested prompts, and one honest insight. When something in this repo stops being true because
Microsoft changed it, that is where the correction gets explained rather than quietly committed.
👉 **[Subscribe free](https://newsletter.kesslernity.com/?utm_source=github&utm_medium=readme&utm_campaign=cowork_bots_repo&utm_content=newsletter)**.
No spam, no fluff, unsubscribe anytime.

🎓 **AI Quick Start Essentials** is a free 35-minute course on using AI at work without creating
a governance problem for someone else to find.
👉 **[Start the free course](https://trainings.kesslernity.com/?utm_source=github&utm_medium=readme&utm_campaign=cowork_bots_repo&utm_content=course)**:
no credit card, you just need an account.

---

## The catalog

<!-- CATALOGUE:start -->
**23 bots in 8 packs.** Every one ships as an upload-ready archive in `dist/`.

| Pack | Bot | What it owns |
|---|---|---|
| **Core / Executive** | [`calendar-defender`](packs/core-executive/calendar-defender/) | Reviews the week ahead for double-bookings, meetings with no agenda or no decision to make, and lost focus time, then proposes specific changes… |
| **Team Lead** | [`one-to-one-prep`](packs/team-lead/one-to-one-prep/) | Prepares a brief for a one-to-one with a named person: their open items, what they raised recently, what you owe them, and what has gone unanswered… |
|  | [`project-decomposer`](packs/team-lead/project-decomposer/) | Breaks a project, initiative or goal into owned tasks, each carrying its own verification criteria and a named owner, and returns one Adaptive Card… |
|  | [`team-lead-mode`](packs/team-lead/team-lead-mode/) | The orchestrator for a team lead's week. |
| **Finance & FinOps** | [`budget-variance-explainer`](packs/finance-finops/budget-variance-explainer/) | Drafts the narrative behind a budget variance from the context the user supplies and the discussion in mail and meetings, never producing or changing… |
|  | [`cloud-cost-digest`](packs/finance-finops/cloud-cost-digest/) | Turns cloud billing exports and provider alert emails into a short digest of what moved, what is anomalous and what to ask an owner about. |
|  | [`expense-reconciliation`](packs/finance-finops/expense-reconciliation/) | Reconciles submitted expense claims against the receipts and statements sitting in the mailbox, lists what is missing or unmatched, and drafts the… |
|  | [`invoice-ven
```
