AF gumroad-pro
Comprehensive Gumroad merchant management for Products, Sales, Licenses, Discounts, Payouts, and Webhooks. Use when Claude needs to: (1) Manage digital or physical inventory, (2) Oversee transactions and process refunds/shipping, (3) Verify or rotate license keys, (4) Manage offer codes, or (5) Monitor payout history and store webhooks.
Comprehensive Gumroad merchant management for Products, Sales, Licenses, Discounts, Payouts, and Webhooks.
As a process F 38/100 · Will not run — References files that are not bundled: {baseDir}/references/handler-guide.md, {baseDir}/references/ui-rendering.md, {baseDir}/references/changelog.md
How to improve
- The text references files that are not there: add them or drop the references.
- 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: 8. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: {baseDir}/references/handler-guide.md - warning
missing-refreference to a missing file: {baseDir}/references/ui-rendering.md - warning
missing-refreference to a missing file: {baseDir}/references/changelog.md - warning
missing-refreference to a missing file: {baseDir}/references/api-reference.md - warning
missing-refreference to a missing file: {baseDir}/references/api-reference.md - warning
missing-refreference to a missing file: {baseDir}/references/api-reference.md - warning
missing-refreference to a missing file: {baseDir}/references/api-reference.md - warning
missing-refreference to a missing file: {baseDir}/references/api-reference.md
Process rating: all ten parameters 38/100
- 0Tools and files. 8 referenced file(s) missing: {baseDir}/references/handler-guide.md, {baseDir}/references/ui-rendering.md, {baseDir}/references/changelog.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 5 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 100Steps. 20 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 706 tokens
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
- +1No license
- +2Single-language instructions
- +3Description length 338: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 20 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (4 of 4)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.