Agent skill

Skill Task Management

by nyldn in nyldn/claude-octopus

Manage tasks with Claude Code native tools — use to track TODOs, delegate work, and monitor progress

MITAuto-check passedProductivity & Automation

Install Skill Task Management

skills CLI
$ npx skills add nyldn/claude-octopus --skill skill-task-management -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install nyldn/claude-octopus skill-task-management --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/nyldn/claude-octopus.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/skill-task-management .claude/skills/skill-task-management && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
skill-task-management
GitHub stars
4.2k
Used in
1 other repo
Token cost
~3.8k tokens
SKILL.md length
743 words
Files
2
Skills in repo
62
Repo updated
First seen
Licence
MIT

At a glance

Manage tasks with Claude Code native tools — use to track TODOs, delegate work, and monitor progress

  • Works in 7 steps: Adding Tasks to Todo List → Saving Progress / Checkpointing → Resuming Tasks → …
  • Monitor progress
  • SKILL.md covers Overview, When to Use, Core Capabilities and Migration from task plan tool…, plus 8 more sections
  • Calls git

What it does

Skill Task Management is an agent skill from nyldn/claude-octopus. Manage tasks with Claude Code native tools — use to track TODOs, delegate work, and monitor progress

Its SKILL.md is about 3.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in Productivity & Automation, covering Task management. It works with Git. The repository describes itself as: Run multiple AI models against the same research, design, or coding task. Surface disagreements before you ship. The licence is MIT.

When your agent uses it

  • Monitor progress
  • Tasks that involve Task management

Example prompts

  • “/skill-task-management”

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Adding Tasks to Todo List
  2. Saving Progress / Checkpointing
  3. Resuming Tasks
  4. Proceeding to Next Steps
  5. Clear Task Subjects and Descriptions
  6. Use Task Dependencies
  7. Context Preservation in Checkpoints

What it can do on your machine

Read from SKILL.md and the folder at commit 4d152db. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Skill Task Management loads about 3.8k tokens when it runs. Until then it costs about 31 tokens; SKILL.md has 743 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~31
When it runs · the whole SKILL.md, loaded when a task matches
~3.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from nyldn/claude-octopus at commit 4d152db, republished under its MIT licence (© nyldn). 743 words, ~3,824 tokens.

Download SKILL.mdSave it as .claude/skills/skill-task-management/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
skill-task-management
description
Manage tasks with Claude Code native tools — use to track TODOs, delegate work, and monitor progress
disable-model-invocation
true

Host: Codex CLI — This skill was designed for Claude Code and adapted for Codex. Cross-reference commands use installed skill names in Codex rather than /octo:* slash commands. Use the active Codex shell and subagent tools. Do not claim a provider, model, or host subagent is available until the current session exposes it. For host tool equivalents, see skills/blocks/codex-host-adapter.md.

Task Management & Orchestration (v7.23.0+)

Overview

Systematic task orchestration for multi-step work, progress checkpointing, and seamless task resumption across sessions.

Core principle: Track → Checkpoint → Resume → Complete.

v7.23.0 Migration: This skill now uses native Claude Code host subagent tools:

  • TaskCreate - Create new tasks
  • TaskUpdate - Update task status/details
  • TaskList - View all tasks
  • TaskGet - Get specific task details

Benefits:

  • ✅ Tasks show in native Claude Code UI
  • ✅ Better progress tracking and visualization
  • ✅ Consistent with Claude Code conventions
  • ✅ No dependency on external task plan tool tool

When to Use

Use this skill when user wants to:

  • Add items to the todo list
  • Save current progress for later continuation
  • Resume previously saved work
  • Checkpoint progress in long-running tasks
  • Proceed to next steps in a workflow
  • Continue from where they left off

Do NOT use for:

  • Creating git commits (use skill-finish-branch)
  • Simple todo list queries ("what's on my list?")
  • Task completion that involves pushing code

Core Capabilities

