task-classifier

Classify incoming tasks into complexity categories and output JSON routing decisions.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/matt-metivier/zk-hub --skill task-classifier-matt-metivier
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: task-classifier
Source: https://github.com/matt-metivier/zk-hub/tree/main/skills/orchestrator/task-classifier
Command: npx skills add https://github.com/matt-metivier/zk-hub --skill task-classifier-matt-metivier

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Classify incoming tasks to determine the appropriate execution path and routing decisions within zk-hub, enabling smarter workload management.

Core Features & Use Cases

  • Classifies tasks into SIMPLE, COMPLEX, RESEARCH_ONLY, and CLASSIFICATION to guide routing.
  • Supports triage and backlog prioritization by evaluating task scope and impact.
  • Integrates with intake channels (CLI, meetings, automation) to standardize task handling.

Quick Start

Ask zk-hub to classify a new task to determine its routing path and required approach.

Frequently Asked Questions about task-classifier

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

FAQPage Schema
How do I automate task triage and routing based on complexity?▼

Task triage and routing can be automated by classifying incoming tasks to determine their complexity and execution path. This standardizes workload management by evaluating task scope to output a JSON object with routing and approach suggestions.

What is the best way to classify incoming tasks for backlog prioritization?▼

Classifying incoming tasks for backlog prioritization involves evaluating task scope and impact to categorize them into types like SIMPLE or COMPLEX. This process outputs a structured JSON object containing reasoning and a suggested approach for prioritization.

How does task classification work for meeting and CLI intake channels?▼

Task classification for CLI, meetings, and automation triggers works by standardizing intake handling. It processes incoming requests to determine routing paths, returning a JSON object with task type, complexity level, and required execution approach.

Can I categorize tasks into different complexity levels for workflow routing?▼

You can categorize tasks into SIMPLE, COMPLEX, RESEARCH_ONLY, and CLASSIFICATION levels to guide workflow routing. This categorization evaluates task scope and impact to produce a JSON object detailing the suggested execution approach.

What task types are supported when routing work items by complexity?▼

Routing work items by complexity supports task types including SIMPLE, COMPLEX, RESEARCH_ONLY, and CLASSIFICATION. Each classification evaluates scope to return a JSON object with the complexity level, reasoning, and suggested approach.

Do I need specific dependencies to classify tasks and determine routing paths?▼

No specific dependencies are required to classify tasks and determine routing paths. The process applies to task intake across CLI, meetings, or automation triggers and outputs a JSON object with complexity, task type, reasoning, and suggested approach.