CtrlK
BlogDocsLog inGet started
Tessl Logo

flespi

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

59

Quality

68%

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/flespi/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 content is a well-structured, mostly executable guide with strong validation in the connection workflow, but it has minor prose padding, dangling step references, and no external reference split.

Suggestions

Resolve the dangling "Step 2" / "1b" references by labeling Step 1 and Step 2 explicitly so the workflow reads as a coherent numbered sequence.

Trim marketing-style prose (e.g. "so you can focus on the integration logic rather than auth plumbing") and condense the URL-normalization explanation.

Add a short end-to-end example with a concrete returned JSON snippet for running an action to lift actionability toward fully copy-paste ready.

DimensionReasoningScore

Conciseness

The body is mostly tight executable commands with brief explanations, but contains minor over-explanation such as "so you can focus on the integration logic rather than auth plumbing" and the URL-normalization prose that could be trimmed. It is efficient with only minor padding, matching anchor 4.

4 / 5

Actionability

It provides concrete copy-paste commands (install, login, connection ensure, action run, request) plus a flag table, all executable with placeholders. It stops short of a fully fleshed end-to-end example with real returned values, leaving it just below anchor 5.

4 / 5

Workflow Clarity

The connection flow has explicit validation checkpoints and feedback loops (poll until READY, handle CLIENT_ACTION_REQUIRED, re-poll after action). However the "skip to Step 2" / "1b" references are dangling with no labeled Step 1 or Step 2, and running actions lacks result-validation, capping it at 4.

4 / 5

Progressive Disclosure

No bundle files exist; the single SKILL.md is well-organized into clear sections (Overview, Install, Auth, Connecting, Searching, Actions, Proxy, Best practices) with good navigation. It is above anchor 3 but lacks any one-level-deep reference split that anchor 5 rewards.

4 / 5

Total

16

/

20

Passed

Description

62%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 an explicit trigger tied to a distinct platform, but its action verbs are generic and it lacks varied natural trigger terms beyond the Flespi brand.

Suggestions

Replace generic verbs with concrete actions, e.g. "Query device messages, manage channels and streams, run calculations" instead of "Manage data, records".

Add natural trigger variations such as telematics, IoT device data, flespi.com, or REST API calls to broaden keyword coverage.

Tighten the "when" clause with concrete triggers, e.g. "Use when the user wants to query telematics device data or automate Flespi workflows."

DimensionReasoningScore

Specificity

"Manage data, records, and automate workflows" names the Flespi domain plus a few actions, but the verbs (manage, automate) are generic rather than concrete like "extract" or "fill". It sits above anchor 2 (minimal/generic actions) but below anchor 4 (several specific actions).

3 / 5

Completeness

It states the "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Flespi data"). Both are present, but the trigger phrasing is simple rather than the comprehensive concrete triggers of anchor 5.

4 / 5

Trigger Term Quality

The natural trigger is essentially the brand "Flespi" plus "Flespi data"; common variations or synonyms a user might say are largely missing. This matches anchor 3 (some relevant keywords, missing variations) better than anchor 4's broader keyword coverage.

3 / 5

Distinctiveness Conflict Risk

Flespi is a specific named platform giving it a clear niche and distinct trigger ("Flespi data"), but the generic action words (data, records, workflows) create minor overlap risk with general data-handling skills, keeping it just below anchor 5.

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