Name: hologram
Rating: 61.6 (1 reviews)
Author: membranedev

hologram

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

Quality

72%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/hologram/SKILL.md

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 body is highly actionable with executable CLI commands and a well-sequenced connection workflow including state checkpoints and a polling feedback loop. Its main weaknesses are minor padding (the company blurb and a vague overview tree) and a 'Step 2' reference that lacks a matching header.

Suggestions

Trim the opening company description and the placeholder overview tree ('Use action names and parameters as needed') since they add tokens without actionable value.

Label the 'Searching for actions' section as 'Step 2' (or reword the 'skip to Step 2' reference) so the cross-reference resolves to an actual header.

Add an explicit validation/checkpoint note before running actions (e.g. confirm connection state is READY before `action run`) to close the minor workflow gap.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean command-driven content with copy-paste CLI invocations, but carries minor over-explanation (the Hologram company description and the vague overview tree 'Use action names and parameters as needed'), fitting 'efficient; minor instances of over-explanation that could be trimmed' rather than the fully lean level 5.	4 / 5
Actionability	It provides fully executable, copy-paste-ready commands throughout (install, login, connection ensure/get, action list/run, request proxy) with flags and JSON examples covering the common cases, matching the 'fully executable; copy-paste ready' anchor.	5 / 5
Workflow Clarity	There is a clear sequence (install → auth → connect → poll until READY → search → run → proxy) with explicit state-based checkpoints (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a re-poll feedback loop, but the 'Step 2' reference is not labeled as a header and some checkpoints are implicit, fitting 'clear sequence with most checkpoints present; minor validation gaps'.	4 / 5
Progressive Disclosure	No bundle files exist; the single file is organized into clear headed sections (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) with all content inline and a clearly signaled external docs link, giving good structure with only minor organization gaps rather than the well-split multi-file level 5.	4 / 5
	Total	17 / 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 a third-person trigger clause tied to a distinct product, but its action verbs are generic and its trigger vocabulary is narrow. Tightening 'manage data/records' into concrete capabilities and broadening the trigger terms would lift it from good to strong.

Suggestions

Replace generic verbs ('Manage data, records') with concrete Hologram capabilities (e.g. 'send device messages, query usage data, manage device SIMs').

Broaden the trigger clause to capture more natural phrasings: 'Use when the user wants to interact with Hologram devices, SIMs, cellular data, or IoT connectivity.'

Add a file-extension or product-specific keyword (e.g. 'Hologram API', 'IoT devices') to strengthen trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the Hologram domain plus three actions ('Manage data, records, and automate workflows'), but the actions are generic ('manage data') rather than concrete, so it matches the 'names domain and 1-2 concrete actions but not comprehensive' anchor and sits below the multi-specific-action level 4.	3 / 5
Completeness	Both 'what' ('Hologram integration. Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Hologram data') are present, but the 'when' trigger is somewhat narrow, matching the 'has both what and when; when could be more explicit or specific' anchor rather than the comprehensive level 5.	4 / 5
Trigger Term Quality	'Use when the user wants to interact with Hologram data' supplies a natural trigger phrase around 'Hologram', but coverage is limited to that one term with no synonyms or variations, fitting 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	'Hologram' is a specific named IoT connectivity product giving a clear niche with minimal conflict risk, though the generic 'manage data, records' framing keeps it just short of the fully distinct level 5.	4 / 5
	Total	14 / 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/hologram/SKILL.md
Commit: f484c82

Reviewed: 5 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.