CtrlK
BlogDocsLog inGet started
Tessl Logo

slybroadcast

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

61

Quality

72%

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/slybroadcast/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 concrete executable commands and a clear connection workflow that includes validation and a recovery feedback loop. It is concise and well-structured, with only minor trimming opportunities and a slightly inconsistent step labeling.

DimensionReasoningScore

Conciseness

The body is mostly operational and lean, with copy-paste commands throughout; the only mild padding is the opening 'Slybroadcast is a voice broadcasting service...' line and the throwaway 'Use action names and parameters as needed.' that could be trimmed.

4 / 5

Actionability

It provides fully executable, copy-paste-ready commands for every common case (install, login, connection ensure, --wait polling, action list/run, request with a concrete flag table), covering the integration workflow end to end.

5 / 5

Workflow Clarity

The install → authenticate → ensure connection → poll for READY → search → run sequence is clear with state-based validation and a poll-after-user-action feedback loop, but the 'skip to Step 2' reference points to an unlabeled section and there is no explicit checklist.

4 / 5

Progressive Disclosure

No bundle files exist and the body is a single self-contained file with clear, logical section headers; it is well-organized but at ~140 lines offers no one-level-deep reference split for the detailed clientAction state handling.

4 / 5

Total

17

/

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 clearly identifies the Slybroadcast niche and includes an explicit 'Use when' trigger, but it relies on the single generic verb 'Manage' and omits natural trigger synonyms like 'voice broadcasting' or 'campaigns'. It is solid but leaves room for more specific actions and richer trigger phrasing.

Suggestions

Replace the generic 'Manage' with concrete verbs (e.g. 'Send voice broadcast campaigns, upload audio, schedule calls, and manage contacts') to lift specificity.

Add natural trigger phrases users would say, such as 'voice broadcasting', 'voice messages', 'campaigns', or 'phone number lists', to improve trigger term coverage.

Tighten the 'when' clause to concrete scenarios, e.g. 'Use when the user wants to send voice broadcasts or manage Slybroadcast campaigns and contacts.'

DimensionReasoningScore

Specificity

The description names the domain ('Slybroadcast integration') and lists several concrete entity types ('Persons, Organizations, Leads, Deals, Projects, Activities') but relies on a single generic verb ('Manage'), so actions are minimal rather than comprehensive.

3 / 5

Completeness

It provides both a 'what' ('Manage Persons, Organizations, Leads, Deals, Projects, Activities') and an explicit 'when' ('Use when the user wants to interact with Slybroadcast data'), though the trigger clause is somewhat generic and could be more specific.

4 / 5

Trigger Term Quality

It includes the natural product name 'Slybroadcast' and 'interact with Slybroadcast data', but misses common variations and synonyms a user would actually say such as 'voice broadcasting', 'voice messages', 'campaigns', or 'phone numbers'.

3 / 5

Distinctiveness Conflict Risk

The 'Slybroadcast' product name gives it a clear, distinct niche with minimal conflict risk, but the generic CRM-style entity list ('Persons, Organizations, Leads, Deals') creates minor overlap risk with related CRM/sales 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.