.claude/skills/ac-complexity-assessor/SKILL.md
Assess feature and project complexity. Use when estimating effort, determining spec pipeline type, calculating cost estimates, or planning resource allocation.
npx skillsauth add adaptationio/skrillz ac-complexity-assessorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Assess complexity for effort estimation and planning.
Analyzes features and projects to determine complexity levels, estimate effort, and select appropriate processing pipelines.
from scripts.complexity_assessor import ComplexityAssessor
assessor = ComplexityAssessor(project_dir)
assessment = await assessor.assess_project()
print(assessment.pipeline_type) # SIMPLE/STANDARD/COMPLEX
print(assessment.estimated_hours)
{
"project_complexity": "STANDARD",
"pipeline_type": "STANDARD",
"metrics": {
"total_features": 75,
"dependency_depth": 4,
"category_count": 8,
"integration_points": 5,
"technology_complexity": 3
},
"estimates": {
"total_hours": 120,
"estimated_cost_usd": 45.00,
"estimated_sessions": 15,
"features_per_session": 5
},
"feature_estimates": [
{
"id": "auth-001",
"complexity": "low",
"estimated_hours": 1.5,
"factors": ["standard_pattern", "no_dependencies"]
}
],
"recommendations": [
"Consider parallelizing UI features",
"auth-003 may need more time due to OAuth"
]
}
100 features
SIMPLE Pipeline:
1. Plan → 2. Implement → 3. Verify
STANDARD Pipeline:
1. Analyze → 2. Plan → 3. Test Design
4. Implement → 5. Test → 6. Review → 7. Verify
COMPLEX Pipeline:
1. Deep Analyze → 2. Architecture → 3. Plan
4. Test Design → 5. Implement → 6. Test
7. Integration → 8. Review → 9. Verify
cost = (features * avg_tokens_per_feature * cost_per_token)
+ (sessions * session_overhead)
+ (complexity_multiplier * base_cost)
See scripts/complexity_assessor.py for full implementation.
development
Setup secure web-based terminal access to WSL2 from mobile/tablet via ttyd + ngrok/Cloudflare/Tailscale. One-command install, start, stop, status. Use when you need remote terminal access, web terminal, browser-based shell, or mobile access to WSL2 environment.
development
Complete development workflows where Claude writes the code while Gemini and Codex provide research, planning, reviews, and different perspectives. Claude remains the main developer. Use for complex projects requiring expert planning and multi-perspective reviews.
development
Systematic progress tracking for skill development. Manages task states (pending/in_progress/completed), updates in real-time, reports progress, identifies blockers, and maintains momentum. Use when tracking skill development, coordinating work, or reporting progress.
testing
Comprehensive testing workflow orchestrating functional testing, example validation, integration testing, and usability assessment. Sequential workflow for complete skill testing from examples through scenarios to integration validation. Use when conducting thorough testing, pre-deployment validation, ensuring skill functionality, or comprehensive quality checks.