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

92%

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

The canonical home for this skill is stripe-bfcm-dashboard in stripe/ai

SKILL.md
Quality
Evals
Security

Quality

Content

86%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.

A well-engineered skill body: fixed rules up front, a crisp six-step workflow with real error checkpoints, and disciplined one-level-deep reference structure with a fallback URL. The residual weaknesses are minor — some state detail inlined in Step 2 that could live in the design reference, and no explicit handling for query failures in the body itself.

Suggestions

Move the pixel-level loading-state specification from Step 2 into dashboard-design.md's States section (keeping only 'publish the loading artifact per the spec in the reference') to cut duplicated detail, since that file is read immediately after in Step 4 anyway.

Add an explicit checkpoint in Step 5 or 6 for failed or empty query runs — e.g., retry once, then render the reference's no-data state and tell the user — to close the workflow's main validation gap.

Merge Steps 5 and 6 (or fold them into Step 4's read instruction) since both are single-line pointers to the same output reference, trimming two near-empty sections.

DimensionReasoningScore

Conciseness

The body is directive with no explanations of concepts Claude already knows, but a few spots could be trimmed — the pixel-level loading-state spec in Step 2 (spinner ring colors, 160x72 placeholder cards) duplicates state detail that dashboard-design.md's States section could carry, and Steps 5 and 6 are near-empty pointers. It is above anchor 3 ("some unnecessary explanation") because nearly everything is instruction rather than padding, but below anchor 5's "every token earns its place."

4 / 5

Actionability

Guidance is fully concrete and executable for an instruction-only skill: exact MCP tool names (`list_available_accounts_or_orgs`, `get_stripe_account_info`), a decision table mapping client type to output and reference file, precise `acct_`/`org_` matching rules, an exact loading-state spec, and a single-command read instruction with explicit anti-patterns ("Don't search the docs, fetch Stripe pages, or call `describe_capabilities`"). This matches anchor 5's copy-paste-ready specificity covering the common cases; nothing remains vague or abstract.

5 / 5

Workflow Clarity

The six steps are clearly sequenced with explicit failure checkpoints — "If the Stripe tools are missing, blocked, or need sign-in, say so in one line with the fix... and stop" and "If no account is listed, say that the connection needs a Stripe account... and stop" — but the body lacks a feedback loop for query execution failures (retry or error-state handling appears only implicitly via the references' States section). That places it at anchor 4 ("clear sequence with most checkpoints present; minor validation gaps") rather than 5, which requires explicit validation and error-recovery loops; the destructive/batch cap does not apply since the skill is read-only.

4 / 5

Progressive Disclosure

The body is a genuine overview that splits detail one level deep into four real, well-signaled reference files (references/dashboard-design.md, queries.md, hosted-page.md, local-dashboard.md), each read at a defined step with its purpose stated ("read <references/dashboard-design.md> for the layout, labels, and states"), and every section the body cites ("Write and open the page," "Build the dashboard," "Hand over") exists in the target files. A fallback URL for missing bundle files rounds out easy navigation, matching anchor 5's clear overview with well-signaled one-level-deep references.

5 / 5

Total

18

/

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.

A strong description in third-person voice that states a concrete capability, scopes it to the 2026 season, and gives an explicit 'Use when' clause with thorough natural-language triggers and example phrasings. The only minor gap is that it describes one build action with rich specifics rather than multiple distinct actions.

DimensionReasoningScore

Specificity

The description names concrete deliverables — "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" — but the capability is a single build action rather than a list of several concrete actions, leaving minor coverage gaps. It sits above anchor 3 (only 1-2 actions, not comprehensive) because the data domains, source, and both output forms are all explicit, but below anchor 5, which expects multiple distinct concrete actions.

4 / 5

Completeness

It explicitly answers both questions: what ("Builds a Black Friday and Cyber Monday (BFCM) season dashboard of payments, customers, and recurring revenue...") 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. This is a direct match to the anchor-5 example, which pairs a clear what with an explicit 'Use when...' clause and example triggers; it also scopes applicability ("For the 2026 BFCM season only").

5 / 5

Trigger Term Quality

Trigger coverage is comprehensive with natural synonyms — "BFCM, Black Friday, Cyber Monday, holiday, holiday sales, or peak-season dashboard" — plus concrete example utterances like "build me a holiday dashboard" and "build me a Cyber Monday dashboard," even handling the no-keyword case ("even without the word BFCM"). This matches the anchor-5 example's breadth of natural terms and synonyms; anchor 4 ("a few natural terms missing") doesn't apply since no common variation is omitted.

5 / 5

Distinctiveness Conflict Risk

It occupies a clear niche — a Stripe BFCM/seasonal revenue dashboard for merchants — with distinct, domain-anchored triggers (BFCM, Black Friday, Cyber Monday, peak-season), so it is unlikely to fire for unrelated dashboard or data skills. It matches anchor 5's "clear niche with distinct triggers; minimal conflict risk"; the only theoretical overlap is with a generic Stripe-analytics skill, which the season and merchant framing separates.

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/claude/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.