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

Blog Docs Log in Get started

piano

Piano integration. Manage data, records, and automate workflows. Use when the user wants to interact with Piano 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/piano/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 integration guidance is concrete and the connection workflow has good state-checkpointing, but the document is undermined by an unrelated, inaccurate musical-piano intro and overview that pad the content and confuse the skill's true purpose. Tightening these would lift conciseness and organization notably.

Suggestions

Remove the musical-piano intro paragraph and 'Piano Overview' (Song/Arrangement/Lesson/Exercise/Sheet Music/Setting) — they describe a different product and pad the skill with wrong context.

Label the post-connection phase explicitly as 'Step 2' (or remove the 'Step 2' references) so the 'skip to Step 2' instructions resolve to a real heading.

Add a brief validation/verification step after running actions (e.g., inspect the `output` field and confirm the expected record changed) for destructive or batch operations.

Dimension	Reasoning	Score
Conciseness	The Membrane CLI sections are mostly efficient, but the intro paragraph ('a virtual piano that allows users to play music...') and the 'Piano Overview' bullets (Song, Arrangement, Lesson...) are unnecessary padding that is also unrelated to the actual Piano platform integration.	3 / 5
Actionability	It provides copy-paste-ready commands (login, connection ensure, action list/run, request) plus a flag table; not a 5 because details like obtaining the specific actionId and post-run result handling have minor gaps.	4 / 5
Workflow Clarity	The connection flow is well sequenced with an explicit state feedback loop (READY / BUILDING poll / CLIENT_ACTION_REQUIRED / error), but the repeatedly referenced 'Step 2' is never labeled and there is no validation after running actions.	4 / 5
Progressive Disclosure	Sections are well-organized with clear headers and the skill needs no bundle files, but the inlined irrelevant musical-piano content is an organization gap that keeps it below 5.	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 correctly answers both what and when with a clear third-person 'Use when' trigger, but its action list is generic and its trigger vocabulary is thin. It is competent but not crisp enough to score at the top of the scale.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Piano-platform actions (e.g., 'Create and update records, query subscriber data, trigger automation workflows').

Broaden trigger terms with synonyms a user might say (e.g., 'subscribers', 'Piano records', 'Piano workflows', 'piano.io').

Disambiguate from the musical instrument by signaling the platform (e.g., 'Piano (piano.io) subscription/commerce platform').

Dimension	Reasoning	Score
Specificity	Names the Piano domain and a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete like extracting or filling, so it lands at 'domain + 1-2 actions, not comprehensive' rather than 4.	3 / 5
Completeness	It has both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Piano data'); not a 5 because the 'what' is vague rather than concrete.	4 / 5
Trigger Term Quality	The natural trigger phrases are essentially 'Piano' and 'interact with Piano data' — relevant but with no synonyms or variations, matching 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	'Piano integration' tied to data/records/workflows signals a distinct platform niche, but the word 'Piano' overlaps with musical-instrument skills, giving minor conflict risk rather than minimal.	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/piano/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.