AB taskify-cli
Manage tasks, boards, and calendar events via the Taskify CLI (`taskify` command). Use when: (1) listing, searching, creating, updating, or deleting tasks, (2) marking tasks done or reopening them, (3) managing boards and columns, (4) assigning tasks to users, (5) checking upcoming or overdue tasks, (6) exporting or importing tasks, (7) triage or AI-powered task creation. Taskify stores tasks on Nostr relays — the CLI is the primary interface for agents working with Taskify data.
As a process B 69/100 · Nearly there — weak spots: running it twice, progress reporting
How to improve
- 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: 4. 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: Manage tasks, boards, and calendar events via the Taskify CLI (`ta… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
Process rating: all ten parameters 69/100
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 2 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 55Failures and branches. 1 branches
- 60Tools and files. Uses tools (web, node) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 14 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1445 tokens
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)
- +1No license
- +2Single-language instructions
- +3Description length 484: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 14 items
- +3Output format is stated explicitly
- +4Has examples (13 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 81.