task-test
npx machina-cli add skill martinemde/skillet/task-test --openclawTask System Test Skill
This skill exercises the Task tool system. You MUST use TaskCreate, TaskUpdate, and TaskList to manage tasks. Set awn owner for the tasks to "haiku".
Instructions
Step 1: Create tasks IN PARALLEL (all three TaskCreate calls in one response):
- TaskCreate: subject="List Go files", description="Count the number of *.go files", activeForm="Listing Go files"
- TaskCreate: subject="Check formatting", description="Run go fmt on all the files", activeForm="Checking formatting"
- TaskCreate: subject="Count lines", description="Count # of lines in *.go files", activeForm="Counting lines"
Step 2: List tasks to see what was created.
Step 3: Complete each task
Summarize results.
Source
git clone https://github.com/martinemde/skillet/blob/main/.claude/skills/task-test/SKILL.mdView on GitHub Overview
This skill exercises the Task tool system by creating three tasks in parallel, listing them, and then completing each one. It uses TaskCreate, TaskUpdate, and TaskList with the owner set to haiku. It's designed to validate task lifecycle and ownership propagation in a controlled test flow.
How This Skill Works
Step 1 creates three tasks in parallel using TaskCreate with specific subjects, descriptions, and activeForm values. Step 2 uses TaskList to verify the created tasks. Step 3 completes each task via TaskUpdate and then summarizes the results to confirm successful creation and completion.
When to Use It
- When validating Task tool integration and permissions
- When testing parallel task creation and ownership assignment
- When verifying task lifecycle from creation to completion
- When debugging TaskList output and task visibility
- When performing regression tests for task-related features
Quick Start
- Step 1: Create three tasks in parallel using TaskCreate with the provided subjects, descriptions, and activeForm values, setting owner to haiku
- Step 2: Run TaskList to view all created tasks and confirm their presence and initial states
- Step 3: Update each task with TaskUpdate to mark them complete, then summarize results
Best Practices
- Always create all tasks in parallel in a single response as specified
- Ensure the owner is consistently set to haiku for all created tasks
- Verify TaskList reflects all newly created tasks before proceeding
- Use TaskUpdate to mark tasks as complete and verify status changes
- Summarize results clearly to confirm successful creation and completion
Example Use Cases
- QA: verify end-to-end task lifecycle in the Task tool integration
- Demo: illustrate parallel task creation with distinct subjects and forms
- Automation: smoke test for TaskCreate, TaskList, and TaskUpdate interactions
- Onboarding: show how tasks can be created and completed programmatically
- Regression: ensure ownership and status updates remain consistent after changes
