CtrlK
BlogDocsLog inGet started
Tessl Logo

setmore

Setmore integration. Manage data, records, and automate workflows. Use when the user wants to interact with Setmore 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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/setmore/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 content is actionable and well-structured, with executable Membrane CLI commands and a clear connection-state workflow including feedback loops. Its main weaknesses are mild verbosity (padded intro and a redundant section) and the absence of a complete worked example.

Suggestions

Trim the introductory paragraph explaining Setmore's business use to one line, since Claude already understands scheduling platforms.

Remove or merge the 'Popular actions' section, which duplicates the action-list command already shown under 'Searching for actions'.

Add one fully-worked example: a real `membrane action run` invocation with sample input JSON and the expected `output` field.

DimensionReasoningScore

Conciseness

The body is mostly lean commands, but the introductory paragraph explaining what Setmore is and the redundant 'Popular actions' section (which repeats the action-list command from 'Searching for actions') add unnecessary tokens.

3 / 5

Actionability

It provides concrete, copy-paste-ready commands for install, auth, connect, search, run, and proxy with a flag table, but lacks a fully-worked action invocation showing real parameters and parsed output.

4 / 5

Workflow Clarity

The install→auth→connect sequence is clear with state-based branching (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and a polling feedback loop, but 'skip to Step 2' references a Step 2 that is never labeled.

4 / 5

Progressive Disclosure

A single well-sectioned file with no nested references and no bundle files to misplace; minor gaps are the bare 'Setmore Overview' entity list and the thin, duplicative 'Popular actions' section.

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 correctly includes an explicit 'Use when...' trigger and names the target platform, giving it solid completeness and distinctiveness. It is held back by generic action language and a thin set of natural trigger terms that omit appointment/booking/scheduling vocabulary.

Suggestions

Replace generic verbs with concrete Setmore actions, e.g. "Create and manage appointments, services, staff, and bookings."

Expand the when-clause with natural triggers: "Use when the user wants to manage Setmore appointments, bookings, services, or staff."

Add domain synonyms (appointments, bookings, scheduling) so the description matches how users actually phrase requests.

DimensionReasoningScore

Specificity

"Manage data, records, and automate workflows" names the Setmore domain with a few action phrases, but the actions are generic and abstract rather than concrete (e.g. no "create appointments" or "list bookings").

3 / 5

Completeness

It explicitly states both what ("Setmore integration. Manage data, records, and automate workflows.") and when ("Use when the user wants to interact with Setmore data."), but the when-clause is generic rather than listing concrete triggers.

4 / 5

Trigger Term Quality

The only natural keyword is "Setmore" / "Setmore data"; common variations a user would actually say (appointments, bookings, scheduling) are missing, matching the anchor for some relevant keywords without synonyms.

3 / 5

Distinctiveness Conflict Risk

Setmore is a named platform giving a clear niche with minimal conflict risk, but the generic trigger "interact with Setmore data" keeps it just short of the fully-distinct anchor.

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.