SKILLEMALL.ai

BC how-to-set-up-stripe-payments-for-dotnet-9-core-projects

Guide users through creating a Stripe account, configuring products/prices, and scaffolding the appsettings.json for any .NET 9 project. Explain how to manually merge the FastBlazorSaaS boilerplate into an existing project.

ClawHub Agent Skills author: MacMerg v1.0.3 MIT-0 2 files body ≈ 1 009 tokens Open the sourceclawhub.ai analyzed 2 d ago

As a process C 54/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

GeneratorStripeInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
B
88/100
safety, quality, tests
Safety 60%
100
Quality 40%
70
Run on models
none yet
Process rating
C
54/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
When it triggers w 12
20
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: how-to-set-up-stripe-payments-for-dotnet-9-core-projects (ClawHub)

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 54/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 11 mutating operations with no state check
  • 40Consistency. Frontmatter name (how-to-set-up-stripe-payments-for-dotnet-9-core-projects) differs from the folder (stripe-blazor-setup)
  • 65Failures and branches. 3 branches
  • 100Tools and files. No external tools needed
  • 100Steps. 10 steps
  • 100Execution cost. Instruction body is 1009 tokens
  • 100Progress reporting. Reports progress

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • -2localhost URLs: will not work for another user
  • +1No license
  • +2Single-language instructions
  • +3Description length 223: enough signal without eating the budget
  • +4Structure: 5 headings
  • +3Step-by-step instructions: 10 items
  • +4Has examples (1 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.

External checks

ClawHub: clean
This is an instruction-only Stripe setup guide with a visible commercial boilerplate pitch, but it does not run code, read files, or secretly handle credentials.
LLM: benign (high) · VirusTotal: · 29 May 2026