CtrlK
BlogDocsLog inGet started
Tessl Logo

calltrackingmetrics

Calltrackingmetrics integration. Manage Accounts. Use when the user wants to interact with Calltrackingmetrics 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

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/calltrackingmetrics/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 body is highly actionable with executable commands and a strong, validated connection workflow, supported by clean section organization; minor conciseness and workflow-labeling gaps hold it back from full marks.

DimensionReasoningScore

Conciseness

The body is mostly lean with concrete CLI commands throughout, though the opening platform-description paragraph and a few prose asides ("This is the fastest way to get a connection") could be trimmed.

4 / 5

Actionability

Copy-paste-ready commands cover the common cases (install, login, connection ensure, action list/run, request proxy) and a Popular actions table gives concrete action keys.

5 / 5

Workflow Clarity

The connection setup has a clear sequence with explicit validation checkpoints and feedback loops (poll --wait, check READY/CLIENT_ACTION_REQUIRED, re-poll), but "Step 2" is referenced without being labeled and running actions lacks result verification.

4 / 5

Progressive Disclosure

A single self-contained file with well-organized section headers and easy header-based navigation; no nested references, though the large Popular actions table and length keep it just shy of fully split.

4 / 5

Total

17

/

20

Passed

Description

66%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 is distinct and includes an explicit 'Use when' trigger, but it undersells the skill's real capabilities with a single generic action ("Manage Accounts") and thin keyword coverage.

Suggestions

Replace the generic "Manage Accounts" with several concrete actions the skill supports (e.g., manage calls, contacts, tracking numbers, send SMS) to lift specificity.

Expand the 'Use when' clause with natural trigger phrases users would say, such as 'call tracking', 'tracking numbers', or 'call logs'.

Add common synonyms or file/term variations to broaden trigger term coverage beyond the brand name.

DimensionReasoningScore

Specificity

Names the domain ("Calltrackingmetrics integration") and one concrete action ("Manage Accounts"), but the single action is generic and coverage is far from comprehensive.

3 / 5

Completeness

Both a "what" ("Manage Accounts") and an explicit "when" ("Use when the user wants to interact with Calltrackingmetrics data") are present, though the trigger is generic rather than concrete.

4 / 5

Trigger Term Quality

The brand name "Calltrackingmetrics" and "Accounts" are relevant keywords, but common natural terms users would say (calls, contacts, SMS, tracking numbers) are absent.

3 / 5

Distinctiveness Conflict Risk

The named SaaS platform "Calltrackingmetrics" carves a clear niche with brand-specific triggers and minimal overlap risk with other skills.

5 / 5

Total

15

/

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.