web-payments

Stripe Checkout, subscriptions, webhooks, customer portal

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

65%

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

The body is highly actionable with complete executable code and strong security guidance, but it is a monolithic single file with some redundant repetition and lacks an explicitly sequenced validation workflow for its state-changing webhook operations. Splitting detail into reference files and adding a checkpointed flow would improve it.

Suggestions

Move the full embedded-checkout, customer-portal, and pricing-page code examples into reference files (e.g. references/checkout-examples.md) linked one level deep from the overview.

Add an explicitly sequenced integration workflow with validation checkpoints, e.g. 1. Create session -> 2. Verify webhook signature -> 3. Check idempotency -> 4. Provision access -> 5. Confirm DB state, with a retry loop on failure.

Trim the redundant 'Quick Reference' install/env-var/key-endpoint blocks that duplicate earlier sections to recover token budget.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean, actionable code and tables rather than concept explanation, but the 'Quick Reference' section redundantly repeats the install commands, environment variables, and key endpoints already covered earlier, so it could be tightened.	2 / 3
Actionability	It provides complete, executable TypeScript and Python code, exact CLI commands ('stripe listen --forward-to ...'), dashboard URLs, test card numbers, and copy-paste-ready examples across every integration path.	3 / 3
Workflow Clarity	Verification (signature checks) and idempotency are present and the 'Non-Negotiable Rules' act as a checklist, but the end-to-end checkout->webhook->provision flow is not laid out as an explicitly sequenced workflow with validate->fix->retry checkpoints, which caps clarity at 2 for state-changing operations.	2 / 3
Progressive Disclosure	No bundle files exist and all content lives inline in a single ~650-line SKILL.md; sectioning is clear, but content that could be split (embedded checkout, portal, pricing-page examples) is inline with no one-level-deep external references, so it is structured but not progressively disclosed.	2 / 3
	Total	9 / 12 Passed

Description

57%

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 specific and clearly niched to Stripe, but it reads as a noun-phrase feature list with no action verbs and no inline 'Use when...' trigger clause, capping completeness and specificity. Adding a third-person verb phrase and an explicit trigger clause would raise it.

Suggestions

Rewrite as third-person action verbs, e.g. 'Integrates Stripe Checkout, subscriptions, webhooks, and the customer portal into web applications.'

Add an explicit trigger clause to the description: 'Use when implementing payments, subscriptions, billing, or Stripe integration.'

Include the common user terms 'payments' and 'billing' so the most natural trigger phrasings are covered.

Dimension	Reasoning	Score
Specificity	The description enumerates four concrete capabilities ('Stripe Checkout, subscriptions, webhooks, customer portal') but presents them as a noun list rather than third-person action verbs like the top anchor's 'Extract text... fill forms... merge documents', so it names the domain and actions without being comprehensive verb-style actions.	2 / 3
Completeness	It answers 'what' (the four capabilities) but the description field contains no explicit 'Use when...' trigger clause; per the judging guidelines a missing explicit trigger clause caps completeness at 2, even though a separate when-to-use field exists.	2 / 3
Trigger Term Quality	It includes strong natural terms users would say ('Stripe Checkout, subscriptions, webhooks, customer portal'), but the most common user phrasings 'payments' and 'billing' are absent from the description field, leaving some relevant keywords missing common variations.	2 / 3
Distinctiveness Conflict Risk	The Stripe-specific niche ('Stripe Checkout, subscriptions, webhooks, customer portal') is clearly distinguishable from other skills and unlikely to trigger for the wrong skill.	3 / 3
	Total	9 / 12 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (666 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: alinaqi/claude-bootstrap
Commit: 9dacc46

Reviewed: about 8 hours ago

Table of Contents

Discovery Implementation Validation

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.