CtrlK
BlogDocsLog inGet started
Tessl Logo

sms-alert

SMS Alert integration. Manage Alerts, Contacts, Templates. Use when the user wants to interact with SMS Alert data.

62

Quality

74%

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

Quality

Content

75%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 highly actionable with executable CLI commands and a connection workflow that includes polling and state-based validation. The main weaknesses are some padding in the intro paragraph and an ambiguous "Step 2" cross-reference within the workflow.

DimensionReasoningScore

Conciseness

The body is mostly efficient with copy-paste commands, but the introductory paragraph ("SMS Alert is a service that allows businesses to send SMS messages...") and editorializing like "so you can focus on the integration logic rather than auth plumbing" add explanation that could be trimmed, placing it at mostly-efficient-with-some-unnecessary-explanation.

3 / 5

Actionability

It provides fully executable, copy-paste-ready bash commands throughout (install, login, connection ensure, action list/run, request) plus a concrete flags table, covering the common interaction cases.

5 / 5

Workflow Clarity

The connection workflow has a clear sequence with explicit validation checkpoints and feedback loops (poll until state is no longer BUILDING, poll again after a CLIENT_ACTION_REQUIRED action), but references to "Step 2" are not cleanly mapped to labeled sections, leaving a minor navigation gap.

4 / 5

Progressive Disclosure

The content is organized into clear section headers (Overview, Working with SMS Alert, Popular actions, Best practices) in a single file with no nested references and no bundle files to split out, giving good structure with only minor organization gaps rather than the ideal one-level-deep reference split.

4 / 5

Total

16

/

20

Passed

Description

73%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 covers what and when for a distinct, named service, with explicit trigger guidance and good keyword coverage. Its main weakness is the generic verb "Manage" rather than enumerating specific concrete actions.

DimensionReasoningScore

Specificity

The phrase "Manage Alerts, Contacts, Templates" names the domain and three concrete resource entities, but the verb "Manage" is generic rather than listing specific concrete actions (e.g. create, list, send), so it sits at the anchor for domain-plus-minimal-actions rather than the multi-action anchor above.

3 / 5

Completeness

It states both the what ("SMS Alert integration. Manage Alerts, Contacts, Templates") and an explicit when ("Use when the user wants to interact with SMS Alert data"), but the when-clause is somewhat generic rather than concrete trigger phrases, fitting the anchor where 'when' could be more specific.

4 / 5

Trigger Term Quality

It includes the natural service name "SMS Alert" plus the entity terms "Alerts, Contacts, Templates" that users would say, giving good keyword coverage; it misses synonyms or file-extension-style variations, so it does not reach the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

It targets a specific named service ("SMS Alert") with service-scoped triggers, giving it a clear niche with minimal overlap risk against other skills.

5 / 5

Total

16

/

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.