task

Create and schedule recurring YAML-defined tasks in a Claude Code workspace.

26|4|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/kid0317/cc_workspace_bot --skill task-kid0317
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task
Source: https://github.com/kid0317/cc_workspace_bot/tree/main/workspaces/_template/.claude/skills/task
Command: npx skills add https://github.com/kid0317/cc_workspace_bot --skill task-kid0317

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates turning user requests into scheduled, YAML-defined tasks inside a Claude Code workspace, eliminating manual setup for recurring workflows.

Core Features & Use Cases

  • Create and persist recurring tasks by writing YAML files to a designated tasks directory, each with a UUID filename.
  • Support common scheduling patterns via cron expressions and enable/disable switches to control execution.
  • Use case: a daily briefing or weekly report is generated automatically without manual intervention, synchronized with the current app context.

Quick Start

Write a YAML file under the tasks_dir with a new UUID to define a scheduled task and enable it for the current app.

Frequently Asked Questions about task

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

FAQPage Schema
How do I automate recurring tasks in a Claude Code workspace?

You can automate recurring tasks by writing YAML files to a designated tasks directory. Each file uses a UUID filename and defines a cron-based schedule, which the controller registers to execute workflows like daily briefs automatically.

Can I use cron expressions to schedule workspace reports with YAML?

Yes, cron expressions define the execution schedule for YAML task files. You set the cron pattern inside the YAML schema and use an enable switch to activate or pause the recurring task as needed.

What's the best way to set up a daily briefing without manual intervention?

Define a scheduled task by writing a YAML file under the tasks directory using a generated UUID. The controller registers the cron-based execution, synchronizing the daily briefing generation with the current app context automatically.

Do I need to manually update the controller when creating scheduled tasks?

The controller must be updated to register cron-based executions after you write task definitions to the tasks_dir. This registration step ensures the recurring task runs at the scheduled intervals.

How does the YAML schema structure work for defining recurring workspace tasks?

The YAML schema requires a task definition written to the tasks directory with a UUID filename. It includes the cron expression for scheduling and an enable switch to control execution, conforming to the specified structure for recurring workflows.

Why are UUID filenames required for task files in the tasks directory?

UUID filenames uniquely identify each scheduled task within the tasks directory. This prevents naming collisions when multiple recurring task definitions are registered and executed by the controller.