reports
Use when creating, previewing, updating, scheduling, or exploring Costory reports. Route by intent: scheduled Slack/Teams/email sharing (Schedule — ask before build) vs explain last-month cost with preview-first DIGEST (Explain — chat preview required; not query+compare). Workflows are named, never lettered. DIGEST AI is opt-in via display: \"summary\" and/or enableAiInvestigation — both slower. Covers GRAPH_SNAPSHOT, TOP_FLOP, DASHBOARD_PDF, context-first inheritance, destinations after channel type is known, and delivery safety. Call get_skill with skillId \"reports\" before create_report or substantial report work.
costory-io · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add costory-io/costory-finops-mcp-skills --skill reports技能说明
name: reports description: "Use when creating, previewing, updating, scheduling, or exploring Costory reports. Route by intent: scheduled Slack/Teams/email sharing (Schedule — ask before build) vs explain last-month cost with preview-first DIGEST (Explain — chat preview required; not query+compare). Workflows are named, never lettered. DIGEST AI is opt-in via display: "summary" and/or enableAiInvestigation — both slower. Covers GRAPH_SNAPSHOT, TOP_FLOP, DASHBOARD_PDF, context-first inheritance, destinations after channel type is known, and delivery safety. Call get_skill with skillId "reports" before create_report or substantial report work."
Reports
Skill body version 0.5.3. Workflows here are named — Schedule, Explain, Update, Run, Explore. Older bodies lettered them A–E, and other Costory surfaces used a different letter order. If you are holding a lettered routing table for reports, it is stale: route by the names in this body and ignore the letters.
A report has a shared reportContext input (global theme) and widgets that inherit it by default. It delivers those widgets (chart snapshot, PDF, top/flop, text, or DIGEST cost-change tree) to one or more destinations (Slack, Teams, email). Same mental model as dashboards: shared context + per-widget overrides. create_report, update_report, and preview_report_widget all take the same report-level reportContext.
Temporary compatibility: the deprecated top-level
contextalias is accepted during migration, but always generatereportContext. Never send both.
Load this skill first for any report creation, DIGEST preview, substantial update, or delivery conversation.
Must-follow rules
Everything below this section is detail. These eight are the contract:
- Ask before build (Schedule / delivery). Do not pick widgets, call
preview_report_widget, or callcreate_reportuntil the design is confirmed. Never silently default to a graph or an AI summary on Schedule. - Explain exception — preview-first DIGEST. For one-shot "what changed / explain last month" (Explain workflow or
explain-period-changerecipe), defaulting to DIGEST chat preview is required. Do not wait for a full design questionnaire; do not substitutequery+comparefor the first answer. - Context-first. Once answers are in, define the full
reportContextbefore listing widgets. Widgets carry only overrides — never duplicate what already lives inreportContext. - Destinations last. Do not call
list_available_destinationsuntil the user has named the channel type (Slack / Teams / email). Then list only that type and propose matches by name — never paste a whole channel list into the conversation. - AI features are opt-in. DIGEST-only. Set
display: "summary"for the executive narrative and/orenableAiInvestigation: truefor per-node deep analysis — both default off (tree-only) and are slower. - Confirm delivery. Both
NOWandSCHEDULEDneed explicit confirmation beforecreate_report.UNSCHEDULEDdoes not. datePreset, never frozen dates, onSCHEDULEDreports.- Cost data is ~2 days late. Prefer a Tuesday weekly send (
weekday: 2) when the period isLAST_WEEK(a completed calendar week). If the report must land earlier (e.g. Monday), useTRAILING_7_DAYSinstead ofLAST_WEEKso the window is not a half-empty calendar week.
Routing
| User intent (examples) | Workflow |
|---|---|
| "Generate a scheduled report / message for Slack, Teams, or email" | Schedule |
| "I want to share FinOps information with my team" (recurring or channel delivery) | Schedule |
| "I need to explain last month's cost" / "what changed last month and why" | Explain (NOW + DIGEST) |
| Update an existing report | Update |
| Run / retry / transfer / archive | Run |
| Explore a delivered DIGEST execution | Explore |
If intent is ambiguous between Schedule and Explain, ask: recurring delivery to a channel, or one-shot explanation of last month's costs?
Tool order
get_skillwithskillId: "reports"— this guideget_context— org context, currency, popular groupBys- Several organizations: if
get_contextreturns "Multiple organizations" with a list of slugs, do not pick one. Ask the user which org to use (from that list orlist_organizations), then pass thatslugtoget_contextand the following tool calls. If the user already named the org (e.g. "orgacme"), use that slug directly.
- Several organizations: if
list_teams— only when team scoping may apply; each scope'sidis thescopeIdvaluesuggest_groupby— when a DIGEST hierarchy is open-ended; needs the planned period + the report's scope filterlist_available_destinations— only after the channel type is known, and only for a delivered reportpreview_report_widget→create_report/update_report— only after the design brief is confirmed
Destination discovery is a late step, not a warm-up. An org can have dozens of Slack channels; enumerating them before the user has said "Slack" (or "Teams", or "email") buries the design conversation in noise. Once the type is known, list only that type — and if the filtered list is still long, ask for a channel name or keyword and match against it rather than echoing every entry.
Workflow: Schedule — create a scheduled report
Triggers: scheduled message for Slack / Teams / email; share FinOps information with a team on a cadence.
Goal: accompany the user to design a recurring report they will actually use, then create a SCHEDULED report. Do not assume DIGEST or jump to create.
Tone: collaborative design partner. Explain options in plain language, offer concrete starters, confirm a short design brief before any preview or create. The user should feel guided, not interrogated with a long form.
1 — Open the design conversation
Acknow
阅读完整来源 ↗