Name: samsara
Rating: 66.4 (1 reviews)
Author: membranedev

samsara

Samsara integration. Manage Drivers, Assets, Locations, Trips, Reports. Use when the user wants to interact with Samsara data.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

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.

A well-structured, highly actionable CLI integration guide with copy-paste commands and a clear connection-state workflow including feedback loops. The chief weaknesses are mild conceptual padding in the overview and a long inline entity list that could be better organized.

Suggestions

Trim the opening overview paragraph and 'Agent Types' aside to focus on what Claude needs to run the CLI rather than general Samsara background.

Add an explicit 'verify the result' step after 'membrane action run' (e.g., check the output field for errors before proceeding) to strengthen the action-execution workflow.

Collapse the 27-item 'Samsara Overview' bullet list into grouped categories or move the exhaustive enumeration to a reference file, keeping only the most common entities inline.

Dimension	Reasoning	Score
Conciseness	Largely efficient command-driven content with a useful flags table, but the opening overview paragraph and the 'Agent Types' aside explain context that adds mild padding without earning much.	4 / 5
Actionability	Provides fully executable, copy-paste-ready CLI commands (membrane login, connection ensure/get with --wait, action list/run, request proxy) plus a concrete flags table covering the common interaction cases.	5 / 5
Workflow Clarity	The connection setup is clearly sequenced with state-based polling (BUILDING -> READY) and a clientAction feedback loop, though action execution lacks an explicit verify-result checkpoint.	4 / 5
Progressive Disclosure	Single well-organized file with clear section headers; no external bundle references are needed, though the 27-item inline entity list leans toward monolithic structure that could be trimmed or split.	4 / 5
	Total	17 / 20 Passed

Description

78%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.

A concise, third-person description that covers both what the skill manages and when to use it, with a Samsara-specific niche that minimizes conflict risk. The main weakness is the generic verb 'Manage' and a broad 'when' clause that could name more concrete trigger phrasings.

Suggestions

Replace the generic verb 'Manage' with specific operations (e.g., 'Create, list, update, and query Drivers, Assets, Locations, Trips, and Reports').

Tighten the 'Use when' clause with concrete trigger phrases users would actually say (e.g., 'Use when the user asks about driver logs, vehicle trips, asset locations, or Samsara reports').

Dimension	Reasoning	Score
Specificity	Names the domain and five concrete managed objects ('Drivers, Assets, Locations, Trips, Reports') but the verb 'Manage' is generic rather than enumerating distinct operations, leaving minor coverage gaps.	4 / 5
Completeness	Explicitly states both what ('Manage Drivers, Assets, Locations, Trips, Reports') and when ('Use when the user wants to interact with Samsara data'), though the 'when' clause is fairly broad rather than tied to concrete trigger phrases.	4 / 5
Trigger Term Quality	Includes natural Samsara terms (Drivers, Assets, Locations, Trips, Reports) and a 'Use when' clause, but 'interact with Samsara data' is somewhat generic and misses common synonyms or phrasings.	4 / 5
Distinctiveness Conflict Risk	Targets a clearly distinct Samsara-specific niche with brand-bound triggers ('Samsara data'), making mis-triggering against other skills unlikely.	5 / 5
	Total	17 / 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/samsara/SKILL.md
Commit: f484c82

Reviewed: 10 hours 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.