Name: profitwell
Rating: 56.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

profitwell

ProfitWell integration. Manage Users, Organizations. Use when the user wants to interact with ProfitWell data.

Quality

65%

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

Quality

Content

65%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 highly actionable with executable CLI commands and a solid connection state machine, but it suffers from an oversized inline entity list, missing validation for destructive action execution, and no progressive disclosure into reference files.

Suggestions

Move the 45-item entity catalog into a references file (e.g., references/entities.md) and link to it from the overview to reduce the inline token load.

Add a verification step after running actions (e.g., re-query or check the action output/error before reporting success) to satisfy the destructive/batch validation requirement.

Trim the introductory paragraph explaining what ProfitWell is, since it restates product knowledge Claude already has.

Dimension	Reasoning	Score
Conciseness	Mostly efficient command-driven content, but the 45-item flat entity bullet list and the introductory 'what ProfitWell is' paragraph are unnecessary padding that could be tightened, matching 'mostly efficient but includes some unnecessary explanation'.	3 / 5
Actionability	It provides copy-paste-ready, fully executable commands with real flags (install, login, connection ensure, poll with --wait, action list/run, request proxy) and a concrete options table covering the common cases.	5 / 5
Workflow Clarity	The connection setup has a clear sequence with a polling/state feedback loop, but running actions (which can be destructive per the Charges/Billing/Subscriptions entities) lacks any validation or verification checkpoint, capping this at 3 per the destructive-operations rule.	3 / 5
Progressive Disclosure	Section headings give reasonable structure, but at ~195 lines everything is inlined in one file with no external references — the entity catalog and proxy reference that belong in separate files are inlined, fitting 'some structure but content that should be separate is inline'.	3 / 5
	Total	14 / 20 Passed

Description

66%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 third-person, names the product and a couple of entities, and includes an explicit 'Use when' trigger, but the capability list is shallow and the trigger phrasing is a single generic clause.

Suggestions

Expand the action list beyond 'Manage Users, Organizations' to concrete operations (e.g., query MRR/churn, manage subscriptions, retrieve customer metrics) to lift specificity.

Broaden the 'Use when' clause with concrete natural triggers (e.g., 'Use when the user asks about ProfitWell MRR, churn, subscriptions, or customer lifetime value').

Dimension	Reasoning	Score
Specificity	Names the domain ('ProfitWell integration') and two concrete-ish actions ('Manage Users, Organizations'), but 'Manage' is generic and coverage is thin — matching the 'names domain and 1-2 concrete actions, but not comprehensive' anchor.	3 / 5
Completeness	It states both what ('ProfitWell integration. Manage Users, Organizations.') and when ('Use when the user wants to interact with ProfitWell data.'), but the 'when' is a single clause rather than multiple concrete trigger phrases, so it is not a 5.	4 / 5
Trigger Term Quality	'ProfitWell', 'Users', 'Organizations', and 'ProfitWell data' are relevant keywords, but synonyms and common variations are missing, fitting 'some relevant keywords but missing common variations or synonyms'.	3 / 5
Distinctiveness Conflict Risk	ProfitWell is a specific named SaaS product with a distinct trigger term, giving it a clear niche and minimal conflict risk with other skills.	5 / 5
	Total	15 / 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/profitwell/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.