CtrlK
BlogDocsLog inGet started
Tessl Logo

freedompay

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

61

Quality

72%

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/freedompay/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 body is highly actionable with executable commands and a clear multi-step workflow, supported by solid section organization. Minor trimming of background prose and either labeling the missing "Step 2" or extracting detailed reference material into bundle files would push it to the top level.

DimensionReasoningScore

Conciseness

The body is largely efficient with lean CLI commands, but includes some mild over-explanation (the platform-background paragraph and phrases like "auth plumbing") that could be trimmed.

4 / 5

Actionability

It provides copy-paste ready `membrane` commands with concrete flags, a parameter example using `--input '{"key": "value"}'`, and a flag table, fully covering the common cases.

5 / 5

Workflow Clarity

There is a clear install → authenticate → connect → search → run sequence with a polling loop and conditional clientAction handling, but the unlabeled "Step 2" reference and absence of an explicit validation checkpoint are minor gaps.

4 / 5

Progressive Disclosure

The single SKILL.md is well organized into clear sections, but with no bundle files present the detailed clientAction state breakdown and proxy flag table are inlined where they could be split into references.

4 / 5

Total

17

/

20

Passed

Description

62%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 covers both what and when and is anchored to a distinct named platform, but it relies on generic action verbs and offers limited trigger-term variety. Tightening the verbs to concrete payment operations and adding task-level synonyms would lift the weaker dimensions.

Suggestions

Replace generic verbs with concrete payment operations the skill performs (e.g. query transactions, fetch payment records, pull reports) to raise specificity.

Expand trigger terms beyond the product name to include natural task phrases users say (e.g. "FreedomPay transactions", "payment reports", "payment records").

Make the "Use when" clause more specific by naming the concrete tasks that should trigger this skill rather than the broad "interact with FreedomPay data".

DimensionReasoningScore

Specificity

The description names the FreedomPay domain and lists several actions ("Manage data, records, and automate workflows"), but the verbs are generic rather than concrete payment operations, so coverage is not comprehensive.

3 / 5

Completeness

Both a "what" (integration, manage data/records, automate workflows) and an explicit "Use when..." trigger are present, though the "when" clause is somewhat thin and could be more specific.

4 / 5

Trigger Term Quality

"FreedomPay" and "FreedomPay data" are relevant keywords, but there are no synonyms, related task phrases (e.g. transactions, payments, reports), or file extensions beyond the product name.

3 / 5

Distinctiveness Conflict Risk

The FreedomPay product name provides a distinct niche with minimal conflict risk, even though the supporting action verbs ("manage data, records") are broad.

4 / 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.