Name: crowdpower
Rating: 60.8 (1 reviews)
Author: membranedev

crowdpower

CrowdPower integration. Manage Organizations, Users, Goals, Filters. Use when the user wants to interact with CrowdPower data.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/crowdpower/SKILL.md

Quality

Content

76%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 strong connection-setup workflow, and is well-structured for a single-file skill. The main gap is the absence of validation/verification steps for the batch and potentially destructive actions it lists.

Suggestions

Add a validation/verification step after running batch or destructive actions (e.g. check the `output` field, confirm created customer count, or run a follow-up `membrane action list` to verify) so workflow_clarity is not capped at 3.

Trim the crowdsourcing intro paragraph and the 'Agent Types' tangent, or move them behind a short note, to tighten conciseness.

Consider moving the Popular actions table and proxy flag reference into a separate reference file so the SKILL.md overview stays leaner.

Dimension	Reasoning	Score
Conciseness	The body is mostly a lean command reference with copy-paste CLI blocks, but includes minor over-explanation such as the crowdsourcing intro paragraph and the 'Agent Types' tangent that could be trimmed, fitting the 'efficient; minor instances of over-explanation' anchor.	4 / 5
Actionability	It provides copy-paste-ready commands for the full flow (install, login, connection ensure, action list/run, request proxy) plus a Popular actions table with keys and a concrete JSON-input example, matching the 'fully executable; covers common cases' anchor.	5 / 5
Workflow Clarity	The connection flow is well-sequenced with polling and state-based feedback loops, but the skill surfaces batch operations (e.g. 'Bulk Create Customers', 'Track') whose run workflow has no validation/verification step, so the batch-operation cap holds workflow clarity at 3.	3 / 5
Progressive Disclosure	Content is well-organized into clear headed sections with one external doc link and no nested references, but at ~158 lines with the actions table and proxy flag reference all inline it is not split across files, placing it just below the 5 anchor.	4 / 5
	Total	16 / 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, includes an explicit 'Use when' clause, and is highly distinctive thanks to the brand name. Its main weaknesses are a generic 'Manage' verb and thin trigger-term coverage beyond the brand name.

Suggestions

Replace the generic 'Manage' with specific concrete verbs (e.g. 'Create, update, and query Organizations, Users, Goals, and Filters') to raise specificity.

Broaden trigger terms beyond the brand name, e.g. 'Use when the user wants to manage CrowdPower customers, campaigns, pledges, events, charges, or tags.'

Tie the 'when' clause to the actual entities surfaced in the body (customers, events, charges, tags) so the trigger matches real user requests.

Dimension	Reasoning	Score
Specificity	Names the CrowdPower domain and four concrete entities ('Organizations, Users, Goals, Filters'), but the only action verb is the generic 'Manage' rather than multiple distinct concrete actions, matching the anchor that names the domain with limited action specificity.	3 / 5
Completeness	It states a clear 'what' ('Manage Organizations, Users, Goals, Filters') and an explicit 'when' ('Use when the user wants to interact with CrowdPower data'), but the trigger phrase is somewhat generic rather than concrete, placing it just below the 5 anchor.	4 / 5
Trigger Term Quality	The natural trigger is essentially the brand name 'CrowdPower' plus 'CrowdPower data'; relevant but missing common variations or synonyms users might say, fitting the 'some relevant keywords but missing variations' anchor rather than the 4 with good coverage.	3 / 5
Distinctiveness Conflict Risk	The 'CrowdPower' brand name gives it a clear niche with a distinct trigger and minimal overlap risk with other skills, matching the 'clear niche with distinct triggers' anchor.	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/crowdpower/SKILL.md
Commit: f484c82

Reviewed: ~15 hours 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.