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

Blog Docs Log in Get started

productiveio

Productive.io integration. Manage Organizations. Use when the user wants to interact with Productive.io 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/productiveio/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 content is a well-structured, actionable guide to driving Productive.io through the Membrane CLI, with concrete commands and a clear connection-readiness workflow. Its main weaknesses are mild verbosity, a duplicated entity list, and missing verification steps around destructive action/proxy calls.

Suggestions

Add an explicit validation/verification checkpoint before destructive proxy calls or action runs (e.g. confirm the target id, dry-run where supported, check the response for errors before proceeding).

De-duplicate the "Productive.io Overview" entity list ("Deals"/"Deal Budgets" are listed both nested and flat) and fix the step numbering ("Step 2" is referenced but no Step 1 is labeled; "1b" has no 1a).

Trim the PSA background paragraph ("Productive.io is a professional services automation platform...") which Claude can infer, keeping only what is specific to the integration.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the PSA intro paragraph and the duplicated entity list ("Deals"/"Deal Budgets" appear both nested and flat) add padding that could be trimmed.	3 / 5
Actionability	It provides concrete, executable commands for every stage (install, login, connection ensure, action run, proxy) plus a flags table, with only minor gaps such as the placeholder-heavy "Popular actions" section.	4 / 5
Workflow Clarity	The connect-to-ready flow is well sequenced with state polling and error fields, but destructive operations (action run, proxy POST/DELETE) have no validation or verification steps, capping this dimension at 3.	3 / 5
Progressive Disclosure	With no bundle files present, the single SKILL.md is organized into clear sections (overview, install, auth, connecting, searching, running, proxy, best practices); only the duplicated entity list and inconsistent step numbering ("Step 2"/"1b") keep it from a 5.	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 app-specific and includes an explicit "Use when" clause, but it is thin: it surfaces only one entity (Organizations) despite the skill covering many, and its trigger phrasing is generic. It is distinguishable and complete enough, just not comprehensive.

Suggestions

Expand the capability list beyond "Manage Organizations" to mention the other core entities the skill supports (e.g. deals, projects, tasks, time entries).

Sharpen the trigger clause with concrete natural phrases users would say, e.g. "Use when the user wants to manage Productive.io organizations, projects, tasks, deals, or time entries."

Add common synonyms/file or domain cues (e.g. "Productive.io data", "PSA", "agencies") to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	"Manage Organizations" names the domain plus one concrete action, but the description omits the many other entities the skill handles (deals, tasks, projects, time entries), so coverage is not comprehensive.	3 / 5
Completeness	It answers both what ("Productive.io integration. Manage Organizations.") and when ("Use when the user wants to interact with Productive.io data"), but the trigger clause is somewhat generic and the what is thin.	4 / 5
Trigger Term Quality	"Productive.io", "Organizations", and "interact with Productive.io data" give some relevant keywords, but common variations and synonyms users would say (projects, tasks, time tracking, budgets) are missing.	3 / 5
Distinctiveness Conflict Risk	Naming a specific SaaS app (Productive.io) gives it a clear, distinct niche with minimal conflict risk, though "Manage Organizations" alone is a concept many apps share.	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/productiveio/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.