CtrlK
BlogDocsLog inGet started
Tessl Logo

smarterpay

SmarterPay integration. Manage data, records, and automate workflows. Use when the user wants to interact with SmarterPay data.

62

Quality

74%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/smarterpay/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%Weight 40%Scale 1-5

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

The content is highly actionable with fully executable CLI commands and a clear connection-handling workflow including polling states. Conciseness and progressive disclosure are strong with only minor trim and labeling opportunities.

DimensionReasoningScore

Conciseness

The body is mostly lean executable commands with brief explanations, assuming Claude's competence, though minor filler like "This is the fastest way to get a connection" and "This will burn less tokens" could be trimmed.

4 / 5

Actionability

Every section gives copy-paste ready commands (install, login, connection ensure/get, action list/run, request proxy) with concrete flags and JSON examples covering the common cases.

5 / 5

Workflow Clarity

There is a clear install→auth→connect→search→run/proxy sequence with connection-state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a re-poll feedback loop, though the referenced "Step 2" is not cleanly labeled as its own section.

4 / 5

Progressive Disclosure

The single file is well-organized with clear section headers and no nested references, and since no bundle files are needed this is appropriately self-contained, though it sits at the upper end of good rather than exceptional structure.

4 / 5

Total

17

/

20

Passed

Description

66%Weight 40%Scale 1-5

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 clearly identifies its niche via the SmarterPay brand and includes an explicit "Use when" clause, giving it solid completeness and distinctiveness. Specificity and trigger-term coverage are weaker because the stated actions are generic and few synonyms are offered.

Suggestions

Replace generic verbs ("manage data", "automate workflows") with concrete SmarterPay operations such as creating charges, issuing refunds, or handling mandates.

Expand the trigger clause to name common user phrasings (e.g., payments, transactions, payouts) so it fires on natural requests.

Mention the supported entity types (Customer, Invoice, Subscription, Quote) to signal scope and improve specificity.

DimensionReasoningScore

Specificity

"Manage data, records, and automate workflows" names the SmarterPay domain with a few actions, but the actions ("manage data", "automate workflows") are generic rather than concrete SmarterPay-specific operations, matching the 1-2 concrete actions anchor.

3 / 5

Completeness

It answers both what ("Manage data, records, and automate workflows") and when ("Use when the user wants to interact with SmarterPay data"), though the trigger clause could be more specific about which SmarterPay scenarios apply.

4 / 5

Trigger Term Quality

The only natural trigger is the brand term "SmarterPay" in "interact with SmarterPay data"; relevant but missing common variations or synonyms users might say, matching the some-relevant-keywords-but-missing-variations anchor.

3 / 5

Distinctiveness Conflict Risk

"SmarterPay integration" is a specific named platform with a clear niche and distinct triggers, so it is unlikely to fire for an unrelated skill.

5 / 5

Total

15

/

20

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
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.