CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

71%

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/wrike-automation/SKILL.md
SKILL.md
Quality
Evals
Security

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.

A well-structured, highly actionable MCP tool reference with concrete tool sequences, parameters, and pitfalls for every workflow. Its weaknesses are notable redundancy across sections (pitfalls repeated, a duplicative summary table) and the absence of validation/confirmation steps before the documented destructive delete operations.

Suggestions

Add an explicit verification step before destructive operations, e.g., 'Before DELETE_FOLDER/DELETE_SPACE: list contents (WRIKE_GET_FOLDERS / WRIKE_GET_SPACE), confirm scope with the user, and prefer the recycle-bin path (MODIFY_FOLDER) unless permanent deletion is explicitly requested.'

De-duplicate the deletion and date-format pitfalls that currently appear in both the per-workflow 'Pitfalls' blocks and the 'Known Pitfalls' section, and drop the Quick Reference rows that fully restate workflow parameters.

Include one or two example tool-call payloads (e.g., a WRIKE_CREATE_TASK body with folderId, title, responsibles) to make the guidance copy-paste ready.

DimensionReasoningScore

Conciseness

The body is a dense, Wrike-specific reference with no filler explaining concepts Claude already knows, but it has real redundancy: deletion warnings appear in both the folder-workflow pitfalls and the 'Known Pitfalls' section, the date format is stated three times, and the Quick Reference table restates the workflow sections. This fits anchor 3 ('mostly efficient but could be tightened') rather than 4, whose over-explanation would be only minor, and not 2 since nothing is generic padding.

3 / 5

Actionability

Concrete, executable guidance throughout: exact tool slugs ('WRIKE_CREATE_TASK'), parameter names ('folderId', 'responsibles'), enum values ("'Active', 'Completed', 'Deferred', 'Cancelled'"), and formats ('YYYY-MM-DD'). It falls short of anchor 5 only because there are no example tool-call payloads showing an actual invocation, and it is clearly above anchor 3's pseudocode level.

4 / 5

Workflow Clarity

Sequences are well-labeled ([Prerequisite]/[Required]/[Optional]) and setup includes a checkpoint ('Confirm connection status shows ACTIVE'), but the skill involves destructive operations (DELETE_FOLDER 'removes ALL contents permanently', DELETE_SPACE 'is irreversible') with no verification or confirmation step before deletion. Per the rubric, missing validation steps in destructive/batch workflows caps workflow clarity at 3.

3 / 5

Progressive Disclosure

No bundle files exist, and the single-file body is well-organized with clear section headers, per-workflow structure, and a Quick Reference table for navigation. This fits anchor 4 ('good structure, minor organization gaps') rather than 5 because all parameter detail is inlined in one ~230-line file instead of an overview plus one-level-deep reference files.

4 / 5

Total

14

/

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.

A strong, specific description that clearly conveys what the skill does and is well-differentiated by naming Wrike, Rube MCP, and Composio. Its main weakness is the complete absence of a 'when to use' trigger clause, which caps completeness and weakens trigger-term quality.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user mentions Wrike, or wants to create/assign/track project tasks and folders in Wrike.'

Include natural trigger variations users would say, such as 'Wrike task', 'Wrike project', 'to-dos', and 'due dates', to broaden trigger-term coverage.

Replace the generic phrase 'manage projects' with a concrete action like 'create projects from folders' to match the skill's actual capability set.

DimensionReasoningScore

Specificity

The description lists several concrete actions ('create tasks/folders, manage projects, assign work, and track progress') plus a concrete behavioral rule ('Always search tools first for current schemas'), but 'manage projects' and 'track progress' are generic, leaving minor coverage gaps. It matches anchor 4 rather than 5 because its actions are not as uniformly specific as the 5 example, and not 3 because it clearly goes beyond 1-2 actions.

4 / 5

Completeness

The 'what' is clear and multi-action ('Automate Wrike project management... create tasks/folders, assign work, track progress'), but there is no 'Use when...' clause or equivalent explicit trigger guidance — 'Always search tools first for current schemas' is procedural, not a when-trigger. Per the rubric guideline, a missing 'Use when...' clause caps completeness at 3.

3 / 5

Trigger Term Quality

Natural user terms are present ('Wrike', 'tasks', 'folders', 'assign', 'project management'), giving good keyword coverage, but common variations and trigger phrasing (e.g., 'when the user mentions Wrike tasks') are missing. Anchor 5 requires comprehensive synonyms and variations, which this lacks, while coverage is too strong for anchor 3.

4 / 5

Distinctiveness Conflict Risk

The description names a clear niche ('Wrike project management via Rube MCP (Composio)') with distinct triggers tied to the Wrike platform, giving minimal conflict risk with other skills. This matches anchor 5; the domain-specific product name prevents overlap with generic project-management or document skills.

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

Validation — 15 / 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

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

skills/wrike-automation/SKILL.md

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.