Name: wrike
Rating: 64.8 (1 reviews)
Author: membranedev

wrike

Wrike integration. Manage Users, Organizations, Projects, Tasks, Folders, Spaces and more. Use when the user wants to interact with Wrike data.

Quality

77%

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/wrike/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.

A lean, highly actionable CLI skill body with strong executable commands and a well-validated connection state-machine. Its main gap is the absence of validation/verification guidance around destructive operations (delete-task), which limits workflow clarity.

Suggestions

Add a validation/verification step for destructive operations, e.g., confirm with the user before running delete-task and verify the result afterward (e.g., re-list tasks) to establish a feedback loop and lift workflow clarity above 3.

Fix the dangling "skip to Step 2" reference and the orphaned "1b" subheading by adding explicit Step 1 / Step 2 labels so the connection workflow sequence is unambiguous.

Trim the Membrane-internals paragraph ("The URL is normalized to a domain and matched against known apps. If no app is found, one is created and a connector is built automatically.") and the token-burning meta-commentary to tighten conciseness toward 5.

Dimension	Reasoning	Score
Conciseness	Mostly efficient command-driven content that assumes Claude's competence, with minor over-explanation such as the Membrane internals paragraph ("The URL is normalized to a domain and matched against known apps...") and the meta best-practice note about burning tokens.	4 / 5
Actionability	Fully executable, copy-paste-ready commands cover the common cases end-to-end (install, login, connection ensure/get, action list/run with --input, request proxy) plus a 20-row popular-actions table with concrete keys.	5 / 5
Workflow Clarity	The connection setup has a clear sequence with explicit state validation and a poll-after-action feedback loop, but the destructive delete-task action is listed and runnable with no validation/verification guidance, which caps workflow clarity at 3 per the destructive-operations rule.	3 / 5
Progressive Disclosure	Well-organized into clear sections (Install, Authentication, Connecting, Searching, Popular actions, Running, Proxy, Best practices) with no nested references; the inline popular-actions table is a minor organization gap but acceptable for a single-file CLI skill.	4 / 5
	Total	16 / 20 Passed

Description

78%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 a clear niche (Wrike), enumerates concrete managed objects, and includes an explicit "Use when" trigger. The main weakness is the single generic verb "Manage" and a one-phrase trigger rather than a richer set of trigger terms.

Suggestions

Replace the repeated generic verb "Manage" with a few distinct concrete actions (e.g., "Create, update, list, and delete Tasks, Folders, and Spaces") to lift specificity toward a 5.

Expand the "Use when" clause with multiple concrete trigger phrases (e.g., "Use when the user mentions Wrike tasks, projects, folders, or spaces, or wants to manage work in Wrike") to push completeness to 5.

Drop the trailing "and more" or replace it with the remaining entities, since it signals coverage gaps without adding trigger value.

Dimension	Reasoning	Score
Specificity	Lists several concrete managed entities ("Users, Organizations, Projects, Tasks, Folders, Spaces") which read as specific capabilities, though the single generic verb "Manage" and the trailing "and more" leave minor coverage gaps.	4 / 5
Completeness	Both "what" ("Wrike integration. Manage Users, Organizations, Projects, Tasks, Folders, Spaces") and "when" ("Use when the user wants to interact with Wrike data") are explicit, but the when-clause names a single trigger rather than several concrete trigger phrases.	4 / 5
Trigger Term Quality	Good coverage of natural Wrike object names users would say (tasks, projects, folders, spaces) plus the trigger "interact with Wrike data", though a few common synonyms/phrasings are missing.	4 / 5
Distinctiveness Conflict Risk	"Wrike integration" targets a specific branded product with distinct triggers ("interact with Wrike data"), giving a clear niche and minimal conflict risk with other skills.	5 / 5
	Total	17 / 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/wrike/SKILL.md
Commit: f484c82

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