CtrlK
BlogDocsLog inGet started
Tessl Logo

daily-standup-journal

Generate concise daily standups, reflection prompts, and weekly retrospectives for individuals or teams. Use for planning a day, surfacing blockers, reviewing user-provided entries, or drafting a check-in without assuming prior history.

60

Quality

76%

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

A well-structured, actionable instruction-only skill with a clear sequenced workflow and explicit validation for the destructive-ish log-writing path. The main weakness is mild redundancy between prompt tables, sample sessions, and the quality-checks section.

Suggestions

Remove or compress the Sample Sessions section since its output blocks restate the prompt tables already shown under each Session Type.

Fold the standalone Quality checks list into the relevant steps (3-5) to eliminate restated guidance and reduce length.

Make the error-recovery feedback loop explicit in Step 4 (e.g., 'If the user declines the export, return to in-session output') to lift workflow clarity toward 5.

DimensionReasoningScore

Conciseness

The body is mostly efficient (tight tables, no explainer concepts Claude lacks), but the Sample Sessions restate the prompt tables and the Quality checks restate Step 3-5 guidance, so it could be tightened.

3 / 5

Actionability

Concrete prompt sets, a trigger-phrase-to-action table, a 5-step process, and copy-ready output templates give mostly executable guidance; not a 5 because some guidance stays at the prompt-template level rather than fully worked examples.

4 / 5

Workflow Clarity

A clear 5-step sequence (identify type, generate prompts, process responses, offer export, surface actions) with explicit validation before writing/sharing (Step 4) and a closing Quality checks checklist; just short of 5 because error-recovery feedback loops are only implicit.

4 / 5

Progressive Disclosure

Well-organized with clear section headers across session types, triggers, steps, samples, and checks; as a single inline file with no external references it is appropriately structured, though the 5 session templates could conceivably be split out.

4 / 5

Total

15

/

20

Passed

Description

75%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.

A strong, third-person description that concretely states capabilities and use cases with clear trigger guidance. It is well above the midpoint on every dimension but stops short of comprehensive, copy-natural trigger-phrase coverage.

DimensionReasoningScore

Specificity

"Generate concise daily standups, reflection prompts, and weekly retrospectives" names the domain plus several concrete actions; not a 5 because coverage is not comprehensive (e.g., monthly themes from the body are absent).

4 / 5

Completeness

It explicitly states both what ("Generate concise daily standups, reflection prompts, and weekly retrospectives") and when ("Use for planning a day, surfacing blockers..."); the when-scenarios are explicit but framed as use cases rather than the exact trigger phrases a user would say.

4 / 5

Trigger Term Quality

"Use for planning a day, surfacing blockers, reviewing user-provided entries, or drafting a check-in" gives good natural keyword coverage; a few common phrases from the body ("weekly retro", "evening journal", "morning pages") are missing.

4 / 5

Distinctiveness Conflict Risk

The standup/retro/journal framing is a clear niche distinct from generic productivity skills; minor overlap risk with broad journaling skills keeps it just below 5.

4 / 5

Total

16

/

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
iflytek/skillhub
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.