← Back to Skills Marketplace
644
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install wrike
Description
Manage Wrike tasks, projects, folders, and comments via the Wrike REST API.
Usage Guidance
This skill appears coherent for controlling Wrike via a CLI and only needs a Wrike API token. Before installing: verify the npm package 'claw-wrike' is the expected/official package (check npmjs.com, package maintainers, release history, and source repository); inspect the package contents or repository (install scripts, postinstall hooks) if you can; prefer creating a token with least privilege and rotate/revoke it if needed; check that ~/.claw-wrike/config.json is created with safe file permissions and that the CLI masks tokens when showing config; and consider running the CLI in a least-privilege environment or container if you are unsure of package provenance.
Capability Analysis
Type: OpenClaw Skill
Name: wrike
Version: 0.1.0
The skill bundle is designed to manage Wrike tasks and projects via the `claw-wrike` CLI tool. The `SKILL.md` file provides clear instructions for the AI agent, including installation of `claw-wrike` via npm and handling of the `WRIKE_TOKEN`. Crucially, it includes explicit 'NEVER' instructions to guide the agent towards safe and responsible behavior (e.g., 'Never bulk-modify tasks without user confirmation'), which acts as a defense against prompt injection and indicates a lack of malicious intent. There is no evidence of data exfiltration, unauthorized execution, persistence, or other malicious activities within the provided files. The capabilities are aligned with the stated purpose of managing Wrike resources.
Capability Assessment
Purpose & Capability
The skill is named 'Wrike' and documents a Wrike CLI (claw-wrike) that uses a WRIKE_TOKEN. Required binary (claw-wrike), primary env var (WRIKE_TOKEN), and the documented commands align with the described purpose.
Instruction Scope
SKILL.md only instructs using the claw-wrike CLI against the Wrike REST API and references storing the token in ~/.claw-wrike/config.json. It does not ask the agent to read unrelated system files, other env vars, or send data to unexpected endpoints.
Install Mechanism
Install is via npm package 'claw-wrike' which is a reasonable choice for a Node CLI but carries the usual npm risks: install-time scripts can execute arbitrary code and the registry/package provenance is not provided in the metadata. The install spec is not a remote URL extract and looks proportional to the task.
Credentials
Only a single credential (WRIKE_TOKEN) is required and declared as the primary credential. That is appropriate for a Wrike integration; no unrelated secrets or config paths are requested.
Persistence & Privilege
always:false (no forced-permanent inclusion). The skill stores token in its own config path (~/.claw-wrike/config.json) per instructions, which is consistent with CLI behavior and does not request elevated or cross-skill privileges.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install wrike - After installation, invoke the skill by name or use
/wrike - Provide required inputs per the skill's parameter spec and get structured output
Version History
v0.1.0
Initial release
Metadata
Frequently Asked Questions
What is Wrike?
Manage Wrike tasks, projects, folders, and comments via the Wrike REST API. It is an AI Agent Skill for Claude Code / OpenClaw, with 644 downloads so far.
How do I install Wrike?
Run "/install wrike" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Wrike free?
Yes, Wrike is completely free (open-source). You can download, install and use it at no cost.
Which platforms does Wrike support?
Wrike is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Wrike?
It is built and maintained by tallhamn (@tallhamn); the current version is v0.1.0.
More Skills