SKILLEMALL.ai
GitHub ↗ RU Sign in

AC wrike

Wrike API integration with managed OAuth. Manage tasks, folders, projects, spaces, and team collaboration. Use this skill when users want to manage project work, track tasks, handle time logs, or access team resources in Wrike. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Requires network access and valid Maton API key.

LeoYeAI/openclaw-master-skills Agent Skills author: LeoYeAI MIT 3 files body ≈ 5 787 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Wrike API integration with managed OAuth.

As a process C 52/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, consistency

IntegrationSoftware developmenttype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
A
91/100
safety, quality, tests
Safety 60%
100
Quality 40%
78
Run on models
none yet
Process rating
C
52/100
Has gaps
Inputs and preconditions w 11
0
When it triggers w 12
20
Running it twice w 4
30
the three weakest of ten parameters · all ten

How to improve

  1. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning body-long SKILL.md body ≈ 5787 tokens (recommended < 5000); move details to references/

Process rating: all ten parameters 52/100

  • 0Inputs and preconditions. Does not say what the process needs to start
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 25 mutating operations with no state check
  • 40Consistency. Frontmatter name (wrike) differs from the folder (wrike-api)
  • 50Failures and branches. 0 branches, has a failure section
  • 60Tools and files. Uses tools (bash, web, python) that frontmatter does not declare
  • 60Result and completion. Output format stated, no completion criterion
  • 70Execution cost. Instruction body is 5787 tokens
  • 100Steps. 18 steps
  • 100Progress reporting. Reports progress
  • low 11 top-level sections: this looks like several domains in one skill

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +2Single-language instructions
  • +3Description length 373: enough signal without eating the budget
  • +4Structure: 108 headings
  • +3Step-by-step instructions: 18 items
  • +3Output format is stated explicitly
  • +4Has examples (102 code blocks)
  • +1License stated

Quality base 70; lint remarks subtract, signals add up to 100. Result: 78.