complexity-scorer
Acerca de
Esta habilidad analiza la complejidad de tareas mediante coincidencia de palabras clave y reglas heurísticas para clasificar tareas con fines de enrutamiento y priorización. Es ideal para construir despachadores inteligentes que dirijan el trabajo a manejadores apropiados o recomienden recursos basándose en umbrales configurables. Úsela para la autoclasificación de solicitudes, pero evítela para decisiones simples de sí/no o dominios altamente especializados.
Instalación rápida
Claude Code
Recomendadonpx skills add vamseeachanta/workspace-hub/plugin add https://github.com/vamseeachanta/workspace-hubgit clone https://github.com/vamseeachanta/workspace-hub.git ~/.claude/skills/complexity-scorerCopia y pega este comando en Claude Code para instalar esta habilidad
Documentación
Complexity Scorer
When to Use This Skill
✅ Use when:
- Routing tasks to different handlers based on complexity
- Recommending resources (models, workers, time estimates)
- Prioritizing work items
- Auto-classifying incoming requests
- Building intelligent dispatchers
❌ Avoid when:
- Simple yes/no classification
- When ML-based classification is more appropriate
- Highly domain-specific scoring that requires expertise
Complete Example: Task Complexity Scorer
#!/bin/bash
# ABOUTME: Complete task complexity scoring system
# ABOUTME: Multi-factor scoring with recommendations
set -e
# ─────────────────────────────────────────────────────────────────
# Configuration
# ─────────────────────────────────────────────────────────────────
# Colors
GREEN='\033[0;32m'
BLUE='\033[0;34m'
YELLOW='\033[1;33m'
CYAN='\033[0;36m'
RED='\033[0;31m'
NC='\033[0m'
# Keyword patterns
OPUS_KEYWORDS="architecture|refactor|design|security|complex|multi-file|algorithm|optimization|strategy|planning|cross-repository|performance|migration"
SONNET_KEYWORDS="implement|feature|bug|fix|code review|documentation|test|update|add|create|build"
HAIKU_KEYWORDS="check|status|simple|quick|template|list|grep|find|search|summary|validation|exists|show|display"
# Repository tiers
*See sub-skills for full details.*
## Resources
- [Regular Expressions in Bash](https://mywiki.wooledge.org/RegularExpression)
- [Pattern Matching](https://www.gnu.org/software/bash/manual/html_node/Pattern-Matching.html)
---
## Version History
- **1.0.0** (2026-01-14): Initial release - extracted from workspace-hub suggest_model.sh
## Sub-Skills
- [1. Keyword-Based Scoring (+1)](1-keyword-based-scoring/SKILL.md)
- [3. Context-Aware Scoring (+1)](3-context-aware-scoring/SKILL.md)
- [5. Confidence Scoring (+1)](5-confidence-scoring/SKILL.md)
- [Best Practices](best-practices/SKILL.md)
Repositorio GitHub
Habilidades relacionadas
performance-analysis
OtroThis skill provides comprehensive performance analysis and bottleneck detection for Claude Flow swarms, helping developers identify optimization opportunities. It offers real-time monitoring, profiling of swarm operations, and generates detailed reports with actionable recommendations. Use this skill when you need to diagnose performance issues and improve the efficiency of your Claude Code applications.
performance-analysis
OtroThe Performance Analysis skill provides comprehensive monitoring and optimization for Claude Flow swarms, detecting bottlenecks and profiling operations. It generates detailed performance reports and offers AI-powered optimization recommendations to improve swarm efficiency. Developers should use this skill when they need to identify performance issues and receive actionable insights for optimization.
testability-scoring
OtroThis skill provides AI-powered testability assessment for web applications using Playwright and optional Vibium integration. It evaluates applications against 10 intrinsic testability principles like Observability and Controllability to identify improvement areas. Use it when assessing software testability, evaluating test readiness, or generating testability reports.
six-thinking-hats
OtroThis Claude skill applies the Six Thinking Hats framework to software testing, guiding structured analysis for test strategy design, failure analysis, and retrospectives. It systematically explores a problem through six distinct perspectives: factual data, risks, benefits, creative solutions, emotional responses, and process control. Use it to facilitate comprehensive testing discussions and ensure balanced quality evaluations.
