CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

context-manager

Organiza contexto, tarefas e handoff entre sessoes. Trigger em: "criar tarefa", "lista de tarefas", "status", "progresso", "trocar foco", "resetar contexto", "o que falta", "proxima tarefa", "historico", "pipeline de tarefas".

Quality

72%

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 ./skills/08-context-manager/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 body is a lean, well-sectioned governance document with a concrete task lifecycle and an explicit verification checkpoint with failure handling. Its main gaps are the absence of examples or templates for its core outputs (task list entries, handoff summaries) and heavy dependence on policy/template files that are not shipped in the bundle, which weakens both actionability and progressive disclosure.

Suggestions

Add a minimal inline example of the two core artifacts — one task list entry and a short handoff summary — so the skill's primary outputs are concrete rather than described.

Inline the few operative rules from the referenced policies (or ship the policies/templates inside the bundle) so references resolve; as written, GLOBAL.md, five policies/*.md and templates/handoff.md are all dangling.

Trim the 'Skills Utilitarias' section to the YAML snippet and the when-to-apply rule; the mem9 attribution and rationale paragraph are context that does not earn its tokens.

DimensionReasoningScore

Conciseness

The body is written as terse bullet lists and short sections with no explanation of concepts Claude already knows — 'titulo no imperativo e curto', 'no maximo 15 tarefas ativas', 'uma tarefa in_progress por vez'. Minor trimming is possible: the 'Skills Utilitarias' section spends ~10 lines on a pattern attribution to mem9 that is not needed to execute, and 'Saidas Esperadas' overlaps with 'Evidencia de Conclusao'. That level of slack matches 'efficient; minor instances of over-explanation' rather than the 'several unnecessary explanations' of anchor 2/3 territory.

4 / 5

Actionability

There is real concrete guidance — the task state machine ('Criar item (pending) -> Atualizar para in_progress -> ... -> completed -> Revisar lista'), specific limits (max 15 tasks, one in_progress), concrete persistence paths ('docs/context/current-focus.md', 'docs/context/history.md') and a copy-ready YAML frontmatter snippet. However, the skill's primary deliverables — a task list entry and a handoff summary — have no example or template (the referenced templates/handoff.md is not in the bundle), leaving key details missing. This lands on 'some concrete guidance but incomplete' rather than 'mostly executable with minor gaps'.

3 / 5

Workflow Clarity

The task lifecycle is an explicit, ordered sequence, and it includes a genuine validation checkpoint with error recovery: 'Checkpoint antes de marcar completed: confirmar que a evidencia de conclusao ... existe de fato' plus failure handling ('a tarefa volta pra in_progress com a razao anotada'). It falls short of anchor 5 because the wider workflow — focus change, persistence, handoff — is presented as parallel bullet sections rather than one end-to-end sequenced flow with checkpoints, and the lifecycle itself is a single arrow line rather than a numbered procedure.

4 / 5

Progressive Disclosure

The single-file body is well-sectioned with clear headers, but every cross-reference it makes — GLOBAL.md, policies/execution.md, policies/persistence.md, policies/token-efficiency.md, policies/handoffs.md, policies/evals.md, policies/verification-before-completion.md, templates/handoff.md — points to files that are not present in this skill's bundle, so the navigation layer cannot be verified and the skill is not self-contained. With no bundled references and a ~120-line body (above the 50-line simple-skill exception), this is 'some structure but could be better organized' rather than good or clear one-level-deep disclosure.

3 / 5

Total

14

/

20

Passed

Description

66%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 has a solid, explicit trigger list with natural user phrasing and correctly separates the what from the when. Its main weaknesses are a thin capability statement built on one generic verb, and several overly generic trigger terms ("status", "progresso", "historico") that raise conflict risk with sibling skills.

Suggestions

Expand the capability sentence into 3-4 concrete actions (e.g., 'cria e atualiza listas de tarefas, resume estado atual, registra mudanca de foco, gera handoff entre sessoes') instead of the single verb 'organiza'.

Qualify or remove the generic triggers 'status', 'progresso' and 'historico' (e.g., 'status das tarefas', 'historico de contexto') so they do not fire for unrelated progress-reporting skills.

Add a few missing natural variations users would say, such as 'to-do', 'checklist', 'salvar contexto' or 'resumo da sessao', to round out trigger coverage.

DimensionReasoningScore

Specificity

The description names its domain and a small set of actions — "Organiza contexto, tarefas e handoff entre sessoes" — but relies on a single generic verb ("organiza") applied to three objects rather than listing several concrete actions. It matches the anchor 'names domain and 1-2 concrete actions, but not comprehensive'; it is above 'actions are minimal or generic' because 'handoff entre sessoes' is a concrete deliverable, and below 'lists several specific actions' because no distinct verbs or capabilities are enumerated.

3 / 5

Completeness

Both parts are present: the 'what' ("Organiza contexto, tarefas e handoff entre sessoes") and an explicit 'when' via the trigger list ("Trigger em: ..."). It does not reach anchor 5 because the 'what' is a single thin sentence without the enumerated capabilities seen in the top anchor, whereas anchor 4 ('both what and when; when could be more explicit') is surpassed — the when-clause is quite explicit.

4 / 5

Trigger Term Quality

Ten natural trigger phrases are listed ("criar tarefa", "lista de tarefas", "trocar foco", "resetar contexto", "o que falta", "proxima tarefa", "historico", "pipeline de tarefas") — phrasings a user would plausibly say, with some synonym coverage. It falls short of comprehensive (anchor 5) because common variations like "to-do", "checklist", "salvar contexto" or "resumo da sessao" are absent, while generic terms like "status" and "progresso" are included.

4 / 5

Distinctiveness Conflict Risk

Triggers like "criar tarefa", "trocar foco" and "resetar contexto" point clearly at a context/task-management skill, but the list also contains broadly applicable terms — "status", "progresso", "historico" — that any progress-reporting or orchestration skill would also match. This is 'somewhat specific but could still overlap with similar skills'; it is not 'mostly distinct' (anchor 4) because those generic terms create real conflict risk.

3 / 5

Total

14

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

felvieira/claude-skills-fv

Path

skills/08-context-manager/SKILL.md

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.