wrike-automation
Automate Wrike Project Workflows
Manual Wrike updates can slow project coordination and create inconsistent records. This skill guides Rube MCP tools for structured task, project, and workspace operations.
Stop for confirmation before installing.
Review the plan and obtain explicit user consent before changing files.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "wrike-automation" from https://skillstore.io/skills/sickn33-wrike-automation.md and its manifest at https://skillstore.io/api/skills/sickn33-wrike-automation/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "wrike-automation". List active tasks due this week in the Website Launch project.
Expected outcome:
- Found 8 active tasks due this week in Website Launch.
- Three tasks are due within two days, and two tasks have no assignee.
- Results include task title, assignee, start date, due date, and status.
Using "wrike-automation". Create a high-priority design review task for Maya due Friday.
Expected outcome:
Created Design review in the approved project, assigned it to Maya, set high importance, and scheduled the requested due date.
Using "wrike-automation". Delete the obsolete Campaign Archive folder.
Expected outcome:
Campaign Archive contains 14 tasks and 3 subfolders. Permanent deletion is pending explicit confirmation for the resolved folder identifier.
Security Audit
High RiskThe backtick and reconnaissance detections are false positives caused by Markdown formatting and ordinary Wrike documentation. Real risks remain from third-party OAuth delegation and irreversible deletion workflows that lack mandatory confirmation.
Confirmed security concerns (2)
Capability review items (1)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Risk Factors
⚙️ External commands (50)
🌐 Network access (1)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/sickn33-wrike-automation/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-wrike-automation?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-wrike-automation?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-wrike-automation/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-wrike-automation.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
sickn33. (2026). wrike-automation security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-wrike-automation/audits/5BibTeX citation
@techreport{sickn33-sickn33-wrike-automation-2026,
author = {sickn33},
title = {wrike-automation security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/sickn33-wrike-automation/audits/5},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "wrike-automation security audit report (audit version 5)"
version: "unspecified"
type: report
authors:
- name: "sickn33"
date-released: "2026-09-07"
url: "https://skillstore.io/skills/sickn33-wrike-automation/audits/5"
identifiers:
- type: other
value: "skillstore:sickn33-wrike-automation:audit:5"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Coordinate Team Tasks
Create assigned tasks with dates, status, importance, and custom fields inside the correct Wrike project.
Monitor Delivery Progress
Retrieve active or overdue tasks, resolve assignee names, and summarize current work across selected folders.
Standardize Repeated Projects
Find a task blueprint and launch a rescheduled copy in the required folder or parent task.
Try These Prompts
List active Wrike tasks in [folder or project]. Include title, assignee, start date, due date, and status.
Create a Wrike task named [title] in [project]. Assign [people], set dates to [dates], and show the resolved destination before creation.
Find the Wrike blueprint named [name]. Launch it under [project] with title [title] and reschedule its start to [date].
Find overdue active tasks in [scope]. Group them by assignee, propose status or date changes, and request approval before applying updates.
Best Practices
- Search current tool schemas before each workflow because MCP tool parameters can change.
- Resolve folders, users, custom fields, and blueprints by lookup instead of guessing identifiers.
- Confirm resolved resources and impact before invitations, bulk updates, blueprint launches, or deletions.
Avoid
- Do not guess Wrike identifiers from names or reuse identifiers from another workspace.
- Do not delete folders or spaces without reviewing their contents and obtaining explicit approval.
- Do not assume all records were returned when a tool response includes pagination.