Name: productboard
Rating: 55.2 (1 reviews)
Author: membranedev

productboard

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

Quality

62%

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

Quality

Content

63%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 actionable with concrete Membrane CLI commands and a validated connection workflow, but it carries unnecessary conceptual padding up front and inlines reference material that, given its length, would benefit from separate files.

Suggestions

Cut the introductory paragraph explaining what Productboard is and who uses it; Claude already knows this and it adds no integration guidance.

Move the proxy flag table and the detailed clientAction schema into a references file (e.g. reference/proxy.md) and link to it from SKILL.md to improve progressive disclosure.

Reconcile the duplicated action-discovery guidance ('Searching for actions' vs 'Popular actions') into one section to remove redundancy.

Dimension	Reasoning	Score
Conciseness	The core CLI guidance is efficient, but the opening paragraph explaining what Productboard is and the vague 'Productboard Overview' section restate concepts Claude already knows and add padding, fitting 'mostly efficient but includes some unnecessary explanation'.	3 / 5
Actionability	Concrete, copy-pasteable commands are given throughout (install, login, connection ensure, action list/run, request) with a flag table; minor gaps remain since CONNECTION_ID and QUERY placeholders must be substituted, fitting 'mostly executable guidance with minor gaps'.	4 / 5
Workflow Clarity	The connect-to-run flow is sequenced with state-based validation checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a poll-retry loop, but a couple of transitions (e.g. where 'Step 2' lives) are implicit, fitting 'clear sequence with most checkpoints present; minor validation gaps'.	4 / 5
Progressive Disclosure	Sections are header-organized and navigable, but at 150+ lines with no bundle files, reference-style content (the proxy flag table, the full clientAction schema) is inlined rather than split into one-level-deep references, fitting 'some structure but could be better organized'.	3 / 5
	Total	14 / 20 Passed

Description

61%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 distinct and includes an explicit trigger clause, but its capability list is generic ('manage data, records, automate workflows') rather than concrete, and trigger-term coverage relies on a single proper noun with no synonyms.

Suggestions

Replace generic verbs with concrete actions, e.g. 'list features, fetch insights, update components, and tag records' instead of 'manage data, records, and automate workflows'.

Add natural trigger variations and entities users actually mention, such as 'features, components, insights, roadmaps, or Productboard API'.

Tighten the 'what' so it lists the specific Productboard objects the skill operates on (features, components, insights, users, tags).

Dimension	Reasoning	Score
Specificity	The actions 'Manage data, records, and automate workflows' name the domain but are generic and minimal rather than concrete, matching the 'names the domain but actions are minimal or generic' anchor rather than the 3 which requires concrete actions.	2 / 5
Completeness	Both a 'what' (manage data, records, automate workflows) and an explicit 'when' ('Use when the user wants to interact with Productboard data') are present, though the 'what' is somewhat vague; the explicit 'Use when' clause avoids the 3-cap.	4 / 5
Trigger Term Quality	It surfaces the natural term 'Productboard' and 'Productboard data' but offers no synonyms or variations, fitting 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	Tying the skill to the specific product 'Productboard' gives it a clear niche with distinct triggers and minimal conflict risk with other skills.	5 / 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/productboard/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.