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

pilvio

Pilvio integration. Manage Organizations, Pipelines, Users, Goals, Filters. Use when the user wants to interact with Pilvio 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

Passed

No findings from the security scan

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 content is highly actionable with copy-paste CLI commands and a solid connection-state feedback loop, and it is well-structured with clear headers. Weaknesses are minor: a padded marketing intro and the lack of any external reference files for a skill of this length.

Suggestions

Trim the conceptual intro paragraph about what Pilvio is, since Claude does not need platform marketing context to run the CLI.

Move the proxy flag reference table and detailed action-discovery guidance into a one-level-deep reference file (e.g. references/api.md) and link to it from the body to improve progressive disclosure.

Add an explicit validation/check step before running potentially destructive actions (e.g. confirm intent or dry-run) to strengthen workflow clarity.

Dimension	Reasoning	Score
Conciseness	The body is mostly command- and table-driven and efficient, but the marketing-style intro ("Pilvio is a white-label cloud platform...") and phrases like "burn less tokens" are minor over-explanation that could be trimmed, matching anchor 4 rather than 5.	4 / 5
Actionability	It provides copy-paste-ready commands across the common cases (install, login, connection ensure, action list/run, request proxy) plus a flag reference table, fully matching the anchor 5 "copy-paste ready code covering common cases".	5 / 5
Workflow Clarity	The connection flow has an explicit state machine (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) with polling feedback, giving clear sequencing with most checkpoints present, but there is no explicit validation step before potentially destructive action runs and later sections are loosely sequenced, capping it at 4.	4 / 5
Progressive Disclosure	The body is well-organized with clear section headers and no nested references, but at ~140 lines it is entirely self-contained with no one-level-deep reference files for content like the proxy flag table or action discovery, leaving minor organization gaps versus the anchor 5 split-content pattern.	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.

The description is concise, third-person, and clearly names the Pilvio niche with an explicit "Use when" trigger, giving it strong distinctiveness. Its main limitation is that "Manage ..." uses one generic verb over a noun list and the trigger clause is broad rather than scenario-specific.

Suggestions

Replace the single verb "Manage" with distinct concrete actions per entity (e.g., "Create and manage Organizations, run Pipelines, invite Users") to raise specificity.

Make the "Use when" trigger more scenario-rich, e.g. "Use when the user wants to list or create Pilvio organizations, run pipelines, or manage users and goals."

Dimension	Reasoning	Score
Specificity	"Manage Organizations, Pipelines, Users, Goals, Filters" lists several concrete entities, but the single generic verb "Manage" applied to a noun list is less action-specific than the multi-verb anchor 5 example, so it sits at 4 rather than 5.	4 / 5
Completeness	It states both a clear "what" (Pilvio integration managing those entities) and an explicit "Use when the user wants to interact with Pilvio data" trigger, but the "when" is somewhat broad and does not enumerate concrete triggering scenarios, matching anchor 4 rather than 5.	4 / 5
Trigger Term Quality	"Pilvio" plus the enumerated entity names (Organizations, Pipelines, Users, Goals, Filters) give good keyword coverage, though common synonyms or phrasings users might actually say are not exhaustively covered, keeping it just below 5.	4 / 5
Distinctiveness Conflict Risk	Naming the specific niche platform "Pilvio" with its distinct entity vocabulary gives a clear niche with minimal overlap risk against other skills.	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/pilvio/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.