CtrlK
BlogDocsLog inGet started
Tessl Logo

pinme-uniwebpay

Use when generating, modifying, or reviewing PinMe Worker (Cloudflare Worker TypeScript) code that accepts payments through UniwebPay — payment links, products/prices, checkout sessions, payment status reads, refunds, subscriptions, or handling UniwebPay webhooks with @uniwebpay/sdk in a PinMe project.

72

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

77%Weight 40%Scale 1-3

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 clear, validated workflows, but it is monolithic: a large inline SDK reference and a full reference implementation, with some rule repetition across sections, that would benefit from being split into separate bundle files.

Suggestions

Move the 'SDK Surface Quick Reference' and/or the full 'Worker Reference Implementation' into separate files under references/ and link to them from a concise overview, enabling progressive disclosure.

Reduce duplication between the inline security/webhook rules and the 'Common Mistakes' table by having one section state the rule and the table link back to it.

Trim or consolidate the repeated webhook-routing guidance that appears in prose, the reference implementation comments, and the checklist.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's knowledge of TypeScript/Workers without padding, but the same rules recur across the SDK surface, the full reference implementation, and the 'Common Mistakes' table, which could be tightened.

2 / 3

Actionability

Provides fully executable TypeScript — a complete reference implementation with real route handlers, input validation, SDK calls, D1 queries, and webhook verification — that is copy-paste ready.

3 / 3

Workflow Clarity

The webhook flow is explicitly sequenced with validation checkpoints (signature verification, 400/500 semantics, event.id idempotency, amount/currency/state checks before fulfillment) plus a Finish Checklist and Common Mistakes feedback loops.

3 / 3

Progressive Disclosure

No references/scripts/assets bundle exists, so all content is inline in one ~570-line file; the large SDK surface reference and full reference implementation are content that, ideally, would live in separate one-level-deep reference files.

2 / 3

Total

10

/

12

Passed

Description

100%Weight 40%Scale 1-3

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, trigger-rich, and clearly distinguishes this niche skill, with an explicit 'Use when...' clause covering both what and when. It uses the imperative trigger voice rather than first/second person, so no voice penalty applies.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'generating, modifying, or reviewing' PinMe Worker code for 'payment links, products/prices, checkout sessions, payment status reads, refunds, subscriptions, or handling UniwebPay webhooks' — matching the score-3 anchor.

3 / 3

Completeness

Explicitly answers both 'what' (PinMe Worker TypeScript code that accepts payments through UniwebPay) and 'when' via an explicit 'Use when...' trigger clause.

3 / 3

Trigger Term Quality

Includes natural user-facing terms — 'payment links', 'checkout sessions', 'refunds', 'subscriptions', 'webhooks', 'UniwebPay', 'PinMe Worker' — with good coverage users would actually say.

3 / 3

Distinctiveness Conflict Risk

Highly specific niche tied to 'PinMe Worker', 'UniwebPay', and '@uniwebpay/sdk' — distinct triggers unlikely to fire for the wrong skill.

3 / 3

Total

12

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (576 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository
glitternetwork/pinme
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.