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

Blog Docs Log in Get started

woopra

Woopra integration. Manage data, records, and automate workflows. Use when the user wants to interact with Woopra 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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/woopra/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 actionable and well-structured with a solid connection workflow, but it carries some redundant/padded explanation and lacks validation checkpoints for destructive proxy and action operations. Splitting detailed reference material and adding pre-flight verification would improve it.

Suggestions

Add a validation/verification checkpoint before destructive proxy or action calls (e.g. "For -X DELETE or mutating actions, confirm the target with the user first and re-fetch to verify the result").

De-duplicate the `action list` example by merging "Searching for actions" and "Popular actions" into one section, and trim the introductory Woopra paragraph to one line.

Move the detailed connection-state / clientAction field reference into a separate references file and link to it, keeping the body a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly operational, but the introductory "Woopra is a customer journey analytics platform..." paragraph explains context Claude largely already knows, and the `action list --intent=QUERY` example is repeated across both "Searching for actions" and "Popular actions", so it could be tightened.	3 / 5
Actionability	It provides concrete, executable commands throughout (npm install, membrane login, connection ensure, action run, and a proxy flag table), but relies on placeholders like <actionId> and dynamic discovery rather than showing concrete Woopra-specific action examples, leaving minor gaps.	4 / 5
Workflow Clarity	The connection state machine has clear checkpoints and a poll-after-client-action feedback loop, but the skill enables destructive operations (proxy DELETE, action run on data) with no validation/verification step, so the destructive-operations cap holds it at 3.	3 / 5
Progressive Disclosure	There are no bundle files; the single SKILL.md is well-organized with clear section headers and no nested references, but minor organization gaps (section redundancy between "Searching for actions" and "Popular actions") keep it just below 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 answers both what and when with an explicit Use-when clause and is distinct via the Woopra product name, but its action verbs and trigger terms are generic, limiting specificity and keyword coverage. Tightening the actions and adding concrete Woopra concepts would raise the score.

Suggestions

Replace generic verbs with concrete Woopra actions, e.g. "query reports, build funnels, segment users, and manage user profiles".

Expand the trigger to list natural phrases users say, e.g. "Use when the user mentions Woopra, customer journey analytics, funnels, segmentation, or Woopra reports."

Drop filler like "Woopra integration." as a standalone sentence and fold it into the action list to increase density.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Woopra domain plus a few actions, but the verbs ("Manage", "automate") are generic rather than concrete, matching the 1-2-concrete-actions anchor without being comprehensive.	3 / 5
Completeness	Both a "what" (Woopra integration, manage data/records, automate workflows) and an explicit "Use when the user wants to interact with Woopra data" trigger are present, but the when-clause is generic rather than listing concrete trigger phrases, so it is not a 5.	4 / 5
Trigger Term Quality	The only natural keyword is "Woopra" / "Woopra data"; related terms a user might actually say (analytics, customer journey, reports, funnels, tracking) are absent, leaving coverage at the some-keywords-but-missing-variations anchor.	3 / 5
Distinctiveness Conflict Risk	The "Woopra" proper noun gives a clear niche with low conflict risk, but the generic "Manage data... automate workflows" phrasing creates minor overlap with other integration skills, keeping it just below the minimal-conflict anchor.	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/woopra/SKILL.md
Commit: f484c82

Reviewed: 3 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.