Name: holistics
Rating: 56.8 (1 reviews)
Author: membranedev

holistics

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

Quality

65%

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/holistics/SKILL.md

Quality

Content

67%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 delivers executable, well-structured CLI guidance with a clear connection-state workflow and feedback loops. It is held back by generic Membrane boilerplate and explanatory padding that competes with genuinely Holistics-specific content.

Suggestions

Trim generic Membrane explanations (auth plumbing, URL normalization) that Claude can infer, keeping only the commands and Holistics-specific behavior.

Replace the vague "Use action names and parameters as needed" under Holistics Overview with a few concrete example actions (e.g., listing/scheduling reports, querying datasets).

Move the detailed CLIENT_ACTION_REQUIRED connection-state handling into a referenced file or condense it, since it is generic across Membrane skills rather than Holistics-specific.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-driven and efficient, but carries generic Membrane boilerplate and explanatory padding (e.g., "so you can focus on the integration logic rather than auth plumbing", the URL-normalization aside) that could be trimmed.	3 / 5
Actionability	It provides concrete, executable commands throughout (install, login, connection ensure, action list/run, request) plus a flag table; placeholder tokens like CONNECTION_ID and QUERY are clearly marked, leaving only minor gaps.	4 / 5
Workflow Clarity	The connection flow is clearly sequenced with explicit polling and state checkpoints (READY, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) and a re-poll feedback loop, though the steps are not framed as a tight end-to-end checklist.	4 / 5
Progressive Disclosure	No bundle files exist, so scoring reflects structure: headers organize the content well with no nested references, but the skill exceeds 50 lines and inlines connection-state detail that is somewhat generic rather than Holistics-specific.	4 / 5
	Total	15 / 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 in correct third-person voice and covers both what the skill does and when to use it, anchored to a distinct product name. Its main weakness is generic action language and thin natural trigger coverage that stops just short of the top anchors.

Suggestions

Replace generic verbs with concrete Holistics actions, e.g. "query datasets, schedule reports, and manage data sources and dashboards".

Expand the 'Use when' clause with natural triggers users actually say, such as "when the user asks about Holistics reports, dashboards, datasets, or scheduled deliveries".

Drop the filler phrase "Holistics integration." and lead with the concrete actions to sharpen specificity.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Holistics domain with a few actions, but the actions are generic rather than concrete (e.g., no mention of reports, dashboards, datasets, or data sources).	3 / 5
Completeness	Both halves are present — "Manage data, records, and automate workflows" (what) and "Use when the user wants to interact with Holistics data" (when) — but the trigger clause is generic rather than listing concrete triggers.	4 / 5
Trigger Term Quality	It surfaces "Holistics" and "data" as keywords but omits natural variations and synonyms a user would say (dashboards, reports, BI, datasets), leaving keyword coverage partial.	3 / 5
Distinctiveness Conflict Risk	The named product "Holistics" gives a distinct niche with low conflict risk, though the generic action phrasing ("manage data, records") leaves minor overlap with other data/automation 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/holistics/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.