CD yatta
Personal productivity system for task and capacity management. Create and organize tasks with rich attributes (priority, effort, complexity, tags), track time and streaks, manage capacity across projects and contexts, view Eisenhower Matrix prioritization, sync calendar subscriptions, handle delegation and follow-ups, and get AI-powered insights. Supports batch operations, multi-project workflows, and real-time capacity planning to prevent overcommitment. Security: v0.2.0 eliminates RCE vulnerability from v0.1.3 (shell/JSON injection in examples), adds endpoint verification, safe jq patterns throughout.
Personal productivity system for task and capacity management.
As a process D 49/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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 · 14
✓ No critical or high findings
Medium and low: 14
-
low Risky intent
intent-offensive-securitySECURITY-ASSESSMENT-ISSUE-15.md:106Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- No privilege escalation
-
low Risky intent
intent-offensive-securitySECURITY-ASSESSMENT-ISSUE-16.md:262Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- No privilege escalation
-
low Risky intent
intent-offensive-securitySECURITY-ASSESSMENT-ISSUE-17.md:258Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- No privilege escalation
-
low Risky intent
intent-offensive-securitySECURITY-ASSESSMENT-v0.2.0.md:139Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- No privilege escalation
-
low Risky intent
intent-offensive-securitySECURITY-ASSESSMENT-v0.2.0.md:449Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- No privilege escalation
-
low Risky intent
intent-offensive-securitySECURITY.md:137Offensive-security / dual-use content (legitimate for authorised testing; review intended use)### Example 3: Privilege Escalation
A further 8 matches are quotations in this security skill's documentation and are not counted as findings.
Files scanned: 15. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Personal productivity system for task and capacity management. Cre… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
body-longSKILL.md body ≈ 6109 tokens (recommended < 5000); move details to references/ - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 49/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 26 mutating operations with no state check
- 40Consistency. Frontmatter name (yatta) differs from the folder (openclaw-yatta-skill)
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 70Execution cost. Instruction body is 6109 tokens
- 100Steps. 96 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Progress reporting. Reports progress
- low 18 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)
- +3Output format is not stated: the model decides each time
- -5TODO / placeholder text left in the skill
- -213 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 610: enough signal without eating the budget
- +4Structure: 69 headings
- +3Step-by-step instructions: 96 items
- +4Has examples (60 code blocks)
- +3All 2 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 47.