1. Adding Tasks to Todo List

When user says "add to the todo's" or similar:

markdown
**What would you like to add to the todo list?**

I'll help you capture this task. Please provide:
- Task description (what needs to be done)
- Any dependencies or prerequisites
- Priority (if applicable)

After getting details, use TaskCreate to add:

javascript
TaskCreate({
  subject: "[Brief task description]",
  description: "[Detailed description including dependencies and context]",
  activeForm: "Working on [task description]"
})

Then confirm to user:

✅ Task created: [Task description]

View all tasks with TaskList or use /tasks command.
2. Saving Progress / Checkpointing

When user says "save progress" or "checkpoint this":

Step 1: Assess Current State
bash
# Check git status
git status

# Check current branch
git branch --show-current

# Check uncommitted work
git diff --stat
Step 2: Create Progress Checkpoint

Option A: Git-based checkpoint (if git repo)

bash
# Create a work-in-progress commit
git add .
git commit -m "WIP: [description of current state]

Progress checkpoint - work in progress
Not ready for review or merge

Current state:
- [What's completed]
- [What's in progress]
- [What's next]

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>"

Option B: Task-based checkpoint (preferred for tracking)

Create checkpoint task with detailed state:

javascript
TaskCreate({
  subject: "Checkpoint: [Brief description]",
  description: `
📍 CHECKPOINT: ${new Date().toISOString()}

Completed:
✓ [Task 1]
✓ [Task 2]

In Progress:
⚙️ [Current task with details]

Next Steps:
- [ ] [Next task 1]
- [ ] [Next task 2]
- [ ] [Next task 3]

Context:
- Branch: ${branchName}
- Last commit: ${lastCommit}
- Files changed: ${filesChanged}
  `,
  activeForm: "Checkpoint saved"
})
Step 3: Update Existing Tasks

Mark completed tasks as done:

javascript
// For each completed task
TaskUpdate({
  taskId: "[task-id]",
  status: "completed"
})

Mark current task as in_progress:

javascript
TaskUpdate({
  taskId: "[current-task-id]",
  status: "in_progress"
})
Step 4: Provide Resume Instructions
markdown
✅ Progress saved!

To resume this work:
1. Run: git checkout [branch-name]
2. View tasks: TaskList
3. Say: "resume tasks" or "pick up where we left off"

Current state:
- Branch: [branch-name]
- Tasks: [X completed, Y in progress, Z pending]
- Last checkpoint: [timestamp]
3. Resuming Tasks

When user says "resume tasks" or "pick up where we left off":

Step 1: Load Task State
javascript
// Get all tasks
const tasks = TaskList()

// Filter by status
const completed = tasks.filter(t => t.status === 'completed')
const inProgress = tasks.filter(t => t.status === 'in_progress')
const pending = tasks.filter(t => t.status === 'pending')

// Find checkpoint task (if exists)
const checkpoint = tasks.find(t => t.subject.startsWith('Checkpoint:'))
Step 2: Check Git State
bash
# Check for WIP commits
git log --oneline -10 | grep WIP

# Check current branch
git branch --show-current

# Check git status
git status
Step 3: Present Current State
markdown
📋 **Resuming from last checkpoint**

**Branch:** [branch-name]
**Last checkpoint:** [timestamp from WIP commit or checkpoint task]

**Completed:** (${completed.length} tasks)
${completed.map(t => `✓ ${t.subject}`).join('\n')}

**In Progress:** (${inProgress.length} tasks)
${inProgress.map(t => `⚙️ ${t.subject}`).join('\n')}

**Next Steps:** (${pending.length} tasks)
${pending.map((t, i) => `${i + 1}. [ ] ${t.subject}`).join('\n')}

**Would you like me to:**
1. Continue with the next task?
2. Modify the plan?
3. See more details about current state?
Step 4: Execute Based on Choice
  • If "continue with next task" → Get first pending task, mark as in_progress, and begin work:

    javascript
    const nextTask = pending[0]
    TaskUpdate({ taskId: nextTask.id, status: 'in_progress' })
    // Begin working on nextTask
  • If "modify the plan" → Use AskUserQuestion to understand changes, then update tasks

  • If "see more details" → Show git diff, file changes, recent commits, task descriptions

4. Proceeding to Next Steps

When user says "proceed to next steps":

Step 1: Check Current Task Status
javascript
const tasks = TaskList()
const currentTask = tasks.find(t => t.status === 'in_progress')

if (currentTask) {
  console.log(`Current task: ${currentTask.subject}`)
  console.log(`Status: ${currentTask.status}`)
}
Step 2: Complete Current and Move Forward
javascript
// Mark current task as complete
if (currentTask) {
  TaskUpdate({
    taskId: currentTask.id,
    status: 'completed'
  })
  console.log(`✓ ${currentTask.subject}`)
}

// Get next pending task
const nextTask = tasks.find(t => t.status === 'pending' && !t.blockedBy?.length)

if (nextTask) {
  // Mark as in progress
  TaskUpdate({
    taskId: nextTask.id,
    status: 'in_progress'
  })
  console.log(`\n⚙️ ${nextTask.subject}`)
  console.log(`\nProceeding with: ${nextTask.description}`)
}
Step 3: Execute Next Task

Begin working on the next task immediately after marking it as in_progress.

Migration from task plan tool (v7.22.x → v7.23.0+)

For Users with Existing .md Todo Files

If you have existing .claude/todos.md or similar files:

Show full SKILL.md (308 more words)Show less
Option 1: Automatic Migration
bash
# Run migration script
"${HOME}/.claude-octopus/plugin/scripts/migrate-todos.sh"

This will:

  1. Parse existing .md todo files
  2. Convert to TaskCreate calls
  3. Preserve task order and status
  4. Archive old .md files to .claude/archived-todos/
Option 2: Manual Migration

For each todo item in your .md file:

markdown
<!-- Old format in todos.md -->
- [ ] Implement user authentication
- [x] Set up database
- [ ] Create API endpoints

Convert to:

javascript
// New format using native tasks
TaskCreate({
  subject: "Implement user authentication",
  description: "Create auth system with JWT tokens",
  activeForm: "Implementing authentication"
})

TaskCreate({
  subject: "Set up database",
  description: "Configure PostgreSQL and run migrations",
  activeForm: "Setting up database"
})
// Mark as completed since it was [x]
TaskUpdate({ taskId: "...", status: "completed" })

TaskCreate({
  subject: "Create API endpoints",
  description: "Build REST API for user operations",
  activeForm: "Creating API endpoints"
})
Backward Compatibility

Opt-out for users who prefer old system:

Create .claude/claude-octopus.local.md with:

yaml
use_native_tasks: false

# Claude Octopus Local Configuration

This project uses legacy task plan tool tool instead of native Task management.

When use_native_tasks: false, skill falls back to task plan tool behavior.

Integration with Other Skills

With skill-finish-branch
User: "save progress and prepare for PR"

1. Use skill-task-management to checkpoint (create tasks for current state)
2. Then use skill-finish-branch to prepare PR
With flow-develop
User: "add implementation of auth system to todos"

1. Use skill-task-management to add high-level task
2. Use flow-develop to break down and implement
3. Update tasks as work progresses
With skill-debug
User: "checkpoint this, I found a bug"

1. Use skill-task-management to save current progress (checkpoint task)
2. Use skill-debug to investigate the bug
3. Return to saved checkpoint after fix

Best Practices

1. Clear Task Subjects and Descriptions

Good task:

javascript
TaskCreate({
  subject: "Implement token refresh with 15-minute expiration",
  description: `
Create token refresh endpoint that:
- Validates refresh token from secure HTTP-only cookie
- Issues new access token with 15min expiry
- Rotates refresh token for security
- Returns 401 if refresh token invalid/expired

Dependencies: OAuth provider setup must be complete
  `,
  activeForm: "Implementing token refresh logic"
})

Poor task:

javascript
TaskCreate({
  subject: "Do auth stuff",
  description: "Fix things",
  activeForm: "Working"
})
2. Use Task Dependencies

For tasks with prerequisites:

javascript
// First task
TaskCreate({
  subject: "Set up OAuth provider configuration",
  description: "Configure Auth0 application settings",
  activeForm: "Configuring OAuth provider"
})

// Dependent task
TaskCreate({
  subject: "Implement token refresh endpoint",
  description: "Create /auth/refresh endpoint",
  activeForm: "Implementing refresh endpoint",
  addBlockedBy: ["1"]  // Blocked by task #1
})
3. Context Preservation in Checkpoints

When checkpointing, always include:

  • What's completed (prevents re-doing work)
  • What's in progress (enables quick resume)
  • What's next (provides clear path forward)
  • Why decisions were made (preserves reasoning)

Example checkpoint task:

javascript
TaskCreate({
  subject: "Checkpoint: Auth implementation 70% complete",
  description: `
📍 CHECKPOINT: 2026-02-03T14:30:00Z

Completed:
✓ OAuth provider configuration (Auth0)
✓ Token exchange endpoint (/auth/login)
✓ User session middleware

In Progress:
⚙️ Token refresh logic (70% done)
  - Validation complete
  - Token rotation TODO
  - Cookie handling TODO

Next:
- [ ] Complete token rotation logic
- [ ] Add logout endpoint
- [ ] Add session expiration handling
- [ ] Write integration tests

Branch: feature/auth-system
Last commit: abc123f "Add session middleware"

Decisions Made:
- Using Auth0 (rationale: enterprise-grade, handles complexity)
- 15-minute access token expiry (security vs UX balance)
- HTTP-only cookies for refresh tokens (XSS protection)
  `,
  activeForm: "Checkpoint saved"
})

Common Patterns

Pattern 1: End-of-Day Checkpoint
User: "save progress, I'm done for today"

Action:
1. Create WIP commit with current state
2. Create checkpoint task with completed/pending breakdown
3. Mark in-progress tasks with current status
4. Provide resume instructions for tomorrow
Pattern 2: Context Switch
User: "checkpoint this, need to work on something else"

Action:
1. Save current branch state (WIP commit)
2. Create checkpoint task with detailed context
3. Mark current task as pending (will resume later)
4. Ready for resume when user returns
Pattern 3: Collaboration Handoff
User: "save progress for Claude to pick up"

Action:
1. Create comprehensive checkpoint task
2. Document all context and decisions
3. Mark in-progress tasks with current state
4. Ensure new session can load task state and resume seamlessly

Red Flags - Don't Do This

ActionWhy It's Wrong
Checkpoint without documenting contextNext session won't know what was happening
Skip WIP commit for code changesLose work if something breaks
Generic "proceed to next" without checking TaskListMight skip incomplete work
Vague task subjects/descriptionsUnclear what needs to be done
Resume without showing TaskList stateUser doesn't know where they are
Create tasks without activeFormNo progress indication in UI

Quick Reference

User IntentSkill ActionTool Used
"add to todos"Gather details, create taskTaskCreate
"save progress"Create checkpoint task + WIP commitTaskCreate + git
"resume tasks"Load task state, show status, ask directionTaskList
"proceed to next"Complete current, start nextTaskUpdate
"checkpoint this"Create detailed checkpoint taskTaskCreate

Task Status Workflow

pending → in_progress → completed
                ↓
              deleted (if no longer needed)

Best practices:

  • Create tasks in pending state
  • Mark in_progress when starting work
  • Mark completed only when fully done
  • Use deleted for cancelled/obsolete tasks

The Bottom Line

Task management → Clear state + Easy resume + Native UI
Otherwise → Lost context + Duplicate work + No visibility

Track everything. Checkpoint frequently. Resume seamlessly. Use native tools.

Example: Full Workflow

javascript
// User: "add implementing auth to my todos"

// Step 1: Create main task
TaskCreate({
  subject: "Implement user authentication system",
  description: `
Build complete auth system with:
- OAuth 2.0 (Auth0 provider)
- JWT token management
- Refresh token rotation
- Session middleware
- Logout functionality
  `,
  activeForm: "Planning authentication implementation"
})

// User works on it...

// User: "save progress for tomorrow"

// Step 2: Create checkpoint
TaskCreate({
  subject: "Checkpoint: Auth implementation in progress",
  description: `
📍 Checkpoint: 2026-02-03T18:30:00Z

Completed:
✓ OAuth configuration
✓ Login endpoint

In Progress:
⚙️ Token refresh (50%)

Next:
- [ ] Complete refresh logic
- [ ] Add logout
- [ ] Write tests

Branch: feature/auth
Commit: abc123f
  `,
  activeForm: "Checkpoint saved"
})

// Step 3: Update main task status
TaskUpdate({
  taskId: "1",
  status: "in_progress"
})

// User: "resume tasks" (next day)

// Step 4: Load and present state
const tasks = TaskList()
// Present: "You have 1 in_progress task, last checkpoint 2026-02-03T18:30:00Z"
// Show details from checkpoint task

// User: "continue"

// Step 5: Resume work
const currentTask = tasks.find(t => t.status === 'in_progress')
// Begin working on token refresh where they left off

© nyldn, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in skills/skill-task-management of nyldn/claude-octopus.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit 4d152db

Used in 1 other repository

We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in nyldn/claude-octopus, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Skill Task Management next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Skill Task Management compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Skill Task Management this skillnyldn/claude-octopus4.2k1 repos~3.8kAutomated safety check: PassMIT
Linear Autopilotsundial-org/awesome-openclaw-skills663—~1.5kAutomated safety check: PassNone
Epiqljtn/epiq535—~930Automated safety check: PassMIT
Knowledge Interaction Surfaces Web ClientechoVic/blade-code181—~2kAutomated safety check: PassMIT
Kanvibe Release Deployrookedsysc/kanvibe143—~12kAutomated safety check: NotesAGPL-3.0
Diagram312362115/claude107—~2.7kAutomated safety check: PassMIT

Similar skills

  • Linear Autopilot

    sundial-org/awesome-openclaw-skills

    Automate Linear task processing with Discord notifications and git sync.

    663 GitHub stars~1.5k tokensUpdated 7 mo ago
    Productivity & AutomationAuto-check passed
  • Epiq

    ljtn/epiq

    Workflow for working an epiq issue board through the epiq MCP — take an identity, sync on demand, keep tickets small and their status, tags and comments current.

    535 GitHub stars~930 tokensUpdated today
    Productivity & AutomationAuto-check passed
  • 覆盖 Blade React Web 的启动恢复、Session/任务 Zustand 投影、SSE 重连、聊天输入、 多项目导航、布局、预览、Browser 面板与终端。进入时机:修改 Web 消息流、Session 切换、草稿、错误恢复、Sidebar/Kanban、全屏预览、文件/Browser 活动或前端 API。

    181 GitHub stars~2k tokensUpdated 11 days ago
    Productivity & AutomationAuto-check passed
  • Kanvibe Release Deploy

    rookedsysc/kanvibe

    A skill your agent uses whenever releasing or deploying KanVibe desktop from a clean, up-to-date dev checkout: ask only for the target version and release-note approval, then let the AI update…

    143 GitHub stars~12k tokensUpdated today
    DevelopmentAuto-check: notes
  • Diagram

    312362115/claude

    专业图表生成技能:根据需求自动选择合适的图表类型,生成符合设计规范的 PNG 图表. An agent skill from 312362115/claude.

    107 GitHub stars~2.7k tokensUpdated 4 mo ago
    DevelopmentAuto-check passed
  • Flow Next Work

    gmickel/flow-next

    Execute a Flow spec or task systematically with git setup, task tracking, quality checks, and commit workflow.

    707 GitHub stars~1.9k tokensUpdated today
    Backend & APIsAuto-check passed

More from nyldn/claude-octopus

All 62 skills in this repo
  • Octopus Quick

    nyldn/claude-octopus

    Quick execution for ad-hoc tasks without full workflow overhead — use for small, self-contained requests

    4.2k GitHub starsUsed in 1 repo~2.2k tokens
    Auto-check passed
  • Octopus Research

    nyldn/claude-octopus

    Thorough research across multiple sources — use for complex topics needing broad synthesis

    4.2k GitHub starsUsed in 1 repo~1.9k tokens
    Auto-check passed
  • Octopus Security Audit

    nyldn/claude-octopus

    OWASP compliance, vulnerability scanning, and adversarial red team testing — use for security reviews

    4.2k GitHub starsUsed in 1 repo~2.3k tokens
    Auto-check passed
  • Skill Audit

    nyldn/claude-octopus

    Audit codebases for quality, consistency, and broken patterns — use for pre-release or tech debt review

    4.2k GitHub starsUsed in 1 repo~3.2k tokens
    Auto-check passed
  • Skill Content Pipeline

    nyldn/claude-octopus

    Extract patterns and anatomy from URLs — use to reverse-engineer content strategies from live pages

    4.2k GitHub starsUsed in 1 repo~3.9k tokens
    Auto-check passed
  • Skill Context Detection

    nyldn/claude-octopus

    Auto-detect work context (Dev vs Knowledge) — use to tailor workflows based on current task type

    4.2k GitHub starsUsed in 1 repo~2.6k tokens
    Auto-check passed

Works with

Questions about Skill Task Management

What does Skill Task Management do?

Manage tasks with Claude Code native tools — use to track TODOs, delegate work, and monitor progress. Skill Task Management is an agent skill from nyldn/claude-octopus.

When should I use Skill Task Management?

Skill Task Management fits situations like: monitor progress; tasks that involve Task management.

How do I install Skill Task Management in Claude Code?

Run `npx skills add nyldn/claude-octopus --skill skill-task-management -a claude-code`. Or copy the skill folder (skills/skill-task-management in nyldn/claude-octopus) into .claude/skills/skill-task-management in your project. Claude Code loads it when a task matches its description.

How do I install Skill Task Management in Codex?

Run `npx skills add nyldn/claude-octopus --skill skill-task-management -a codex`. Or copy the skill folder (skills/skill-task-management in nyldn/claude-octopus) into .agents/skills/skill-task-management in your project. Codex loads it when a task matches its description.

Can I use Skill Task Management in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add nyldn/claude-octopus --skill skill-task-management -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/skill-task-management, .gemini/skills/skill-task-management, .github/skills/skill-task-management and .opencode/skills/skill-task-management in your project.

What does Skill Task Management need to run?

Going by SKILL.md and its folder, Skill Task Management needs the command-line tools its instructions call (git).

Does Skill Task Management access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Skill Task Management safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Skill Task Management use?

Skill Task Management is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Skill Task Management use?

About 3.8k tokens (SKILL.md is roughly 15k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Skill Task Management?

Skills that share tags, products or a category with Skill Task Management: Linear Autopilot (sundial-org/awesome-openclaw-skills, 663 stars), Epiq (ljtn/epiq, 535 stars), Knowledge Interaction Surfaces Web Client (echoVic/blade-code, 181 stars) and Kanvibe Release Deploy (rookedsysc/kanvibe, 143 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Skill Task Management?

nyldn (a GitHub user) maintains it in nyldn/claude-octopus, which has 4,182 GitHub stars. The repository holds 62 skills in this directory. The repository was last updated on October 7, 2026.

Source: nyldn/claude-octopus on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.