BF paytm-integration
Expert guide for integrating Paytm Payment Gateway APIs and SDKs into websites, mobile apps, and backend systems. Use this skill whenever the user is working with Paytm payments - including setting up the payment gateway, generating checksums, calling Initiate Transaction / Transaction Status APIs, integrating the JS Checkout, handling callbacks, generating payment links, generating dynamic QR codes, implementing UPI Autopay subscriptions, or troubleshooting Paytm PG errors. Trigger when the question contains Paytm-specific tokens: "Paytm", "paytmchecksum", "txnToken", "CHECKSUMHASH", "paytmpayments.com", "/theia/api/", "subscription/create", "/link/create", "paymentservices/qr", "WEBSTAGING", "NATIVE_SUBSCRIPTION", or any path under `paytmpayments.com/docs`. Do NOT trigger on generic PSP terms ("MID", "merchant key", "checksum", "PG integration") in isolation - those overlap with other payment gateways and would mis-trigger the skill. Also trigger when the user explicitly mentions they are a Paytm merchant or developer.
As a process F 52/100 · Will not run — References files that are not bundled: scripts/backend-{node,python,spring}
How to improve
- Shorten the description to 1024 characters.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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: 67. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- error
description-longdescription is 1037 chars, limit 1024 - warning
body-longSKILL.md body ≈ 8283 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: scripts/backend-{node,python,spring}
Process rating: all ten parameters 52/100
- 0Tools and files. 1 referenced file(s) missing: scripts/backend-{node,python,spring}
- 0Result and completion. Does not say what the result is
- 30Inputs and preconditions. Does not say what the process needs to start
- 40Consistency. Frontmatter name (paytm-integration) differs from the folder (paytm-integration-skill)
- 40Execution cost. Instruction body is 8283 tokens: crowds the task out of the window
- 100Steps. 70 steps
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 4 branches, has a failure section
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 17 top-level sections: this looks like several domains in one skill
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
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 1036: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -2localhost URLs: will not work for another user
- +1No license
- +2Single-language instructions
- +5Description quotes 13 example trigger phrases
- +4Structure: 32 headings
- +3Step-by-step instructions: 70 items
- +4Has examples (17 code blocks)
- +4Reference files are cited in the instructions (5 of 5)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 47.