Name: puppet
Rating: 43.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

puppet

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

Quality

43%

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

Quality

Content

38%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 CLI workflow guidance is concrete and executable, but the body is dominated by a large, largely-irrelevant bullet list that wastes tokens and offers no progressive disclosure. Moving the overview to a reference file and trimming irrelevant terms would markedly improve it.

Suggestions

Remove or relocate the ~120-item "Puppet Overview" bullet list — most entries (AI, Blockchain, Robotics, IoT, etc.) are unrelated to Puppet and add heavy padding.

Add a verification step after `membrane action run` (e.g. inspect the `output` field and confirm expected state) to satisfy validation for destructive/batch record operations.

Split the action/entity catalog into a separate `references/` file referenced one level deep from SKILL.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The ~120-item "Puppet Overview" bullet list includes many terms unrelated to Puppet (Artificial Intelligence, Blockchain, Robotics, IoT, Big Data, Serverless), which is heavily padded content Claude does not need, matching the severely verbose / heavily padded anchor.	1 / 5
Actionability	The "Working with Puppet" section provides concrete, copy-paste-ready commands (install, login, connection ensure, action run, request) with a flag table and JSON examples, with only minor gaps such as placeholder CONNECTION_IDs and the vague "Use action names and parameters as needed."	4 / 5
Workflow Clarity	There is a clear install → authenticate → connect → search → run sequence with connection-state checkpoints and polling feedback, but running actions on data/records (potentially destructive/batch) lacks result verification, capping workflow clarity per the destructive/batch validation guideline.	3 / 5
Progressive Disclosure	No bundle/reference files exist and the large overview list is inlined directly in SKILL.md rather than split into a separate reference, matching the anchor where content that clearly belongs in separate files is inlined.	2 / 5
	Total	10 / 20 Passed

Description

48%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 well-formed with an explicit trigger clause and a distinctive product name, but its capability list is generic rather than concrete Puppet actions. Strengthening the action verbs and adding natural trigger synonyms would raise it.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete Puppet-specific actions such as managing nodes, running tasks/plans, and querying inventory facts.

Expand the trigger clause with natural synonyms users say, e.g. "Use when the user wants to manage Puppet nodes, run tasks or plans, or query catalog/facts data."

Confirm third-person voice is preserved (it is) and keep the description under the same length while adding specificity.

Dimension	Reasoning	Score
Specificity	The description names the Puppet domain but the actions — "Manage data, records, and automate workflows" — are generic and not Puppet-specific concrete operations, fitting the anchor where the domain is named but actions are minimal or generic.	2 / 5
Completeness	It states a "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Puppet data"), but the "what" actions are generic, so it does not reach the clear, concrete both-anchors level.	3 / 5
Trigger Term Quality	"Puppet" and "Puppet data" are relevant keywords a user would say, but common variations or synonyms are missing, matching the anchor for some relevant keywords lacking common variations.	3 / 5
Distinctiveness Conflict Risk	The distinctive "Puppet" product name and scoped trigger ("interact with Puppet data") make it mostly distinct with only minor overlap risk against other infra-automation skills.	4 / 5
	Total	12 / 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/puppet/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.