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

pennylane

Pennylane integration. Manage data, records, and automate workflows. Use when the user wants to interact with Pennylane 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/pennylane/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 highly actionable with a well-sequenced, state-aware connection workflow, but it opens with irrelevant padding about the unrelated PennyLane quantum-computing library that wastes tokens and risks confusing the model. Structure is clean with no external references needed.

Suggestions

Remove the 'PennyLane is a Python library for quantum machine learning...' preamble and the Circuit/Device/Template/QNode overview; they describe an unrelated library and pad the context with concepts Claude already knows.

Fix the step numbering: the body references 'Step 2' and a '1b.' heading without a labeled Step 1, so relabel the connection flow as explicit numbered steps.

Consider moving the proxy flags table into a short reference note so the main flow reads as a straight install→connect→act walkthrough.

Dimension	Reasoning	Score
Conciseness	The Membrane CLI sections are lean and command-driven, but the opening 'PennyLane is a Python library for quantum machine learning...' paragraphs and the irrelevant Circuit/Device/Template/QNode overview explain concepts Claude already knows and pad the doc; fits anchor 3 (mostly efficient, some unnecessary explanation) rather than 2 because the bulk is actionable.	3 / 5
Actionability	Provides copy-paste-ready commands throughout ('npm install -g @membranehq/cli@latest', 'membrane connection ensure "https://..."', 'membrane action run', 'membrane request') plus a complete flags table, covering the common cases exactly as anchor 5 describes.	5 / 5
Workflow Clarity	Clear install→authenticate→connect→poll→state-machine sequence with an explicit re-poll feedback loop ('poll again... to check if state moved to READY') and a state-driven decision table; fits anchor 4, held below 5 by minor looseness such as references to an undefined 'Step 2' and a stray '1b.' heading.	4 / 5
Progressive Disclosure	No bundle files exist and all content is appropriately inline in well-organized sections (Auth, Connecting, Searching, Running actions, Proxy, Best practices); fits anchor 4 (good structure, content appropriately placed) since the doc is longer than the under-50-line simple-skill exception that would allow a 5.	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 cleanly states what the skill does and when to use it with an explicit trigger clause, but the capability verbs are generic and the trigger keywords lack synonyms. Distinctiveness is anchored by the named app rather than by specific triggers.

Suggestions

Replace generic verbs with concrete actions, e.g. 'Create and search invoices, sync bank transactions, manage customers and records' instead of 'Manage data, records'.

Add natural trigger synonyms users might say, e.g. 'Use when the user wants to manage invoices, billing, or accounting data in Pennylane'.

Keep the explicit 'Use when...' clause but tie it to concrete Pennylane entities to sharpen distinctiveness.

Dimension	Reasoning	Score
Specificity	Names the domain plus action areas ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete; fits anchor 3 (domain + 1-2 actions, not comprehensive) better than anchor 2's minimal/generic bar and below anchor 4's several specific actions.	3 / 5
Completeness	Explicitly answers both 'what' ('Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with Pennylane data'); the when clause is present and reasonably specific, fitting anchor 4, though not as concrete as anchor 5's trigger phrases.	4 / 5
Trigger Term Quality	Includes the brand keyword and the natural phrase 'when the user wants to interact with Pennylane data', but lacks synonyms or variations a user might actually say; matches anchor 3 (some relevant keywords, missing common variations) rather than anchor 4's good coverage.	3 / 5
Distinctiveness Conflict Risk	The named app 'Pennylane' gives a clear niche with minimal conflict risk, fitting anchor 4 (mostly distinct, minor overlap); not a 5 because the action verbs ('manage data') are generic enough to overlap conceptually with other 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/pennylane/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.