CtrlK
BlogDocsLog inGet started
Tessl Logo

daily-meeting-update

Interactive daily standup/meeting update generator. Use when user says 'daily', 'standup', 'scrum update', 'status update', 'what did I do yesterday', 'prepare for meeting', 'morning update', or 'team sync'. Pulls activity from GitHub, Jira, and Claude Code session history. Conducts 4-question interview (yesterday, today, blockers, discussion topics) and generates formatted Markdown update.

81

1.20x
Quality

75%

Does it follow best practices?

Impact

89%

1.20x

Average score across 3 eval scenarios

SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./dist/plugins/daily-meeting-update/skills/daily-meeting-update/SKILL.md

The canonical home for this skill is daily-meeting-update in softaworks/agent-toolkit

SKILL.md
Quality
Evals
Security

Quality

Content

56%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 content is actionable and well-sequenced with real validation checkpoints, but it is padded: the workflow is restated four different ways. Splitting the example session, output template, and anti-patterns into reference files would improve token efficiency and progressive disclosure.

Suggestions

Consolidate the redundant workflow representations: pick either the ASCII diagram or the prose phases, and drop the duplicate Quick Reference table to cut the body length substantially.

Move the Example Session, Output Example, and Anti-Patterns sections into separate reference files (e.g., examples.md, anti-patterns.md) and link them one level deep, reducing inline bulk.

Add explicit error-recovery steps for gh/jira data pulls (not just the digest script) so every external-data source has a uniform validate->fix->retry or graceful-fallback loop.

DimensionReasoningScore

Conciseness

Noticeably verbose for a single-purpose skill: the same workflow is restated via an ASCII diagram, three phase sections, a Quick Reference table, an Example Session, and an Output Example, creating substantial redundancy. Not a 1 because it avoids re-explaining concepts Claude already knows; not a 3 because the repetition across four representations exceeds 'some unnecessary explanation'.

2 / 5

Actionability

Provides concrete executable commands ('ls ~/.claude/projects/*/*.jsonl 2>/dev/null | head -1', 'python3 .../claude_digest.py --format json', 'gh auth status'), specific interview prompts with options, and a copy-paste output template with minor gaps. Not a 5 because the digest logic itself is externalized to the bundle script and several prompts are conversational rather than fully executable code.

4 / 5

Workflow Clarity

Three phases are clearly sequenced with an explicit diagram and validation checkpoints (consent-before-access gating, explicit digest-script failure fallback, 'Do NOT run digest script when...'). Not a 5 because error-recovery feedback loops are spelled out only for the digest script, while gh/jira pull-failure handling remains implicit.

4 / 5

Progressive Disclosure

The single bundle reference (scripts/claude_digest.py) is real and cleanly one-level, but substantial content that could live in separate files (Example Session, Output Example, Anti-Patterns) is inlined into SKILL.md. Not a 4 because the inlining is more than minor organization gaps.

3 / 5

Total

13

/

20

Passed

Description

95%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 strong: it clearly states what the skill does, when to invoke it via natural trigger phrases, and stays in third person. Minor specificity gap in 'Pulls activity' being broad, but overall a high-quality, distinctive description.

DimensionReasoningScore

Specificity

Lists several concrete actions ('Pulls activity from GitHub, Jira, and Claude Code session history', 'Conducts 4-question interview (yesterday, today, blockers, discussion topics)', 'generates formatted Markdown update') with only minor coverage gaps; not a 5 because 'Pulls activity' remains somewhat broad.

4 / 5

Completeness

Explicitly answers both 'what' (interactive standup generator conducting a 4-question interview producing formatted Markdown) and 'when' (concrete 'Use when user says...' trigger phrases).

5 / 5

Trigger Term Quality

Comprehensive natural trigger coverage including synonyms and a full quoted phrase list ('daily', 'standup', 'scrum update', 'status update', 'what did I do yesterday', 'prepare for meeting', 'morning update', 'team sync') that users would naturally say.

5 / 5

Distinctiveness Conflict Risk

Clear niche (daily standup/meeting update) with distinctive triggers ('standup', 'scrum update') and minimal conflict risk; third-person voice is consistent, no penalty applies.

5 / 5

Total

19

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
softaworks/agent-toolkit
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.