CtrlK
BlogDocsLog inGet started
Tessl Logo

piwik-pro

Piwik Pro integration. Manage data, records, and automate workflows. Use when the user wants to interact with Piwik Pro data.

57

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/piwik-pro/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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 actionable and well-structured with concrete CLI examples and state-handling guidance, but it mixes in background explanation Claude does not need, leaves a dangling 'Step 2' reference, and omits validation checkpoints for batch/destructive operations.

Suggestions

Remove or compress the Piwik PRO marketing/analytics background and Membrane-auth explanation that Claude can infer, and trim the nested admin-entity catalog unless it drives action selection.

Label 'Step 2' explicitly (or drop the step references) so the connection-to-action workflow is unambiguous.

Add explicit validation/verification steps for destructive or batch operations (e.g. checking action output before acting, confirming proxy request results) to lift workflow clarity past the validation cap.

DimensionReasoningScore

Conciseness

Mostly efficient with executable command blocks, but it includes explanations of concepts Claude already knows (what Piwik PRO is, that Membrane 'handles authentication and credentials refresh automatically') and the long nested overview list of admin entities adds length without action guidance.

3 / 5

Actionability

Provides concrete, copy-pasteable CLI commands with flags and a clear options table covering the common cases, with only minor gaps such as placeholder handling for CONNECTION_ID.

4 / 5

Workflow Clarity

The connection flow is sequenced with state checks and polling, but batch/destructive operations like 'action run' and proxy requests lack explicit validation or verification checkpoints, and the step numbering is inconsistent (references 'Step 2' that is not labeled).

3 / 5

Progressive Disclosure

Well-organized into clear sections (Overview, Connecting, Searching, Running actions, Proxy, Best practices) with no bundle files needed; minor gaps are the inlined admin-entity catalog and a 'Popular actions' section that largely repeats the preceding 'Searching for actions' guidance.

4 / 5

Total

14

/

20

Passed

Description

75%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.

A solid description that states the domain, concrete capabilities, and an explicit 'Use when' trigger, all in third person. It is concise and distinct, with only minor gaps in trigger-phrase comprehensiveness.

DimensionReasoningScore

Specificity

Names the Piwik Pro domain plus three concrete actions ('Manage data, records, and automate workflows'), but the verbs are fairly generic and lack the granularity of comprehensive coverage, so it sits above the 1-2-action anchor but below fully comprehensive.

4 / 5

Completeness

Explicitly states both what it does ('Manage data, records, and automate workflows') and when to use it ('Use when the user wants to interact with Piwik Pro data'), but the 'when' clause is somewhat general rather than concrete trigger phrases.

4 / 5

Trigger Term Quality

Includes natural phrases like 'interact with Piwik Pro data' and 'Manage data, records', giving good keyword coverage, though it lacks synonyms or file extensions that would push it to comprehensive.

4 / 5

Distinctiveness Conflict Risk

The Piwik Pro niche is clearly named and triggers are product-specific, so it is mostly distinct with only minor overlap risk against generic analytics skills.

4 / 5

Total

16

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
Reviewed

Table of Contents

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.