CtrlK
BlogDocsLog inGet started
Tessl Logo

gift-up

Gift Up! integration. Manage Products, Customers, Orders, Discounts. Use when the user wants to interact with Gift Up! 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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/gift-up/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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.

A solid, actionable integration guide with executable CLI examples and a well-sequenced connection workflow. Its main weaknesses are an over-long inline concept list/actions table that bloats the file and the absence of any reference files to offload detail.

Suggestions

Move the 40-item Gift Up! Overview concept list and the Popular actions table into a references/ file (e.g. ACTIONS.md), linking from the body with a one-line pointer.

Trim prose that re-explains what Membrane/auth is; keep only the command and the state-handling guidance.

Add an explicit validate/verify checkpoint after running actions (e.g. check the `output` field and `state`) to strengthen the workflow feedback loop.

DimensionReasoningScore

Conciseness

The body is mostly efficient with copy-paste commands, but the 40-item bullet "Overview" of Gift Up! concepts and prose restating what Membrane does are unnecessary padding Claude doesn't need.

3 / 5

Actionability

Concrete executable commands (install, login, connection ensure, action list/run, request proxy) with flags and JSON examples cover the common cases; minor gaps like no concrete CONNECTION_ID substitution example.

4 / 5

Workflow Clarity

The connection flow is sequenced with state checks (READY/BUILDING/CLIENT_ACTION_REQUIRED) and polling guidance, a clear feedback loop; only minor validation gaps in the action-run path keep it from a 5.

4 / 5

Progressive Disclosure

Sections are organized and there are no broken nested references, but no bundle files exist and the large inlined actions table and concept list that could live in a reference file are kept inline without one-level-deep pointers.

3 / 5

Total

14

/

20

Passed

Description

80%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.

A concise, well-formed description that answers both what and when with a specific trigger clause. Trigger-term coverage is the weakest area, lacking common synonyms like gift cards or vouchers.

Suggestions

Add natural synonyms users say, e.g. "Use when the user wants to manage gift cards, vouchers, or Gift Up! data".

Consider mentioning gift cards/vouchers in the action list since they are central to Gift Up!, not just Products/Customers/Orders/Discounts.

DimensionReasoningScore

Specificity

"Manage Products, Customers, Orders, Discounts" names the domain plus four concrete actions; minor gaps in coverage (gift cards, checkout, webhooks absent from the description) keep it just below comprehensive.

4 / 5

Completeness

It explicitly states what it does ("Manage Products, Customers, Orders, Discounts") and when to use it ("Use when the user wants to interact with Gift Up! data"), answering both clearly.

5 / 5

Trigger Term Quality

"interact with Gift Up! data" gives one relevant phrase, but common variations like "gift cards", "vouchers", or natural phrasings users say are missing.

3 / 5

Distinctiveness Conflict Risk

Gift Up! is a specific named platform with distinct triggers, so it is clearly distinguishable from other skills with minimal conflict risk.

5 / 5

Total

17

/

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.