context-manager

Skill de gerenciamento de contexto e tarefas usando o mecanismo de task, memoria ou checklist disponivel no ambiente, com persistencia enxuta entre sessoes quando fizer sentido. Use quando precisar organizar tarefas, acompanhar progresso, trocar foco de trabalho, ou manter historico resumido. Trigger em: "criar tarefa", "lista de tarefas", "status", "progresso", "trocar foco", "resetar contexto", "o que falta", "proxima tarefa", "historico", "pipeline de tarefas".

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/08-context-manager/SKILL.md

Quality

Content

50%Weight 40%Scale 1-3

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

A lean, well-structured instruction-only skill that avoids padding and gives concrete rules, but it stays directional on its core mechanism and lacks explicit validation checkpoints for context resets. No bundle files exist, so progressive disclosure rests on the single inline document plus external kit references.

Suggestions

Merge the overlapping Quando Usar / Entradas Esperadas / Saidas Esperadas / Responsabilidades sections into one to remove redundancy and reclaim tokens.

Add an explicit validation/verification checkpoint in the Mudanca de Foco and resetar-contexto flows (e.g. confirm nothing important is dropped before archiving the prior context).

Move the sub-skill utilitaria (context: fork) pattern into a referenced file and keep only a one-line pointer in SKILL.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with terse bullets and no explaining of concepts Claude already knows, but "Quando Usar", "Entradas Esperadas", "Saidas Esperadas", and "Responsabilidades" overlap noticeably and could be consolidated.	2 / 3
Actionability	Gives some concrete rules and paths ("no maximo 15 tarefas ativas", "docs/context/current-focus.md", a context:fork YAML snippet), but the core operation "Usar o mecanismo disponivel no ambiente" stays directional rather than copy-paste executable.	2 / 3
Workflow Clarity	The task lifecycle (pending -> in_progress -> completed -> revisar) and the focus-change steps are sequenced, but there are no explicit validation/verification checkpoints for batch or destructive context resets.	2 / 3
Progressive Disclosure	Well-organized into clear sections with one-level-deep signaled references to kit policies and templates, but the skill is a single monolithic file with no own bundle files, and inline content that could be split (e.g. sub-skill pattern) is kept in-body.	2 / 3
	Total	8 / 12 Passed

Description

92%Weight 40%Scale 1-3

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

A strong description with concrete actions, explicit when-to-use guidance, and natural trigger terms in the user's likely phrasing. Its main weakness is distinctiveness — several triggers are generic enough to collide with adjacent planning/orchestration skills.

Suggestions

Narrow the trigger list or add a scoping qualifier so generic terms like "status" / "progresso" / "historico" are less likely to fire this skill when a more specific planning skill exists.

Add one short phrase that distinguishes this skill from the Orquestrador (e.g. emphasize it is the tracking/focus layer, not the decision layer) to reduce conflict risk.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "organizar tarefas", "acompanhar progresso", "trocar foco de trabalho", "manter historico resumido", and persistence between sessions — rather than vague language.	3 / 3
Completeness	Explicitly answers both what ("gerenciamento de contexto e tarefas...") and when ("Use quando precisar organizar tarefas..." plus an explicit "Trigger em" clause), satisfying the both-what-and-when requirement.	3 / 3
Trigger Term Quality	Provides natural trigger phrases a user would actually say: "criar tarefa", "lista de tarefas", "status", "progresso", "o que falta", "proxima tarefa", giving good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	Task/context management is a broad niche and terms like "status", "progresso", "historico" could overlap with other planning or orchestration skills; the triggers help but do not fully isolate it.	2 / 3
	Total	11 / 12 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: felvieira/claude-skills-fv
Path: skills/08-context-manager/SKILL.md
Commit: 030ef22

Reviewed: 8 days ago

Table of Contents

Discovery Implementation Validation

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.