CtrlK
BlogDocsLog inGet started
Tessl Logo

swoogo

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

56

Quality

65%

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

Quality

Content

67%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 a strong, executable guide to the Membrane CLI workflow with good connection-state checkpoints, but it stays generic to Membrane rather than showing Swoogo-specific actions, carries some marketing padding, and has a dangling "Step 2" reference. No bundle files exist, so structure alone supports a good-but-not-excellent progressive disclosure score.

Suggestions

Trim the marketing intro and filler lines ("Use action names and parameters as needed", "so you can focus on the integration logic") to assume Claude's competence.

Flesh out "Popular actions" with concrete Swoogo examples (e.g. creating an event, listing registrations) and fix the dangling "skip to Step 2" by labeling the next section.

Add a validation/dry-run note before running mutating or batch actions to satisfy the destructive/batch workflow checkpoint.

DimensionReasoningScore

Conciseness

The body is mostly efficient with concrete commands, but the marketing-flavored intro ("helps businesses plan and execute... streamline their event processes"), "Use action names and parameters as needed", and "so you can focus on the integration logic rather than auth plumbing" are padding Claude does not need.

3 / 5

Actionability

It provides copy-paste-ready membrane commands with flags and a proxy option table, but the "Popular actions" section is hollow (repeats the discovery command without listing any) and no Swoogo-specific action example is shown.

4 / 5

Workflow Clarity

The connection-readiness flow has explicit state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and polling, but the "skip to Step 2" reference dangles with no labeled Step 2, and there are no validation steps for potentially destructive/batch action runs.

4 / 5

Progressive Disclosure

Content is well organized into clear sections (Overview, Authentication, Connecting, Searching, Proxy, Best practices) with no nested references, but at ~143 lines with everything inlined (flag tables, state handling) it is not the lean single-purpose skill that would score 5.

4 / 5

Total

15

/

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 answers both what and when and is anchored to a distinct platform, but its capability list is generic ("manage data, records, automate workflows") rather than naming concrete Swoogo-specific actions. Trigger terms rely almost entirely on the platform name with little variation.

Suggestions

Replace generic actions with concrete Swoogo capabilities, e.g. "Create events, manage registrations, and sync attendees".

Expand the "Use when" clause with concrete trigger phrases such as "when the user mentions Swoogo events, registrations, or attendee data".

Add natural synonyms/variations (e.g. "event management", "registration forms") beyond just the platform name.

DimensionReasoningScore

Specificity

"Manage data, records, and automate workflows" names the Swoogo domain and a few actions, but the actions are generic rather than concrete Swoogo operations like registering attendees or creating events.

3 / 5

Completeness

Both "what" ("Manage data, records, and automate workflows") and "when" ("Use when the user wants to interact with Swoogo data") are present, but the what is generic and the when lists no concrete trigger scenarios, so it does not reach a 5.

4 / 5

Trigger Term Quality

The keyword "Swoogo" appears throughout ("Swoogo integration", "interact with Swoogo data"), but there are no synonyms or varied natural trigger phrases beyond the platform name.

3 / 5

Distinctiveness Conflict Risk

Naming the specific platform Swoogo gives it a clear niche with minimal conflict risk, though the generic action phrasing leaves minor overlap risk with other Swoogo-related skills.

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.