CtrlK
BlogDocsLog inGet started
Tessl Logo

tyntec

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

63

Quality

75%

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

Quality

Content

88%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 a strong, action-oriented skill with executable commands, a validated connection workflow with feedback loops, and clean section structure. Its only notable weakness is a padded marketing intro and a thin overview section.

DimensionReasoningScore

Conciseness

The body is mostly lean command reference with copy-paste bash blocks, but the opening paragraph ("Tyntec is a cloud communications platform that helps businesses connect with their customers...") is marketing-style padding that could be trimmed. It is above 3 because most content is efficient, and below 5 because of that padded intro.

4 / 5

Actionability

It provides fully executable, copy-paste-ready commands throughout (install, login, connection ensure/get, action list/run, request) plus a flag table and JSON parameter examples covering the common cases. It matches the 5 anchor rather than 4 because the guidance is complete and specific.

5 / 5

Workflow Clarity

The connection workflow is a clear sequence with explicit validation via state checks (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), a poll-with-"--wait" feedback loop, and error-recovery guidance to re-poll after user action. It fits the 5 anchor with explicit validation and feedback loops.

5 / 5

Progressive Disclosure

No bundle files exist and the single SKILL.md is organized into clear sections (Overview, Working with Tyntec, Authentication, Connecting, Searching, Popular actions, Best practices) with no nested references. It stays at 4 rather than 5 because the "Tyntec Overview" bullet list is thin/placeholder-like and minor organization gaps remain.

4 / 5

Total

18

/

20

Passed

Description

61%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 with a distinct, low-conflict brand niche, but its capabilities are stated generically and its trigger terms lack the concrete Tyntec-specific vocabulary (SMS, WhatsApp, messaging) users would naturally say.

Suggestions

Replace generic verbs with concrete Tyntec actions, e.g. "Send SMS and WhatsApp messages, manage contacts and conversations, and automate messaging workflows."

Add natural trigger terms and synonyms such as "SMS", "WhatsApp", "messages", "conversations", and "templates" so the description matches what users actually say.

Sharpen the "Use when" clause with concrete triggers, e.g. "Use when the user wants to send SMS/WhatsApp messages or manage Tyntec contacts and conversations."

DimensionReasoningScore

Specificity

"Manage data, records, and automate workflows" names the Tyntec domain but the actions are generic rather than concrete Tyntec capabilities (no SMS, WhatsApp, messaging, or contacts). It does not reach 3 because it lacks 1-2 specific concrete actions, and stays above 1 because the domain is named.

2 / 5

Completeness

It states a what ("Manage data, records, and automate workflows") and an explicit when ("Use when the user wants to interact with Tyntec data"), but the when is broad rather than concrete. It is not 5 because the trigger phrases are not concrete, and not 3 because both what and when are explicitly present.

4 / 5

Trigger Term Quality

The brand keyword "Tyntec" ("Tyntec data", "Tyntec integration") is the primary natural trigger, but common synonyms and concrete terms users say (SMS, WhatsApp, messages) are missing. It is below 4 because keyword coverage is not broad, and above 2 because the core relevant term is present.

3 / 5

Distinctiveness Conflict Risk

"Tyntec integration" and "interact with Tyntec data" anchor the skill to a specific branded niche, giving it distinct triggers with minimal conflict risk. It clearly fits the 5 anchor rather than 4 since the brand name is strongly distinguishing.

5 / 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.