CtrlK
BlogDocsLog inGet started
Tessl Logo

handle-large-tasks

Use this skill to split large plans into smaller chunks. This skill manages your context window for large tasks. Use it when a task will take a long time and cause context issues.

58

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agency/plugins/nori/skills/handle-large-tasks/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a lean, actionable instruction set for orchestrating subagents on large tasks, with a clear sequence and feedback loops. Its main weaknesses are minor over-explanation of context-window basics and the absence of a concrete example or template for subagent instructions and tests.

Suggestions

Trim or remove the line 'Each subagent has its own limited context window' since Claude already knows this.

Add a brief example of a subagent Task invocation and a sample behavior test so the guidance is copy-paste ready.

Replace the ad-hoc <required> wrapper with a standard markdown section header and an explicit validation checkpoint per subagent.

DimensionReasoningScore

Conciseness

The body is efficient and mostly assumes Claude's competence; only minor lines like 'Each subagent has its own limited context window' restate what Claude already knows.

4 / 5

Actionability

Provides concrete, sequenced guidance (TodoWrite steps, Task tool usage, test-writing responsibility) with minor gaps such as no example test or invocation snippet.

4 / 5

Workflow Clarity

The workflow is a clear sequenced list with explicit feedback loops ('Iterate until tests pass AND the code fits', final integration check), though it stops short of explicit validation checkpoints for each subagent's output.

4 / 5

Progressive Disclosure

For a short single-file skill it is reasonably organized with a required-steps block and a Guidelines section, but the nonstandard <required> tag and bullet-heavy layout leave minor organization gaps.

4 / 5

Total

16

/

20

Passed

Description

58%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description clearly states both what the skill does and when to use it, which is its main strength. However, the capability description is generic and the trigger terms are broad, raising overlap risk with other planning skills.

Suggestions

Replace generic verbs with concrete actions, e.g. 'break a plan into subagent tasks, write per-subagent tests, and orchestrate subagents via the Task tool'.

Add more specific trigger phrasing users would naturally say, such as 'context window is filling up', 'task is too big for one pass', or 'multi-step implementation plan'.

Sharpen distinctiveness by naming the mechanism (subagents + TodoWrite) so it does not collide with general planning skills.

DimensionReasoningScore

Specificity

Names the domain ('split large plans into smaller chunks', 'manages your context window') with one or two concrete actions, but the actions remain generic rather than comprehensive.

3 / 5

Completeness

Answers both what (split plans into chunks, manage context window) and when ('Use it when a task will take a long time and cause context issues'), though the when could be more specific.

4 / 5

Trigger Term Quality

Includes some natural phrases users might say ('large plans', 'large tasks', 'take a long time', 'context issues') but lacks common synonyms or more specific trigger phrasing.

3 / 5

Distinctiveness Conflict Risk

The 'large tasks' framing is broad and could overlap with several planning or agent-orchestration skills, so it is only somewhat distinct.

3 / 5

Total

13

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
microsoft/FluidFramework
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.