CtrlK
BlogDocsLog inGet started
Tessl Logo

asavie

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

56

Quality

65%

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/asavie/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 a clear connection workflow and explicit state checkpoints. Its main weaknesses are an undefined 'Step 2' reference, placeholder-only action examples, and a token-heavy inline entity list.

Suggestions

Define or remove the dangling 'skip to Step 2' reference — either add a 'Step 2: Search for actions' heading or reword to 'skip to Searching for actions'.

Add one fully concrete worked action example with real values (a real actionId and a representative --input payload) so the run pattern is copy-paste ready.

Move the 60-item Asavie entity catalog into a separate references/ file and link to it, keeping SKILL.md as an overview.

DimensionReasoningScore

Conciseness

The body is mostly lean executable CLI commands, but the 60-item Asavie entity catalog and a few explanatory sentences add padding that keeps it just short of fully lean.

4 / 5

Actionability

Concrete commands (login, connection ensure, action list/run, request with a flags table) cover the common cases, though action-run examples rely on generic placeholders like <actionId> and {"key": "value"}.

4 / 5

Workflow Clarity

The connection flow has explicit state-based checkpoints and error recovery (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but the referenced 'Step 2' is undefined and action execution lacks a validation feedback loop.

4 / 5

Progressive Disclosure

Clear section headers provide good navigation and the skill is self-contained, but the long inline entity catalog could live in a separate reference file rather than SKILL.md.

4 / 5

Total

16

/

20

Passed

Description

55%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' and is anchored to a distinctive product name, but its action list is generic and trigger-term coverage is thin. It reads well but lacks the concrete, varied triggers of a top-tier description.

Suggestions

Replace generic verbs ('Manage data, records, automate workflows') with specific Asavie capabilities (e.g., manage SIMs, device profiles, policies, data plans, and workflow automations).

Expand the 'Use when...' clause with concrete enumerated triggers such as 'Use when the user mentions Asavie SIMs, device profiles, data plans, policies, tunnels, or Asavie API interactions'.

Add common synonyms or product-specific terms so the trigger is more likely to match natural user phrasing.

DimensionReasoningScore

Specificity

"Manage data, records, and automate workflows" names the Asavie domain plus a couple of actions, but the verbs are generic and not comprehensive, matching the '1-2 concrete actions' anchor.

3 / 5

Completeness

Both a 'what' ("Manage data, records, and automate workflows") and an explicit 'Use when...' trigger are present, but the 'when' is generic rather than enumerated concrete trigger phrases.

4 / 5

Trigger Term Quality

The only natural keyword is the proper noun "Asavie" / "Asavie data" with no synonyms, file extensions, or common phrasings, fitting the 'one or two generic keywords' anchor.

2 / 5

Distinctiveness Conflict Risk

The "Asavie" proper noun gives it a clear niche with minimal conflict risk, though the generic 'data/records/workflows' actions rely on the product name for distinctiveness.

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.