task-classifier

Classify task descriptions into agent specializations using keyword matching.

14|2|Updated Sep 23, 2025
One-click install
npx skills add https://github.com/masharratt/claude-flow-novice --skill task-classifier
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task-classifier
Source: https://github.com/masharratt/claude-flow-novice/tree/main/.claude/skills/cfn-task-intelligence/lib/classifier
Command: npx skills add https://github.com/masharratt/claude-flow-novice --skill task-classifier

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires grep, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Classifies tasks into frontend/backend/infrastructure/etc. for agent selection.

Core Features & Use Cases

  • Keyword-driven classification
  • Multi-category outputs

Quick Start

classify-task.sh "Build React UI with API backend"

Frequently Asked Questions about task-classifier

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

FAQPage Schema
How do I classify tasks to route them to the right agent or specialist?

Task classification maps natural-language task descriptions to agent specializations using keyword-based pattern matching. The Skill matches task briefs against domain keywords for frontend, backend, DevOps, security, data, testing, and documentation to determine optimal agent routing, returning multiple classifications when applicable.

Can I classify mixed tasks that span multiple domains?

Yes. The Skill returns multiple classifications when task keywords match several domains. For example, "Build React UI with API backend" classifies as both frontend and backend, allowing multi-agent task orchestration.

What happens if a task description doesn't match any domain keywords?

The Skill falls back to a general classification when no domain-specific keywords match. It maintains stateless operation with exit status 0 on success, ensuring consistent behavior across task inputs.

How does the keyword matching work under the hood?

Classification uses grep with extended regex patterns (grep -E) to scan task descriptions against domain keyword arrays for frontend, backend, DevOps, security, data, testing, and documentation specializations.

What's the difference between this and manual agent selection?

Keyword-driven classification automates agent routing by pattern matching domain keywords in task descriptions, eliminating manual mapping overhead while handling multi-category tasks that require coordination across specializations.