CtrlK
BlogDocsLog inGet started
Tessl Logo

pushpay

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

60

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/pushpay/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 executable commands and a well-validated connection workflow, organized into clear sections with no nested references. Minor trimming and an explicitly labeled 'Step 2' would push it to the top level.

DimensionReasoningScore

Conciseness

The body is largely efficient with concrete commands, but the introductory Pushpay paragraph and phrases like 'so you can focus on the integration logic rather than auth plumbing' and 'Use action names and parameters as needed' could be trimmed.

4 / 5

Actionability

Provides fully executable, copy-paste-ready commands throughout (login, connection ensure, action list/run, request with a complete flag table) covering the common cases.

5 / 5

Workflow Clarity

The connection flow has a clear sequence with state-validation checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a poll-after-action feedback loop, but 'skip to Step 2' references a step that is not explicitly labeled.

4 / 5

Progressive Disclosure

Sections are well-organized with clear headers and no nested references, and no bundle files exist; the ~30-entity dump under 'Pushpay Overview' is compact enough to stay inline but is the main candidate for a separate reference file.

4 / 5

Total

17

/

20

Passed

Description

61%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 answers both what and when and is highly distinct thanks to the named product, but its capability language is generic and its trigger terms are narrow, missing natural synonyms like 'donations' and 'giving'.

Suggestions

Replace generic verbs with concrete Pushpay capabilities, e.g. 'Manage donations, pledges, funds, members, and transactions. Automate giving workflows.'

Broaden the trigger clause to cover natural user phrasings: 'Use when the user wants to manage Pushpay donations, giving, pledges, members, or church engagement data.'

Keep the explicit 'Use when...' clause but pair it with the specific entity names users mention.

DimensionReasoningScore

Specificity

Names the domain ('Pushpay integration') but the actions 'Manage data, records, and automate workflows' are generic verbs rather than concrete capabilities, matching the 'names the domain but actions are minimal or generic' anchor.

2 / 5

Completeness

Both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Pushpay data') are present, but the trigger clause is a single narrow phrase rather than multiple concrete triggers.

4 / 5

Trigger Term Quality

Includes the natural proper-noun trigger 'Pushpay' and 'Pushpay data', but omits common synonyms a user would actually say such as 'donations', 'giving', 'pledges', or 'church giving'.

3 / 5

Distinctiveness Conflict Risk

'Pushpay' is a specific named product, giving the skill a clear niche with a distinct trigger and minimal conflict risk with other skills.

5 / 5

Total

14

/

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.