Name: volvo-aemp
Rating: 59.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

volvo-aemp

Volvo AEMP integration. Manage Organizations. Use when the user wants to interact with Volvo AEMP data.

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/volvo-aemp/SKILL.md

Quality

Content

71%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 solid connection-state feedback loop, but it carries some unnecessary prose and inlines a large reference table that would be better placed in a separate file. Fixing the dangling step references and trimming marketing language would round it out.

Suggestions

Move the Popular actions table into a references file (e.g. references/actions.md) and link to it from the body to improve progressive disclosure.

Resolve the dangling "skip to Step 2" / unlabeled "1b" numbering by explicitly labeling the workflow steps.

Trim marketing-style padding (e.g. "so you can focus on the integration logic rather than auth plumbing") to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	Mostly command-driven and efficient, but includes marketing-style padding ("so you can focus on the integration logic rather than auth plumbing") and explanatory prose Claude does not strictly need.	3 / 5
Actionability	Provides copy-paste-ready commands for every stage (install, login, connection ensure/get, action list/run, request) plus a concrete table of action keys and flags, fully covering the common cases.	5 / 5
Workflow Clarity	A clear install→login→connect→search→run sequence exists with an explicit state-polling feedback loop (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but the dangling "Step 2" reference and unlabeled "1b" are minor navigation gaps.	4 / 5
Progressive Disclosure	Sections are well-organized, but the 13-row Popular actions table is bulk reference content inlined into a single monolithic file with no external references to split it out.	3 / 5
	Total	15 / 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 has a clear niche and an explicit Use-when clause, but its capability statement is thin and somewhat misaligned with the skill's actual equipment-telematics focus. Expanding the action list and trigger phrasings would lift specificity and trigger quality.

Suggestions

Replace the generic "Manage Organizations" with the skill's actual capabilities, e.g. "Track Volvo construction equipment location, utilization, hours, fuel, and fault codes."

Broaden trigger terms to include natural phrasings such as "Volvo equipment", "fleet telematics", "machine location", or "AEMP data".

Tighten the Use-when clause to concrete triggers, e.g. "Use when the user wants to query Volvo CE fleet telematics, equipment status, or fault codes."

Dimension	Reasoning	Score
Specificity	Names the domain ("Volvo AEMP integration") and one concrete action ("Manage Organizations"), but the action is generic and does not reflect the equipment/fleet telematics capabilities actually documented in the body.	3 / 5
Completeness	States both a "what" ("Volvo AEMP integration. Manage Organizations.") and an explicit "when" ("Use when the user wants to interact with Volvo AEMP data"), though the "what" is thin and the trigger could be more specific.	4 / 5
Trigger Term Quality	Includes the core domain term "Volvo AEMP" and "Volvo AEMP data", but lacks common synonyms or concrete phrasings a fleet manager might say (equipment, fleet, telematics, machine location).	3 / 5
Distinctiveness Conflict Risk	"Volvo AEMP integration" is a clear, narrow niche with a distinct trigger; it is unlikely to fire for any unrelated skill.	5 / 5
	Total	15 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/volvo-aemp/SKILL.md
Commit: f484c82

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.