Assesses task difficulty by analyzing scope, risk and codebase context, producing a scored report.
npx skills add https://github.com/YuluoY/nimis --skill task-difficulty
Please help me install this Agent Skill. Skill: task-difficulty Source: https://github.com/YuluoY/nimis/tree/main/skills-en/task-difficulty Command: npx skills add https://github.com/YuluoY/nimis --skill task-difficulty
Task difficulty assessment throttle — identifies and clips under- or over-estimation of task complexity by analyzing user requirements and the surrounding project context. It traces relevant files, modules, dependencies, and risk signals to produce a calibrated difficulty appraisal.
Describe your task in one sentence and run the assessor to generate the difficulty report.
High-intent search queries and answers about installing and using this skill.
Assess task difficulty by analyzing user requirements and project context to prevent misestimation. The process traces relevant files, modules, and dependencies, applying multi-dimensional scoring and an upward-bias throttle to produce a calibrated difficulty appraisal.
Multi-dimensional scoring evaluates task complexity across Scope, Depth, Coupling, Risk, and Cognition. This mechanism scores each dimension individually, then applies an upward-bias throttle to the weighted total to accurately reflect real-world execution effort.
Context tracing identifies impacted areas, dependencies, and risk signals by analyzing project files and modules. You need this process before coding begins to expose potential risks and accurately calibrate the scope of your user requirement.
Yes, you can use automated difficulty analysis as a prerequisite gate before task execution. It functions flexibly as a standalone assessment or an automated pipeline gate, generating a Difficulty Assessment Report via CLI to guide planning and risk awareness.
The Difficulty Assessment Report includes a weighted score, the final difficulty level after throttle bias, rationale, and contextual findings. These outputs provide the necessary data for project planning and proactive risk assessment.
The upward-bias throttle intentionally clips underestimation by shifting the weighted score upward to reflect real-world effort. You should not use this throttled score as an absolute minimum limit if your project context already contains highly accurate, historically calibrated baseline metrics.
yuchenzhu-researchDiagnose TOEFL writing samples with a five-dimension ETS-aligned report.
Hopin-incCreate phased delivery plans with dependencies, milestones, and feature-flag gating.
atholaEvaluate artifacts using weighted criteria and threshold-based decision rules.
VictorSmaniottoAnalyze PHP code for smells, complexity, duplications, and pattern violations.
