CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

stripe-bfcm-dashboard

Builds a Black Friday and Cyber Monday (BFCM) season dashboard of payments, customers, and recurring revenue from the connected Stripe MCP account, as a hosted page in Claude on the web or desktop or a local page in coding agents. For the 2026 BFCM season only. Use when a merchant asks for a BFCM, Black Friday, Cyber Monday, holiday, holiday sales, or peak-season dashboard, such as "build me a holiday dashboard" or "build me a Cyber Monday dashboard," even without the word BFCM.

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

96%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a highly disciplined skill body: fixed rules, an unambiguous six-step workflow with explicit error stops, named tools and files, and a well-signaled one-level reference bundle verified to exist. The only structural nitpick is the inline loading-state design spec in Step 2, which slightly blurs the overview/detail split with dashboard-design.md.

DimensionReasoningScore

Conciseness

The body is dense, directive, and free of concept explanations Claude already knows — no primer on Stripe, dashboards, or BFCM. Every sentence carries operational content: fixed rules ("Don't ask which metrics, period, time zone, output, or account to use"), tool names, and exact specs, with no padded sections and no time-sensitive dates in the body. This matches the lean/every-token-earns-its-place anchor rather than the 4 anchor's 'minor instances of over-explanation'.

5 / 5

Actionability

Guidance is fully concrete: named tools (`list_available_accounts_or_orgs`, `get_stripe_account_info`), a decision table mapping each client to an output and reference file, exact account-matching rules ("whose `stripe_context` starts with `acct_`"), and exact colors, sizes, and timings for the loading state. For an instruction-only skill the guidance is copy-paste actionable, matching the top anchor; executable SQL and page code correctly live in the references.

5 / 5

Workflow Clarity

Six explicitly sequenced steps with ordering constraints ("Do this before reading any file or planning"), explicit decision points (client table, account selection with fallback for API-key sessions), and explicit validation/error checkpoints ("If the Stripe tools are missing, blocked, or need sign-in, say so in one line with the fix ... and stop. Don't produce an empty dashboard"; "If no account is listed ... and stop"). Query-level retry and polling are delegated to the queries reference, giving complete feedback loops for this read-only skill.

5 / 5

Progressive Disclosure

The body is a clean orchestration overview pointing to four real, one-level-deep reference files, each with a clearly signaled role ("<references/dashboard-design.md> for the layout, labels, and states, <references/queries.md> for the time windows, queries, responses, and calculations"), and the bundle confirms no nested reference chains. It stops short of the 5 anchor because Step 2 inlines roughly twelve lines of detailed loading-state design spec (colors, dimensions, animation timing) that overlaps dashboard-design.md's domain — a minor organization gap, albeit justified inline by the 'show progress before reading any file' constraint.

4 / 5

Total

19

/

20

Passed

Description

95%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is an exemplary trigger description: concrete about what is built and from where, explicit about when to fire with a full synonym set and example phrases, and tightly scoped to the 2026 BFCM season. Its only ceiling is that it describes one build action rather than a list of several distinct capabilities.

DimensionReasoningScore

Specificity

Quotes a concrete build action with specific data domains ("dashboard of payments, customers, and recurring revenue"), a concrete source ("from the connected Stripe MCP account"), and both output modes ("a hosted page in Claude on the web or desktop or a local page in coding agents"). It falls just below the 5 anchor because there is essentially one build action rather than the multiple distinct actions (extract/fill/merge/convert) the top anchor exemplifies, and above the 3 anchor because the single action is specified across data domains and delivery targets.

4 / 5

Completeness

Explicitly answers both questions: what ("Builds a Black Friday and Cyber Monday (BFCM) season dashboard of payments, customers, and recurring revenue from the connected Stripe MCP account") and when ("Use when a merchant asks for a BFCM, Black Friday, Cyber Monday, holiday, holiday sales, or peak-season dashboard"), with concrete trigger phrases included — a direct match to the top anchor.

5 / 5

Trigger Term Quality

Covers the full synonym set a merchant would naturally say — "BFCM, Black Friday, Cyber Monday, holiday, holiday sales, or peak-season dashboard" — and adds concrete example utterances ("build me a holiday dashboard" or "build me a Cyber Monday dashboard") plus the explicit note "even without the word BFCM". This matches the comprehensive-synonyms anchor; no common natural phrasing for this domain is missing.

5 / 5

Distinctiveness Conflict Risk

The niche is sharply bounded by "For the 2026 BFCM season only", the merchant audience, and the Stripe MCP data source, so it is unlikely to fire for generic dashboard, analytics, or non-Stripe skills. Clear distinct triggers with minimal conflict risk, matching the top anchor.

5 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

stripe/ai

Path

providers/agent-plugins/plugin/skills/stripe-bfcm-dashboard/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.