Name: density
Rating: 59.2 (1 reviews)
Author: membranedev

density

Density integration. Manage data, records, and automate workflows. Use when the user wants to interact with Density 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/density/SKILL.md

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 body is a strong, actionable integration guide with executable CLI commands and a clear state-driven workflow. Its main weaknesses are some non-essential introductory prose and slightly inconsistent step numbering rather than structural or actionability problems.

Dimension	Reasoning	Score
Conciseness	The bulk is efficient command-driven documentation, but the opening paragraph explaining what Density the product is and asides like 'so you can focus on the integration logic rather than auth plumbing' are unnecessary explanation that could be trimmed.	3 / 5
Actionability	Provides copy-paste-ready executable commands for install, login, headless auth, connection ensure, polling, action search, action run with JSON input, and proxy requests, plus a flags table — covering the common cases comprehensively.	5 / 5
Workflow Clarity	A clear install → auth → connect → poll → search → run → proxy sequence with state-based checkpoints (READY, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) and a re-poll loop, but step numbering is inconsistent ('1b' with no '1a', a referenced 'Step 2') and there is no explicit validation/retry checklist.	4 / 5
Progressive Disclosure	A single well-organized document with clear section headers and no nested references; no bundle files exist, so all content is appropriately inline, though it is somewhat long for a SKILL.md overview and the proxy/flags detail could plausibly live in a separate reference.	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 correctly names the Density domain and includes a 'Use when' trigger, achieving adequate completeness and distinctiveness. It is held back by generic action verbs and limited natural trigger-term coverage rather than concrete, specific capabilities.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Density-specific actions such as 'query space and membership counts, retrieve sensor and device data, and trigger occupancy-based workflows'.

Expand the 'Use when' clause with concrete trigger phrases users would actually say, e.g. 'Use when the user asks about building occupancy, space utilization, sensor counts, or Density reports'.

Add natural synonyms and surface terms (occupancy, utilization, sensors, counts) to broaden trigger-term coverage beyond the single keyword 'Density'.

Dimension	Reasoning	Score
Specificity	Names the Density domain and a couple of actions ('Manage data, records, and automate workflows') but the actions are generic rather than concrete and specific, matching the anchor for 1-2 concrete actions without comprehensive coverage.	3 / 5
Completeness	States both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Density data'), but the when-clause could be more specific with concrete trigger phrases.	4 / 5
Trigger Term Quality	Includes the relevant term 'Density data' and 'interact with Density data', but leans on generic words ('data', 'records', 'workflows') and lacks common synonyms or extensions, matching 'some relevant keywords but missing variations'.	3 / 5
Distinctiveness Conflict Risk	The named 'Density' niche keeps it mostly distinct from other skills, though the generic 'manage data, records, automate workflows' phrasing creates minor overlap risk with general data skills.	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/density/SKILL.md
Commit: f484c82

Reviewed: ~18 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.