Name: slicktext
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

slicktext

SlickText integration. Manage Accounts. Use when the user wants to interact with SlickText data.

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/slicktext/SKILL.md

Quality

Content

76%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 CLI commands and a clear connection workflow that includes state polling. Its main gap is the absence of validation/verification guidance for executing (potentially batch/destructive) SlickText actions.

Suggestions

Add a verification/confirmation step before running write or batch actions (e.g. 'Inspect the action outputSchema first; for sends or bulk updates, confirm the target with the user before running').

Show how to check an action's outputSchema and interpret the `output` field so Claude can verify a run succeeded rather than fire-and-forget.

Dimension	Reasoning	Score
Conciseness	The body is mostly executable commands and a flags table with little padding; only minor phrases ('so you can focus on the integration logic rather than auth plumbing') could be trimmed, keeping it just below the lean anchor.	4 / 5
Actionability	It provides copy-paste-ready commands for every common case (login, connection ensure/get with --wait, action list/run with --input, request proxy with a full flag table), fully executable with concrete examples.	5 / 5
Workflow Clarity	The connection flow has a real feedback loop (poll BUILDING to READY, handle CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR), but running actions on an SMS platform is a batch/destructive operation with no validation or verification step, capping this dimension.	3 / 5
Progressive Disclosure	No bundle files exist and the skill is a single well-sectioned file with clear headers and one-level structure; at ~140 lines it is slightly long to score 5, but organization is good and nothing is buried.	4 / 5
	Total	16 / 20 Passed

Description

57%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 has an explicit Use-when clause and names a distinct app, but its capability statement is thin ('Manage Accounts') and it lacks natural SMS/text-marketing trigger synonyms. It is adequate but under-specified.

Suggestions

Replace 'Manage Accounts' with concrete actions the skill supports, e.g. 'Manage SlickText contacts, lists, campaigns, keywords, and messages.'

Add natural trigger terms users would actually say, e.g. 'Use when the user wants to send SMS campaigns, manage text-marketing contacts or lists, or work with SlickText data.'

Dimension	Reasoning	Score
Specificity	It names the domain ('SlickText integration') but the only named action is the generic 'Manage Accounts', which is minimal rather than a list of concrete capabilities; it does not reach the 1-2 specific actions anchor cleanly.	2 / 5
Completeness	Both 'what' ('SlickText integration. Manage Accounts.') and an explicit 'when' ('Use when the user wants to interact with SlickText data.') are present; the when is clear though the what could be more specific, fitting the both-present anchor.	4 / 5
Trigger Term Quality	It surfaces 'SlickText' and the phrase 'interact with SlickText data', but omits natural synonyms a user would say (SMS, text messages, contacts, lists, campaigns), so common variations are missing.	3 / 5
Distinctiveness Conflict Risk	Naming a specific third-party app (SlickText) gives it a clear niche with low conflict risk, but the generic trigger phrasing leaves minor overlap room with other messaging/integration skills.	4 / 5
	Total	13 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/slicktext/SKILL.md
Commit: f484c82

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.