task-parsing

Convert natural language task descriptions into structured tasks with priority, dates, and tags.

1|1|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/aviz85/claude-tasks --skill task-parsing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task-parsing
Source: https://github.com/aviz85/claude-tasks/tree/main/.claude/skills/task-parsing
Command: npx skills add https://github.com/aviz85/claude-tasks --skill task-parsing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill converts casually described work into formal task items with priority, due date, project, and tags, enabling automation and improved planning.

Core Features & Use Cases

  • Automated conversion: Transform natural language into a ready-to-use checkbox task with optional priority, due date, project, and tags.
  • Context-aware routing: Infer destination project and tags from the task description for effective organization.
  • Use Case: Example: "Review John's PR for the auth feature, it's blocking the release" becomes a prioritized task ready for today or backlog based on urgency.

Quick Start

Use the task-parsing skill to convert a natural language task into a structured checklist item. Example: "Review John's PR for the API feature, it's blocking the release" → - [ ] Review John's PR for API feature @work #review #code !high ~30m

Frequently Asked Questions about task-parsing

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

FAQPage Schema
How do I convert natural language into structured tasks with priority and tags?

To convert natural language into structured tasks, the Skill parses casual descriptions and extracts priority, due dates, projects, and tags to output a ready-to-use checklist item. It identifies priority markers like !high and tags like #review automatically.

Can I parse inbox notes into prioritized checklist items for project routing?

Yes, you can parse inbox-like notes into prioritized checklist items. The Skill infers destination projects and tags from the task description, enabling automated routing across personal and team workflows for effective organization.

What is the best way to extract time estimates and priority from task descriptions?

The best way to extract time estimates and priority from task descriptions is using natural language parsing. The Skill identifies time estimates ranging from ~15m to ~4h and priority levels from text to generate structured task data.

Does natural language task parsing work for both personal and team workflows?

Natural language task parsing works for both personal and team workflows. It processes casually described work across various contexts, transforming text into formal task items with due dates, projects, and tags for improved planning.

How do I format a natural language task to include project and tag markers?

To format a natural language task with project and tag markers, use symbols like @project and #tag in your text. The parser recognizes these along with priority indicators such as !high and time estimates like ~30m to structure the output.

What are the limitations of parsing natural language tasks without dependencies?

As a basic implementation with no dependencies, this Skill processes text to extract structured task attributes like priority, dates, and tags. It focuses on parsing syntax and inferring routing context rather than executing the tasks themselves.