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

densify

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

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/densify/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 highly actionable Membrane CLI integration guide with concrete commands and a well-sequenced, state-aware connection workflow. Its main weaknesses are some marketing-style over-explanation up front and a couple of small structural loose ends (the bare overview list and an undefined 'Step 2').

Suggestions

Trim the introductory paragraph to one factual sentence about what Densify does, dropping the audience/marketing language to improve token efficiency.

Either explain or remove the bare 'Densify Overview' list (Dataset/Column/Model/Inference/Project/User), which currently adds tokens without actionable guidance.

Resolve the 'skip to Step 2' reference by adding a clear 'Step 2' heading (e.g., over 'Searching for actions') so the workflow navigation is unambiguous.

Dimension	Reasoning	Score
Conciseness	Mostly efficient commands and flags, but the opening marketing-style paragraph ('It helps organizations analyze and optimize their cloud infrastructure spending... used by cloud engineers, IT managers, and finance teams') and the unexplained 'Densify Overview' bullet list are unnecessary padding.	3 / 5
Actionability	Provides fully executable, copy-paste-ready commands throughout (install, login, connection ensure, action list/run, request proxy) plus a complete proxy-flag table covering the common cases.	5 / 5
Workflow Clarity	Clear sequenced connection flow with explicit state-based validation checkpoints and feedback loops (BUILDING poll, CLIENT_ACTION_REQUIRED re-poll, CONFIGURATION_ERROR error check); minor gap is a 'skip to Step 2' reference with no matching Step 2 heading.	4 / 5
Progressive Disclosure	Well-organized into clear sections with content appropriately inline for a single-file CLI guide and no external bundle files needed; minor gaps include the unexplained overview list and a dangling 'Step 2' 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 is third-person, includes an explicit 'Use when' clause, and names a distinct product niche, but its action list is generic and its trigger-term coverage is narrow. It is solid but lacks the concrete, comprehensive specificity of the top anchors.

Suggestions

Replace generic verbs with concrete Densify actions, e.g. 'Analyze cloud resource utilization, surface rightsizing and cost-saving recommendations, and automate optimization workflows.'

Broaden trigger terms to include natural variations users might say, e.g. 'Use when the user wants to optimize cloud spend, analyze Densify recommendations, or manage Densify data and records.'

Tighten the 'when' clause with concrete trigger phrases that map directly to real user requests.

Dimension	Reasoning	Score
Specificity	Names the Densify domain plus a couple of actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete, matching the anchor for domain + 1-2 actions that aren't comprehensive.	3 / 5
Completeness	Explicitly answers both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Densify data'), with the 'when' present but somewhat generic, fitting just below the anchor that requires concrete trigger phrases.	4 / 5
Trigger Term Quality	Includes relevant natural terms ('Densify data', 'interact with Densify data') but lacks synonyms or variations beyond the product name, matching the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	'Densify' is a named niche product giving mostly distinct triggers, though the generic 'manage data, records' verbs create minor overlap risk with other data-handling 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/densify/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.