Name: productlane
Rating: 50.4 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

productlane

Productlane integration. Manage Workspaces. Use when the user wants to interact with Productlane data.

Quality

55%

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

Quality

Content

56%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 generally actionable, well-sectioned guide to driving Productlane via the Membrane CLI, but it leans slightly verbose, inlines some reference-grade detail, and lacks explicit validation feedback loops for risky proxy operations.

Suggestions

Trim background prose (the 'Productlane Overview' hierarchy and the marketing-style intro) so the file opens directly with the working steps.

Add an explicit validation/verification checkpoint after destructive or batch proxy requests (e.g. re-fetch the resource to confirm the change) to lift workflow clarity.

Move the verbose clientAction field breakdown into a short reference table or a linked file so the main flow stays lean.

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient with concrete commands, but includes some unnecessary padding (the overview of what Productlane is, the 'Productlane Overview' hierarchy, and restated install/auth guidance) that could be tightened.	3 / 5
Actionability	Provides copy-paste-ready CLI commands with flags and a clear options table for proxy requests, with only minor gaps such as placeholders (CONNECTION_ID, <actionId>) left unresolved.	4 / 5
Workflow Clarity	The connection flow has a clear sequence with state-based branching and polling, but validation checkpoints are implicit (e.g. no explicit verify-after-action step) and destructive proxy requests lack a validation/verification feedback loop, capping the score.	3 / 5
Progressive Disclosure	Content is organized into clear sections and all references are inline CLI flags rather than separate files, but the body inlines a fair amount of API-reference-style detail (clientAction field breakdown, options table) that a simple skill could keep tighter; no external reference files are used.	3 / 5
	Total	13 / 20 Passed

Description

53%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 answers both what and when with an explicit trigger clause and a distinctive branded name, but it under-delivers on concrete capabilities and trigger-term richness, listing only the generic 'Manage Workspaces'.

Suggestions

Replace the single generic action 'Manage Workspaces' with 2-3 concrete verbs drawn from the body, e.g. 'collect feedback, prioritize features, and build roadmaps'.

Broaden trigger terms beyond 'interact with Productlane data' to include natural user phrases like 'Productlane feedback, feature requests, or roadmaps'.

Keep the explicit 'Use when...' clause but make its scope specific to Productlane tasks to sharpen the trigger.

Dimension	Reasoning	Score
Specificity	Names the Productlane domain but the only concrete action verb is the generic 'Manage Workspaces', which is minimal and not comprehensive relative to the overview body (boards, cards, comments, users).	2 / 5
Completeness	Clearly answers 'what' ('Productlane integration. Manage Workspaces.') and has an explicit 'Use when...' trigger clause, though the 'when' is somewhat generic.	4 / 5
Trigger Term Quality	Includes 'Productlane' and the natural phrase 'interact with Productlane data', but lacks synonyms, feature-level terms (feedback, roadmap, board), or extensions a user might say.	3 / 5
Distinctiveness Conflict Risk	The Productlane brand name gives it a clear niche with minimal overlap risk against other skills, though the generic 'interact with data' phrasing leaves minor ambiguity.	4 / 5
	Total	13 / 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/productlane/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.