Name: pitchly
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

pitchly

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

Quality

61%

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

Quality

Content

61%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 a strong, executable guide for the Membrane CLI workflow with good sequencing and validation around connection setup. Its main gaps are trimmable redundancy/padding, minor actionability holes around capturing the connection id, and the absence of validation guidance for destructive proxy requests.

Suggestions

Add an explicit validation/verification step for destructive proxy requests (POST/PUT/PATCH/DELETE), e.g. a GET to confirm the change or a dry-run note, to lift the workflow-clarity cap.

Show concretely where to obtain the connection id (e.g. parse `id` from the `connection ensure --json` output) so the action examples are fully executable end-to-end.

Remove the redundant 'Popular actions' section (it duplicates 'Searching for actions') and tighten padding like 'focus on the integration logic rather than auth plumbing' to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient executable commands, but contains trimmable padding ('focus on the integration logic rather than auth plumbing', 'This is the fastest way to get a connection') and redundant sections ('Popular actions' repeats the 'Searching for actions' command, 'Best practices' restates discover-before-build), placing it at the 'mostly efficient but could be tightened' anchor rather than the lean anchor above.	3 / 5
Actionability	It provides concrete, copy-paste-ready `membrane` CLI commands with flags across login, connection, action list/run, and proxy requests, plus a full flag table, but has minor gaps such as never showing where to capture the connection id from the `ensure` output and leaving 'Popular actions' without an example result, so it sits just below the fully-covered top anchor.	4 / 5
Workflow Clarity	The connection workflow is clearly sequenced with explicit state-based validation checkpoints (poll until READY, re-poll after CLIENT_ACTION_REQUIRED, error handling), but the proxy section enables destructive HTTP verbs (POST/PUT/PATCH/DELETE) with no validation or verification guidance, which caps workflow clarity at 3 per the destructive-operations rule.	3 / 5
Progressive Disclosure	It is a single, well-organized file with clear section headers and no nested or missing references (no bundle files exist), but at ~140 lines it duplicates 'Popular actions'/'Searching for actions' and could split the proxy flag table or best practices into referenced files, leaving it just below the cleanly-split top anchor.	4 / 5
	Total	14 / 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 functional and correctly pairs a 'what' with an explicit 'Use when' trigger, anchored on the distinct proper-noun 'Pitchly'. Its weakness is generic action verbs ('manage data/records') and a lack of varied, concrete trigger phrases and synonyms.

Suggestions

Replace generic verbs with concrete Pitchly-specific actions, e.g. 'Search and update records, build presentations, and automate Pitchly workflows.'

Expand the 'when' clause with concrete trigger phrases and synonyms users actually say, e.g. 'Use when the user mentions Pitchly, Pitchly records, Pitchly presentations, or wants to automate Pitchly workflows.'

Reference Pitchly-specific entities from the body (presentations, slides, workspaces, templates, brand styles) to raise specificity and distinctiveness.

Dimension	Reasoning	Score
Specificity	Names the Pitchly domain and a couple of actions ('Manage data, records, and automate workflows'), but those actions are generic rather than concrete, so it sits at the 'domain plus 1-2 actions, not comprehensive' anchor and not at the multi-specific-action level above.	3 / 5
Completeness	It states both a clear 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Pitchly data'), but the trigger clause is somewhat generic rather than listing concrete trigger phrases, which keeps it just below the top anchor.	4 / 5
Trigger Term Quality	It includes the natural proper-noun trigger 'Pitchly' and terms like 'data' and 'records', but lacks synonyms, file extensions, or common phrasing variations users might say, matching the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The proper-noun trigger 'Pitchly' gives it a clear niche with minimal conflict risk versus other skills, though the broad 'interact with Pitchly data' phrasing leaves minor overlap risk with a generic data skill rather than fully matching the distinct-trigger anchor.	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/pitchly/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.