CtrlK
BlogDocsLog inGet started
Tessl Logo

swagup

SwagUp integration. Manage Persons, Organizations, Deals, Leads, Projects, Activities and more. Use when the user wants to interact with SwagUp data.

60

Quality

70%

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/swagup/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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 delivers concrete, executable Membrane commands across a sensible connection-to-action workflow, but some prose padding, a dangling Step 2 reference, and the absence of verification for potentially destructive proxy calls hold it back from top marks.

Suggestions

Tighten the prose: drop the swag marketing blurb and the "so you can focus on the integration logic" aside, and consider moving the entity overview tree into a reference file.

Fix the broken "skip to Step 2" reference by either labeling the section sequence (Step 1 / Step 2) or rewriting it to point to the actual "Searching for actions" section.

Add a verification/checkpoint step for destructive proxy calls (e.g., confirm method and target before running DELETE, and check the response status), since the proxy flag table exposes -X DELETE with no guardrail.

DimensionReasoningScore

Conciseness

The body is mostly efficient and command-driven, but the marketing blurb ("Companies use it to manage swag for marketing, events, and employee gifting"), the "so you can focus on the integration logic rather than auth plumbing" fluff, and the inlined entity overview tree are unnecessary padding that could be tightened.

3 / 5

Actionability

Concrete copy-paste commands cover the common cases (login, connection ensure, --wait polling, action list/run with --input, proxy), but the proxy section only demonstrates a GET path while flag table options like -d/--data for POST lack a full example, leaving minor gaps.

4 / 5

Workflow Clarity

The connection flow has explicit state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a re-poll feedback loop, but the "skip to Step 2" reference points to no labeled Step 2, and the action-running/proxy workflow — which supports destructive methods like DELETE — has no verification step, capping this at 3.

3 / 5

Progressive Disclosure

The single SKILL.md is well organized into clearly headed sections (Install, Authentication, Connecting, Searching, Running actions, Proxy, Best practices) with the only external pointer being the official docs URL; no bundle files exist, and content is appropriately placed with only minor organization gaps.

4 / 5

Total

14

/

20

Passed

Description

78%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 cleanly states both what it does and when to use it with a distinct brand trigger, but its single generic verb and "and more" keep specificity and trigger breadth just short of top marks.

DimensionReasoningScore

Specificity

"Manage Persons, Organizations, Deals, Leads, Projects, Activities and more" lists several specific entities, but relies on a single generic verb and the vague "and more" hedge rather than distinct concrete actions, leaving minor coverage gaps short of a 5.

4 / 5

Completeness

Both halves are present — "Manage Persons, Organizations, Deals, Leads, Projects, Activities and more" answers what and "Use when the user wants to interact with SwagUp data" answers when — but the when clause is a single generic trigger rather than the multiple concrete trigger phrases that anchor a 5.

4 / 5

Trigger Term Quality

The brand "SwagUp" plus named domain nouns (Persons, Organizations, Deals, Leads, Projects, Activities) and "interact with SwagUp data" give good keyword coverage a user would naturally say, though a few natural variations are missing.

4 / 5

Distinctiveness Conflict Risk

The explicit "SwagUp" branding anchors a clear niche with brand-specific triggers, keeping conflict risk with other skills minimal.

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.