Name: wicked-reports
Rating: 58.4 (1 reviews)
Author: membranedev

wicked-reports

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

Quality

68%

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

Quality

Content

75%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 concrete commands and a solid connection workflow, losing points mainly to a verbose intro and dangling step references. It is well-structured for a single-file CLI skill.

Suggestions

Trim the opening product-description paragraph and remove editorializing ("so you can focus on...", "burn less tokens") to tighten conciseness.

Label the connection steps explicitly (Step 1, Step 2) so the "skip to Step 2" references resolve, clarifying the workflow sequence.

Consider moving the proxy flags table and clientAction field breakdown into a short reference file to improve progressive disclosure for the >50-line body.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient commands, but the three-sentence product intro and editorializing like "so you can focus on the integration logic rather than auth plumbing" add unnecessary explanation, matching anchor 3 rather than the trimmed anchor 4.	3 / 5
Actionability	It provides copy-paste-ready commands for every common case (install, login, connection ensure/get, action list/run, request) plus a complete proxy-flags table, matching anchor 5.	5 / 5
Workflow Clarity	The connection flow has explicit state checks and a poll-after-user-action feedback loop, but "skip to Step 2" references dangle without labeled Step 1/Step 2 headings, leaving minor gaps at anchor 4 rather than 5.	4 / 5
Progressive Disclosure	Content is well-organized into clearly labeled sections with no nested references, and inline material (flags table, clientAction fields) is reasonable for a CLI guide; it stays at 4 because the >50-line body has no external references to signal.	4 / 5
	Total	16 / 20 Passed

Description

61%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 pairs an explicit "Use when" trigger with a named-product niche, but its capability statement is generic and its trigger vocabulary is narrow. Strengthening the concrete actions and adding common user phrasings would lift the weaker dimensions.

Suggestions

Replace generic verbs with concrete Wicked Reports operations (e.g. "Pull attribution reports, sync leads and sales, track ROI by source") to raise specificity.

Expand the "Use when" clause with natural user phrasings like "marketing attribution", "ROI by campaign", or "lead/source tracking" to improve trigger-term coverage.

Tighten the "what" so it reads as specific capabilities rather than "Manage data, records, and automate workflows".

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the domain but relies on generic verbs ("manage", "automate") rather than concrete actions, matching anchor 2; it does not reach 3 because no specific operations are enumerated.	2 / 5
Completeness	It states a "what" ("Wicked Reports integration. Manage data, records, and automate workflows.") and an explicit "Use when..." clause, but the trigger could be more specific, matching anchor 4 rather than the fully explicit anchor 5.	4 / 5
Trigger Term Quality	"Wicked Reports" and "interact with Wicked Reports data" are natural triggers, but coverage lacks common variations users might say (e.g. marketing attribution, ROI, leads), so it sits at anchor 3 rather than 4.	3 / 5
Distinctiveness Conflict Risk	The trigger is anchored to a named product ("Wicked Reports"), giving it a clear niche with minimal conflict risk, matching anchor 5.	5 / 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/wicked-reports/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.