CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

handoff-context

Prepara contexto e pendencias para outra sessao ou agente. Trigger em: "handoff", "passar bastao", "passar o bastao", "delega pra outro", "delega isso", "transfer context", "passar contexto", "outro dev vai pegar", "outro agente vai continuar", "preciso passar isso", "briefing prospectivo", "sessao fresh", "preparar handoff", "monta o pacote".

Quality

83%

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

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 strong, highly actionable instruction skill: exact commands, a complete output template, an explicit verify-now checkpoint, and per-target handoff prompts. Its only weaknesses are minor — trimmable provenance/explanatory asides and inlined content (cross-vendor section, comparison table) that could be split into reference files. No bundle files are provided, so progressive disclosure rests entirely on the body's own organization, which is good but not optimally split.

DimensionReasoningScore

Conciseness

Directives are lean and imperative ('Nao gerar roadmap. **Um proximo passo concreto**', 'Nao gerar roadmap' anti-pattern list), but there is minor trimmable material: provenance commentary ('Inspiracao: [mattpocock/skills...] (MIT)', 'conceito absorvido, texto reescrito') and the explanatory prose in the cross-vendor section. This fits anchor 4 (efficient with minor instances of over-explanation) rather than 5, since those tokens do not change what Claude does.

4 / 5

Actionability

Fully executable throughout: copy-paste commands ('git status --short', 'git branch --show-current', 'git log --oneline -5'), a complete fill-in output template with frontmatter and exact output path ('docs/handoffs/YYYY-MM-DD-<slug>.md'), and concrete per-target handoff prompts ('prompt = conteudo do .md salvo + "Continue daqui"'). Matches anchor 5 — the common cases (agent, human, fresh session) are all covered with copy-paste-ready material.

5 / 5

Workflow Clarity

Clear five-step sequence (snapshot -> pendencias verificadas -> proximo passo unico -> armadilhas -> output) with an explicit verification checkpoint: 'cada item vem de rodar o comando agora, nao de memoria da sessao (a suite pode ter passado 20 mensagens atras e quebrado desde)'. A decision rule for ambiguous next steps ('escolher o mais bloqueador ou pedir AskUserQuestion') and an anti-patterns checklist add error-recovery guidance, matching anchor 5. The workflow is documentation-generation, not destructive/batch, so the validation cap does not apply — and verification is nonetheless explicit.

5 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, or assets/ directories), so this scores on in-body structure: sections are well-organized and external references are clearly signaled ('Segue `GLOBAL.md`, `policies/handoffs.md` (canonica), `policies/persistence.md`...'). It stops short of anchor 5 because at ~170 lines the cross-vendor section and the skill-31 comparison table are self-contained chunks that could live in one-level-deep reference files, keeping SKILL.md a tighter overview.

4 / 5

Total

18

/

20

Passed

Description

72%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 excellent trigger coverage and an explicit 'when' clause, but its capability statement is generic — a reader cannot tell what a handoff package actually contains. It is clearly distinct from adjacent skills only in its trigger phrasing, not in its stated function. Strengthening the 'what' with 2-3 concrete deliverables would lift both specificity and completeness.

Suggestions

Replace the generic 'Prepara contexto e pendencias' with the concrete deliverables, e.g. 'Gera pacote de handoff com snapshot do estado do git (branch, modificados, ultimos commits), pendencias verificadas rodando comandos agora, e UM proximo passo executavel, salvo em docs/handoffs/YYYY-MM-DD-<slug>.md'.

Name the target audiences in the description (outro agente / dev humano / sessao fresh) so the 'what' answers who consumes the output, matching what the body already specifies.

Add one distinguishing phrase to the description itself (e.g. 'prospectivo — o que falta, nao o que foi feito') to reduce overlap with retrospective-summary skills without requiring the body's comparison table.

DimensionReasoningScore

Specificity

The capability statement 'Prepara contexto e pendencias para outra sessao ou agente' names the handoff domain but its actions are minimal and generic — it never mentions the git state snapshot, the single-next-step rule, the pitfalls log, or the output file format that the skill actually produces. It fits anchor 2 ('names the domain but actions are minimal or generic') rather than 3, because no concrete action beyond the near-tautological 'prepare context and pendings' is stated.

2 / 5

Completeness

Both parts are present: a 'what' ('Prepara contexto e pendencias para outra sessao ou agente') and an explicit 'when' ('Trigger em: ...' with concrete trigger phrases), so the missing-trigger cap of 3 does not apply. It falls short of anchor 5 because the 'what' is vague — it does not say what the handoff package contains (setup commands, verified state, one next step) or who the targets are.

4 / 5

Trigger Term Quality

Fourteen natural trigger phrases with comprehensive coverage including Portuguese/English synonyms and variations ('handoff', 'passar bastao', 'passar o bastao', 'delega pra outro', 'transfer context', 'outro agente vai continuar', 'preparar handoff', 'monta o pacote', 'sessao fresh'). This matches anchor 5 — the natural terms a user would actually say are all present.

5 / 5

Distinctiveness Conflict Risk

Niche-specific triggers like 'passar bastao' and 'outro agente vai continuar' give it a clear niche, but broader phrases ('delega isso', 'transfer context', 'preciso passar isso') carry minor overlap risk with generic delegation or context-transfer skills, and the description does not state what distinguishes it from a retrospective session summary. Anchor 4 ('mostly distinct; minor overlap risk with closely related skills') is the best fit.

4 / 5

Total

15

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

metadata_version

'metadata.version' is missing

Warning

Total

14

/

16

Passed

Repository

felvieira/claude-skills-fv

Path

skills/45-handoff-context/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.