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

prodpad

ProdPad integration. Manage data, records, and automate workflows. Use when the user wants to interact with ProdPad 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/prodpad/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 a solid, executable guide with a well-sequenced, checkpointed connection workflow and good section structure. The main gaps are minor: some trimmable explanatory prose, no ProdPad-specific worked action example, inconsistent step numbering, and a redundant section.

Suggestions

Fix the step numbering: either add a labeled 'Step 1' / 'Step 1a' before '#### 1b' or rename it, and ensure the referenced 'Step 2' exists.

Add one concrete ProdPad action example, e.g. `membrane action run <ideasListId> --connectionId=... --input '{"limit": 25}' --json`, with a sample output field.

Trim the two-sentence ProdPad definition and the 'so you can focus on the integration logic' aside, and merge the redundant '## Popular actions' into 'Searching for actions'.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with concrete commands, but includes minor over-explanation such as the two-sentence ProdPad intro ('ProdPad is a product management software...') and 'so you can focus on the integration logic rather than auth plumbing'; not 5 because of these trimmable asides.	4 / 5
Actionability	Provides copy-paste-ready commands for the full flow (install, login, connection ensure, action list/run, request) plus a concrete proxy flag table; not 5 because ProdPad-specific run examples with real input/output (e.g. listing ideas) are absent and CONNECTION_ID stays an unreplaced placeholder.	4 / 5
Workflow Clarity	The connect-to-ProdPad flow is well sequenced with explicit state checkpoints and a feedback loop (poll until READY, handle CLIENT_ACTION_REQUIRED, re-poll); not 5 because the 'Running actions' section lacks result validation and the step numbering ('1b', references to a missing 'Step 2') is inconsistent.	4 / 5
Progressive Disclosure	Single-file content is well organized into clear sections (Overview, Install, Auth, Connecting, Searching, Best practices) with no nested references; not 5 because of minor organization gaps such as the orphan '#### 1b' heading and a redundant '## Popular actions' section that repeats the search command.	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 correctly answers both 'what' and 'when' in third person and leverages a distinct product name, but its actions and triggers are generic. Sharpening the action list and adding concrete ProdPad-specific trigger phrases would lift the weaker dimensions.

Suggestions

Replace generic actions with concrete ProdPad ones, e.g. 'Create and prioritize ideas, build roadmaps, and manage feedback in ProdPad.'

Expand the trigger to natural user phrases, e.g. 'Use when the user wants to manage ProdPad ideas, roadmaps, feedback, or user data.'

Add ProdPad-specific nouns (ideas, roadmaps, feedback) so the skill triggers on the terms users actually say.

Dimension	Reasoning	Score
Specificity	Names the domain (ProdPad) and lists a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete; not below 2 because multiple action categories are named, not above 3 because none are specific.	3 / 5
Completeness	Both 'what' ('ProdPad integration. Manage data, records, and automate workflows.') and 'when' ('Use when the user wants to interact with ProdPad data.') are present and explicit, but the 'when' is generic rather than concrete trigger phrases, so it does not reach 5.	4 / 5
Trigger Term Quality	The trigger relies almost entirely on the product name 'ProdPad' via 'Use when the user wants to interact with ProdPad data'; it misses natural variations/synonyms users would say (ideas, roadmaps, feedback) that the body itself mentions.	3 / 5
Distinctiveness Conflict Risk	The named product 'ProdPad' gives a clear niche with minimal conflict risk, but the generic 'what'/'when' phrasing keeps it from the crisp, concrete-trigger distinctiveness of anchor 5.	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/prodpad/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.