CtrlK
BlogDocsLog inGet started
Tessl Logo

botstar

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

59

Quality

68%

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/botstar/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 content is highly actionable with executable commands and a well-sequenced connection workflow including validation via state polling; its main gaps are the dangling "Step 2" reference and an inlined actions table that could live in a reference file.

DimensionReasoningScore

Conciseness

The body is mostly executable commands with little padding; the few explanatory lines about Membrane handling auth are justified non-obvious behavior, leaving only minor over-explanation to trim.

4 / 5

Actionability

Copy-paste-ready commands are given for every phase (install, login, connection ensure, action list/run, request) plus a concrete flags table, covering the common cases fully.

5 / 5

Workflow Clarity

The connection flow has explicit state handling (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) with a re-poll feedback loop, but the "Step 2" reference points to no numbered section, leaving a minor navigation gap.

4 / 5

Progressive Disclosure

Sections are well organized with a clear overview flow, but the long Popular actions table is inlined in SKILL.md with no bundle files to offload the reference bulk.

4 / 5

Total

17

/

20

Passed

Description

55%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 distinct because of the Botstar brand, but its action verbs are generic and it lacks concrete entity/trigger keywords that users would naturally mention.

Suggestions

Replace generic verbs with concrete Botstar operations, e.g. "Manage bots, CMS entities, and entity items, and send messages via Botstar."

Add natural trigger keywords users would say, e.g. "Use when the user wants to manage Botstar chatbots, CMS entities, or send broadcast messages."

Mention the messaging/lead-generation use cases so the trigger matches real user intent.

DimensionReasoningScore

Specificity

Quotes "Manage data, records, and automate workflows" name the Botstar domain plus a few concrete actions, but the verbs are generic (manage, automate) rather than the specific CMS/bot operations shown later in the body.

3 / 5

Completeness

Both "what" ("Manage data, records, and automate workflows") and "when" ("Use when the user wants to interact with Botstar data") are present and explicit, though the trigger is generic.

4 / 5

Trigger Term Quality

Only "Botstar" and "Botstar data" appear as natural terms; no synonyms or concrete entities (bots, CMS entities, chatbots, messaging channels) a user would actually say.

2 / 5

Distinctiveness Conflict Risk

Tied to the unique platform name "Botstar", giving a clear niche with low conflict risk, but the generic surrounding verbs leave minor overlap with other data-management skills.

4 / 5

Total

13

/

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.