Name: wrike-automation
Rating: 56.00000000000001 (1 reviews)
Author: administrakt0r

wrike-automation

Automate Wrike project management via Rube MCP (Composio): create tasks/folders, manage projects, assign work, and track progress. Always search tools first for current schemas.

Quality

63%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/wrike-automation/SKILL.md

The canonical home for this skill is wrike-automation in administrakt0r/AI-Agents-Safe-Coding-Skills

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 content is highly actionable, with concrete tool sequences, parameters, and pitfalls for Wrike automation. Its weaknesses are duplicated pitfall content, missing validation checkpoints before destructive deletions, and a monolithic structure with no progressive file disclosure.

Suggestions

Add an explicit validation/confirmation checkpoint before destructive steps (e.g. 'Before DELETE_FOLDER, confirm the folder ID and warn that deletion is permanent; prefer MODIFY_FOLDER to move to recycle bin').

Deduplicate pitfalls — keep them in one place (either per-workflow or under 'Known Pitfalls', not both) and consider moving the Quick Reference table and full parameter dumps into a references file.

Dimension	Reasoning	Score
Conciseness	The body is information-dense and avoids explaining concepts Claude already knows, but pitfalls are duplicated (inline per workflow and again under 'Known Pitfalls'), the Quick Reference table repeats workflow content, and the 'When to Use' line is filler — so it could be tightened, fitting the 'mostly efficient' 3 rather than the lean 4.	3 / 5
Actionability	Provides concrete, numbered tool sequences (WRIKE_CREATE_TASK etc.) with key parameters, types, and formats (YYYY-MM-DD, ID format), giving mostly executable guidance with only minor gaps such as no fully assembled example call.	4 / 5
Workflow Clarity	Sequences are clearly numbered with [Required]/[Optional]/[Prerequisite] markers, but destructive operations (DELETE_FOLDER, DELETE_SPACE) have no validation/confirmation checkpoint in the workflow steps, which caps workflow_clarity at 3 per the destructive-operation guideline.	3 / 5
Progressive Disclosure	The file is well-sectioned but fully monolithic at ~230 lines with no bundle files or external references, and reference material (the Quick Reference table, full parameter dumps) that could live in a separate file is inlined, fitting the 'could be better organized' 3.	3 / 5
	Total	13 / 20 Passed

Description

70%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 specific and clearly scoped to Wrike automation via Rube MCP, with concrete actions and good trigger keywords. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which caps completeness.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants to manage Wrike tasks, folders, projects, assignments, or task blueprints.'

Replace the procedural trailing sentence ('Always search tools first for current schemas') with trigger guidance or fold it into the body, since it does not serve as a 'when to use' signal.

Dimension	Reasoning	Score
Specificity	Names the domain (Wrike project management via Rube MCP/Composio) and lists several concrete actions — 'create tasks/folders, manage projects, assign work, and track progress' — with only minor coverage gaps, fitting the 'several specific actions' anchor rather than the fully comprehensive 5.	4 / 5
Completeness	It has a clear 'what' (create/manage/assign/track) but no 'Use when...' clause or equivalent explicit trigger guidance — the trailing 'Always search tools first for current schemas' is procedural, not a trigger — so completeness is capped at 3 per the missing-trigger guideline.	3 / 5
Trigger Term Quality	Includes natural terms users would say ('Wrike', 'tasks', 'folders', 'projects', 'assign work', 'track progress'); a few natural synonyms (e.g. 'to-dos', 'Gantt') are missing, so it sits just below the comprehensive 5.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche ('Wrike project management via Rube MCP (Composio)') with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	16 / 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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/wrike-automation/SKILL.md
Commit: 57c135b

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