task

Create, list, and complete tasks in a persistent JSON file.

Updated Jan 24, 2026
One-click install
npx skills add https://github.com/jamiegrand/cleo-web --skill task-jamiegrand
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task
Source: https://github.com/jamiegrand/cleo-web/tree/main/.claude/skills/task
Command: npx skills add https://github.com/jamiegrand/cleo-web --skill task-jamiegrand

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Task management in software projects often becomes scattered across notes and emails, making progress hard to track. This Skill provides a minimal, persistent store at .cleo-web/todo.json to coordinate tasks across sessions.

Core Features & Use Cases

  • Create tasks with unique IDs and titles, saved atomically to a local JSON file.
  • List tasks grouped by status (active, pending, done) for a quick status overview.
  • Mark tasks as complete with timestamps, preserving history and enabling basic audit trails.
  • Use Case: A developer assigns onboarding, bug triage, and feature work as tasks and monitors progress within a single, reusable workflow.

Quick Start

Add a new task with a concise title using /task add "Example task" to create and persist it in the local .cleo-web/todo.json.

Frequently Asked Questions about task

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I persist todo tasks in a local JSON file for software project workflows?

You can persist todo tasks by adding items to a local JSON store, which enforces deterministic file writes and safe updates to maintain task state across sessions.

What is the best way to track project workflow tasks locally without a database?

Tracking project workflow tasks locally is done through a persistent JSON file that organizes items by status, assigns unique IDs, and records completion timestamps for basic audit trails.

How do I list and complete tasks stored in a JSON file using a CLI?

To list and complete tasks in a JSON file via CLI, you use commands to group items by active, pending, or done status, and mark items complete with validated task IDs and timestamps.

Can I use a local JSON file for task management across multiple sessions?

Yes, you can use a local JSON file for task management across multiple sessions because the store applies atomic saves and persistent state, ensuring your todo items survive session restarts.

Does organizing task items in a JSON store validate task IDs?

Organizing task items in a JSON store does validate task IDs, enforcing safe updates and deterministic file writes to prevent data corruption when creating or completing tasks.

When should I avoid using a JSON file for project task management?

You should avoid using a JSON file for project task management when your workflow requires concurrent multi-user collaboration, as the local store is designed for single-user persistent state rather than distributed access.