CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

daily-standup

Análise completa de status e planejamento diário usando Notion MCP

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 ./skills/workflow/daily-standup/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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-structured instruction skill with a clear step sequence, concrete filter criteria, and a copy-paste output template. Its main weakness is actionability: the Notion MCP integration is described by intent rather than by executable specifics (no tool names, no example queries), which leaves the executor to invent the mechanics. Consolidating the repeated date rules and adding one worked example query would raise it without growing the token budget much.

Suggestions

Name the actual Notion MCP tools to call, or give one worked example query per task category (atrasadas / em andamento / não iniciadas com atraso), so the collection step is executable rather than inferred.

Collapse the four restatements of the date rule into a single line (e.g., "SEMPRE usar datetime.now() — nunca datas fixas, de commits ou assumidas") to reclaim tokens and tighten conciseness toward 5.

Add a short fallback branch for when Notion MCP is unavailable or returns no tasks (e.g., proceed from conversation context and say so in the Resumo Executivo), which would add the missing validation/feedback loop to the workflow.

DimensionReasoningScore

Conciseness

The body is terse throughout — short bullets, a compact response template, and no explanations of concepts Claude already knows. The only trimmable padding is the '⚠️ OBRIGATÓRIO' block, which restates a single date rule four ways ("SEMPRE captar a data atual", "NUNCA usar datas fixas", "NUNCA usar datas de commits", "SEMPRE usar a data real"), plus a checklist that largely duplicates the process section. That is minor over-explanation fitting anchor 4 rather than the mostly-lean-but-tightenable anchor 3.

4 / 5

Actionability

There is genuinely concrete guidance — the Notion queries are specified by filter criteria ("data final < hoje e status != concluído", "data inicial < hoje e não está em andamento") and the response format is a copy-paste markdown template. However, the MCP steps name no actual tools, databases, or example queries (e.g., which Notion tool to call or how to filter), and "Analisar contexto: logs recentes (logs/)" gives no commands. This lands between 'mostly executable' (4) and incomplete — missing key execution details keeps it at 3.

3 / 5

Workflow Clarity

A clear four-step sequence (Solicitar Contexto → Coletar Informações → Análise Profunda → Proposta de Cronograma) is followed by a checklist that serves as an explicit end-of-run checkpoint, matching anchor 4's 'clear sequence with most checkpoints present'. It is not a 5 because there is no feedback loop or fallback (e.g., what to do when Notion MCP returns nothing or is unavailable), and 'Análise Profunda' overlaps with 'Proposta de Cronograma'. This is a read-only analysis skill, so the destructive/batch validation cap does not apply.

4 / 5

Progressive Disclosure

There are no bundle files and none are needed — all content is appropriately inline for a ~110-line single-purpose skill, with well-signaled sections (Quando Usar, Processo Obrigatório, Formato de Resposta, Checklist) that make navigation easy. This fits anchor 4's 'good structure; most content appropriately placed'. It does not reach 5 because the body exceeds the under-50-line simple-skill threshold and the process sections could be organized more tightly (the date rules and checklist are structurally redundant).

4 / 5

Total

15

/

20

Passed

Description

50%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 is serviceable but flat: it states a clear 'what' (status analysis and daily planning via Notion MCP) at a mid-level of specificity, but omits any 'when to use' guidance and only partially covers the natural trigger phrases a user would say. All four dimensions land at the midpoint for the same root cause — brevity without the complementary trigger/usage information.

Suggestions

Append an explicit trigger clause, e.g. "Use quando o usuário pedir 'fazer daily', 'standup', 'review de status' ou 'planejamento do dia'" — this lifts both completeness and trigger term quality.

Add 1-2 more specific capability phrases to the description (e.g., "busca tarefas atrasadas e em andamento no Notion e propõe cronograma com prioridades") to move specificity from named-domain toward comprehensive.

Include synonyms users naturally say ("daily", "standup", "rotina", "checklist do dia") so the description itself carries the trigger coverage instead of relying on the separate frontmatter triggers field.

DimensionReasoningScore

Specificity

The description names the domain and two concrete actions — "Análise completa de status" and "planejamento diário" — plus the tool ("usando Notion MCP"), matching the anchor for 1-2 concrete actions without comprehensive coverage. It does not list several specific actions (e.g., what the analysis produces or covers), so it is not a 4, and the actions are genuinely named rather than generic, so it is above a 2.

3 / 5

Completeness

It answers 'what' clearly (complete status analysis and daily planning via Notion MCP) but contains no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3. Not a 4 because 'when' is entirely absent rather than just under-specified.

3 / 5

Trigger Term Quality

Terms like "status", "planejamento diário", and "análise" are natural phrases a user might say, but common variations and synonyms such as "standup", "daily", "rotina", or "review de status" are absent from the description itself. This fits the 'some relevant keywords but missing common variations' anchor; it is not a 4 because several natural trigger phrases users would actually say are missing.

3 / 5

Distinctiveness Conflict Risk

Mentioning Notion MCP gives the skill a partial niche, but the broad terms "status", "planejamento", and "análise" overlap with generic planning, review, and productivity skills, so it could still trigger for the wrong skill. This matches the 'somewhat specific but could still overlap' anchor rather than the mostly-distinct anchor 4.

3 / 5

Total

12

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

fernandezbaptiste/cursor-multiagent-system

Path

skills/workflow/daily-standup/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.