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

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

Exemplary skill body: a tight overview with fixed rules, a clearly sequenced workflow with explicit stop/error conditions, and clean one-level-deep progressive disclosure into four real reference files. It assumes Claude's competence, never over-explains, and every instruction is directly executable.

DimensionReasoningScore

Conciseness

The body is lean and imperative throughout — rules, a six-step workflow, and a decision table with no explanation of concepts Claude already knows. Even the prescriptive loading-state spec (exact colors, pixel sizes, timing) is reproducibility specification rather than padding, and nothing can be trimmed without losing actionability.

5 / 5

Actionability

Concrete, executable guidance throughout: exact MCP tool names ('list_available_accounts_or_orgs', 'get_stripe_account_info'), a client-to-output decision table, precise fallback behaviors ('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'), and account-selection rules keyed on 'acct_' prefixes. Per the rubric's scoring note, the absence of code in this instruction-only skill is not penalized because the guidance is fully actionable.

5 / 5

Workflow Clarity

Six clearly sequenced steps (choose output, show progress, choose account, read references, build, hand over) with explicit validation and stop conditions for each failure mode: missing/blocked tools, no account listed, and an API-key session with a defined alternate path. The skill is read-only, so the destructive/batch validation cap does not apply.

5 / 5

Progressive Disclosure

The body is a genuine overview: layout, queries, and per-output build instructions live in four one-level-deep reference files (all verified present in references/), each assigned via the decision table and step 4, with a fallback URL for hosted fetching. No content that belongs in references is inlined beyond what step 2 requires before references are read.

5 / 5

Total

20

/

20

Passed

Description

91%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: third-person, concrete about what is built and from what source, with an explicit 'Use when' clause containing comprehensive natural trigger terms and example phrases. The only weaknesses are minor — a single build action rather than multiple capabilities, and a broad 'holiday dashboard' trigger that slightly raises overlap risk with generic dashboard skills.

DimensionReasoningScore

Specificity

The description states concrete specifics — '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... or a local page' — naming the domain, metric surfaces, data source, and both output forms. It stays at 4 rather than 5 because it describes essentially one build action with rich detail, not multiple distinct concrete actions.

4 / 5

Completeness

It explicitly answers both 'what' (builds a payments/customers/recurring-revenue dashboard from the Stripe MCP account, hosted or local) and 'when' (a 'Use when...' clause with concrete trigger phrases), plus a scope bound ('For the 2026 BFCM season only'). This matches the anchor-5 example structure exactly.

5 / 5

Trigger Term Quality

'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' covers comprehensive natural synonyms and example utterances users would actually say, matching the top anchor.

5 / 5

Distinctiveness Conflict Risk

The Stripe merchant/BFCM niche is clear and distinct, but triggers like 'build me a holiday dashboard' even without BFCM or Stripe mentioned cast a wide net with minor overlap risk against generic dashboard or data-visualization skills, fitting 'mostly distinct; minor overlap risk' better than the minimal-conflict top anchor.

4 / 5

Total

18

/

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