How do I install the Claskit skill?

Run npx skillmds@latest add phucbm/claskit in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Claskit safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Claskit?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Claskit free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Claskit?

phucbm (@phucbm) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Claskit by phucbm — Agent Skill

Name: Claskit
Author: phucbm

Claskit

Autonomous Claude Code task runner — write task specs as Markdown files, run claskit, and Claude implements them one by one. Use when setting up claskit in a project, writing task specs, scheduling autonomous runs, or understanding the todo/done task lifecycle.

phucbm caa4143 3.1 KB Updated Sep 17, 2026

File contents

claskit — Autonomous Claude Code Task Runner

Repo: https://github.com/phucbm/claskit
npm: npx claskit or npm i -g claskit

What it does

claskit reads Markdown task specs from .claude/tasks/todo/, launches Claude with --dangerously-skip-permissions, and lets Claude implement them autonomously. On success each spec moves to .claude/tasks/done/.

Setup

npx claskit --init

Creates:

.claude/tasks/
  todo/     ← drop task specs here
  done/     ← claskit moves completed specs here
  README.md

Running tasks

npx claskit          # interactive menu (now / schedule)
npx claskit --now    # skip menu, run immediately

Interactive flow — schedule path:

Select tasks (comma-separated numbers or "all")
Enter time (HH:MM, 24h) — retries on invalid input
Confirm
Countdown → Claude launches at scheduled time

Creating a task spec with AI

When a user wants to create a claskit spec from a conversation (brainstorm, plan, feature description):

Use the /claskit skill — it reads the current conversation context and writes .claude/tasks/todo/<slug>.md directly
Or manually apply the format below

The /claskit skill handles: slug generation, folder creation, and correct file format. Prefer it over writing specs manually.

Task spec format

# Feature Title

## Task
What to implement — be specific.

## Acceptance Criteria
- [ ] Criterion 1
- [ ] Criterion 2

## Files Affected
- src/foo.ts

## Notes
Dependencies, order hints, constraints.

Save as .claude/tasks/todo/my-feature.md.

Key rules for writing specs

One concern per file — don't bundle unrelated changes
Acceptance criteria must be verifiable (file exists, test passes, UI shows X)
List dependencies in Notes so Claude orders tasks correctly
Never hardcode secrets or env values in specs

Commands

Command	What it does
`npx claskit`	Interactive menu
`npx claskit --init`	Initialize .claude/tasks/ structure
`npx claskit --now`	Run immediately, skip menu
`npx claskit --test`	Create 2 sample tasks to try claskit
`npx claskit --clean-test`	Remove sample tasks and output

How Claude processes specs

Reads all selected .md files
Decides execution order based on dependencies in Notes
Implements each spec fully
Verifies acceptance criteria
Runs build/lint (from package.json scripts)
Moves .md from todo/ → done/ on success
Stops and reports on any failure

Gotchas

Requires Claude Code CLI (claude) installed and authenticated
--dangerously-skip-permissions — only use in trusted, backed-up projects
macOS: uses caffeinate during scheduled countdown to prevent sleep
Specs in todo/ are read-only — claskit (not you) moves them to done/

---name: claskitdescription: Autonomous Claude Code task runner — write task specs as Markdown files, run claskit, and Claude implements them one by one. Use when setting up claskit in a project, writing task specs, scheduling autonomous runs, or understanding the todo/done task lifecycle.---# claskit — Autonomous Claude Code Task Runner**Repo:** https://github.com/phucbm/claskit **npm:** `npx claskit` or `npm i -g claskit`## What it doesclaskit reads Markdown task specs from `.claude/tasks/todo/`, launches Claude with `--dangerously-skip-permissions`, and lets Claude implement them autonomously. On success each spec moves to `.claude/tasks/done/`.## Setup```bashnpx claskit --init```Creates:```.claude/tasks/ todo/ ← drop task specs here done/ ← claskit moves completed specs here README.md```## Running tasks```bashnpx claskit # interactive menu (now / schedule)npx claskit --now # skip menu, run immediately```Interactive flow — **schedule path**:1. Select tasks (comma-separated numbers or "all")2. Enter time (HH:MM, 24h) — retries on invalid input3. Confirm4. Countdown → Claude launches at scheduled time## Creating a task spec with AIWhen a user wants to create a claskit spec from a conversation (brainstorm, plan, feature description):1. Use the `/claskit` skill — it reads the current conversation context and writes `.claude/tasks/todo/<slug>.md` directly2. Or manually apply the format belowThe `/claskit` skill handles: slug generation, folder creation, and correct file format. Prefer it over writing specs manually.## Task spec format```markdown# Feature Title## TaskWhat to implement — be specific.## Acceptance Criteria- [ ] Criterion 1- [ ] Criterion 2## Files Affected- src/foo.ts## NotesDependencies, order hints, constraints.```Save as `.claude/tasks/todo/my-feature.md`.## Key rules for writing specs- One concern per file — don't bundle unrelated changes- Acceptance criteria must be verifiable (file exists, test passes, UI shows X)- List dependencies in Notes so Claude orders tasks correctly- Never hardcode secrets or env values in specs## Commands| Command | What it does ||---|---|| `npx claskit` | Interactive menu || `npx claskit --init` | Initialize .claude/tasks/ structure || `npx claskit --now` | Run immediately, skip menu || `npx claskit --test` | Create 2 sample tasks to try claskit || `npx claskit --clean-test` | Remove sample tasks and output |## How Claude processes specs1. Reads all selected `.md` files2. Decides execution order based on dependencies in Notes3. Implements each spec fully4. Verifies acceptance criteria5. Runs build/lint (from package.json scripts)6. Moves `.md` from `todo/` → `done/` on success7. Stops and reports on any failure## Gotchas- Requires Claude Code CLI (`claude`) installed and authenticated- `--dangerously-skip-permissions` — only use in trusted, backed-up projects- macOS: uses `caffeinate` during scheduled countdown to prevent sleep- Specs in `todo/` are read-only — claskit (not you) moves them to `done/`

Frequently asked questions