Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Task Manager

ASecurity

Design a personal task management system that actually works: capture, clarify, organize, review, and engage across any tool. Use when choosing or fixing how you manage tasks, or evaluating task apps.

2 stars
0 votes
0 copies
0 views
Added 9/29/2026
ai-agentsrustgo

Security Analysis

A100/100

Scanned 9/29/2026

$npx -y skills add aicodedecode/awesome-muse-skills --skill task-manager --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Task Manager?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Task Manager
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aicodedecode-task-manager/badge)](https://www.skillsdirectory.com/skills/aicodedecode-task-manager)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: task-manager
description: Design a personal task management system that actually works: capture, clarify, organize, review, and engage across any tool. Use when choosing or fixing how you manage tasks, or evaluating task apps.
category: productivity
---

# Task Manager

## Overview

Tools don't manage tasks; systems do. Pick the workflow before the app — always in that order.

Every effective system answers five questions: where do I capture, how do I clarify, where does it live, when do I review, what do I do now?

Task management fails for four predictable reasons: slow capture, vague tasks, flat lists with no priorities, and no reviews.

Fix those four and almost any tool works — from a $10/month app to index cards.

Mental shift: your system exists to let you forget. If tasks live in your head 'just in case,' the system has failed.

## When to use

- Choosing between task apps (or deciding you don't need a new one)
- Your current system feels overwhelming, stale, or untrusted
- Setting up task management for a team, family, or household
- Designing the workflow before picking the tool
- Evaluating whether a fancy new app will actually help (it won't, without the system)

## Core concepts

- **The five stages.**
  Capture -> Clarify -> Organize -> Review -> Engage. Every system implements these; most failures are a skipped stage.
- **Trusted system.**
  Your brain must believe the system holds everything and gets reviewed. One complete system beats two half-systems.
- **Next actions.**
  Every project needs a defined next physical, visible action. 'Plan trip' paralyzes; 'Email Maya for hotel recs' moves.
- **Horizons of focus.**
  Runway (today), projects (month), goals (year), vision (3-5 years). Review each at its own cadence: daily, weekly, quarterly, yearly.
- **Timeboxing.**
  A to-do list tells you what; a calendar tells you when. Assign tasks to blocks — the combination is what gets things done.
- **The 2-minute rule.**
  If clarifying reveals a sub-2-minute task, do it now. Filing a 90-second task costs more than doing it.
- **Waiting-for tracking.**
  Delegated items need a home with a follow-up date or they silently die. Waiting-for is a first-class list.
- **Someday/maybe parking lot.**
  Low-priority ideas need deliberate parking, reviewed monthly — otherwise they clog active lists or get lost.

## Practical workflow

1. **Pick one capture tool.**
   The one you'll actually open everywhere: app, notebook, voice memos. Speed and ubiquity beat features.
2. **Define your lists.**
   Minimum viable: Inbox, Next Actions, Waiting For, Projects, Someday/Maybe. Add contexts only if useful.
3. **Clarify ruthlessly.**
   Per inbox item: what's the outcome? Next physical action? <2 min (do it), delegatable (waiting-for + date), multi-step (project + next action).
4. **Organize by outcome.**
   Group by project/goal. Due dates only for real deadlines — fake urgency trains you to ignore all dates.
5. **Timebox the day.**
   Each morning place 3-5 key tasks into calendar blocks. Protect one 90-minute deep-work block. Leave 30% buffer.
6. **Do the weekly review.**
   Inbox to zero, every project checked for a next action, calendar scanned ahead. 30-60 min, same slot weekly.
7. **Review horizons quarterly.**
   Check projects against goals and vision. Kill or pause what no longer serves. Strategy meets the task list here.
8. **Keep one system.**
   Resist the second app, the side spreadsheet, the sticky notes. One system, fully captured, or the brain won't let go.

## Common pitfalls

- **Tool-hopping.**
  Switching apps monthly resets system and habits. Commit to one tool for a full quarter before judging it.
- **Vague tasks.**
  'Website', 'taxes', 'mom' are anxiety with a checkbox. Rewrite until the next action is physical and visible.
- **Over-scheduling.**
  10 hours of tasks in an 8-hour day. Leave 30-40% buffer or the plan collapses by noon.
- **Skipping the review.**
  A system without review rots in two weeks. The review isn't maintenance — the review IS the system.
- **Confusing projects and actions.**
  Multi-step projects in daily lists paralyze. Daily lists hold only next actions; projects live one level up.
- **No someday/maybe.**
  Without a parking lot, low-priority ideas clog active lists or get lost forever.
- **Head-storage.**
  'I'll remember' is the most expensive strategy ever invented. Not captured in 10 seconds = doesn't exist.
- **All capture, no clarify.**
  A 300-item inbox isn't a system, it's a junk drawer. Clarifying is the work; capturing is just intake.

Attribution

aicodedecodeaicodedecode
View sourceSee grades on GitHubMore from aicodedecode →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698461 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →