CtrlK
BlogDocsLog inGet started
Tessl Logo

fractel

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

60

Quality

70%

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/fractel/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 a strong, executable CLI guide with concrete commands, a flags table, and explicit connection-state validation with feedback loops. Its main gaps are minor: a little explanatory padding and loose step numbering rather than a crisply labeled multi-step workflow.

DimensionReasoningScore

Conciseness

The body is mostly concrete commands with only minor over-explanation (e.g. 'so you can focus on the integration logic rather than auth plumbing' and the introductory platform description), fitting 'efficient; minor instances of over-explanation that could be trimmed.'

4 / 5

Actionability

It provides copy-paste-ready, executable commands throughout (npm install, membrane login, connection ensure, action run, request) plus a concrete flags table, covering the common cases as the anchor 5 example does.

5 / 5

Workflow Clarity

There is a clear sequence with explicit state-validation checkpoints and feedback loops (poll until READY, handle CLIENT_ACTION_REQUIRED, retry after user action, inspect error on SETUP_FAILED), but step labeling is loose ('skip to Step 2' with no labeled Step 2 header), leaving a minor gap below anchor 5.

4 / 5

Progressive Disclosure

The single SKILL.md is well-organized into clearly headed sections (Overview, Authentication, Connecting, Searching, Running actions, Proxy, Best practices) with no nested references, but at ~145 lines with no navigation aid or split reference material it sits just below the clean anchor 5.

4 / 5

Total

17

/

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' trigger and a clear brand niche, but its capability language is generic ('manage data, records, and automate workflows') rather than naming FracTEL's actual communication features. It is competent but under-specific.

Suggestions

Replace generic actions with concrete FracTEL capabilities, e.g. 'Send and receive SMS, manage phone calls and numbers, and generate billing reports.'

Add natural trigger synonyms users would say, such as 'SMS', 'messages', 'phone calls', or 'call logs', alongside 'FracTEL'.

Broaden the 'when' clause to cover the real use cases, e.g. 'Use when the user wants to send SMS, manage calls, or query FracTEL communication data.'

DimensionReasoningScore

Specificity

It names the domain ('FracTEL integration') but the actions ('Manage data, records, and automate workflows') are generic rather than concrete FracTEL capabilities like sending SMS or making calls, matching the 'names domain but actions are minimal/generic' anchor.

2 / 5

Completeness

It answers both 'what' (FracTEL integration managing data/records/workflows) and 'when' ('Use when the user wants to interact with FracTEL data'), but the 'when' is narrow and the 'what' is generic, so it falls short of the fully concrete anchor 5.

4 / 5

Trigger Term Quality

It includes the brand keyword 'FracTEL' and a 'Use when' clause, but misses the natural terms users would actually say (SMS, calls, phone numbers, messaging), fitting 'some relevant keywords but missing common variations or synonyms.'

3 / 5

Distinctiveness Conflict Risk

The 'FracTEL' brand name carves a clear niche and the trigger is brand-specific, leaving only minor overlap risk with generic data-management skills, matching 'mostly distinct; minor overlap risk.'

4 / 5

Total

13

/

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.