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.

89

1.20x
Quality

88%

Does it follow best practices?

Impact

89%

1.20x

Average score across 3 eval scenarios

SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Discovery

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is an excellent skill description that hits all the marks. It provides specific concrete actions, comprehensive natural trigger terms, explicit 'Use when' guidance, and a clearly defined niche that distinguishes it from other skills. The description is concise yet thorough, using proper third-person voice throughout.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: 'Pulls activity from GitHub, Jira, and Claude Code session history', 'Conducts 4-question interview (yesterday, today, blockers, discussion topics)', and 'generates formatted Markdown update'.

3 / 3

Completeness

Clearly answers both what (interactive standup generator that pulls from multiple sources and conducts interview) AND when (explicit 'Use when user says...' clause with comprehensive trigger phrases).

3 / 3

Trigger Term Quality

Excellent coverage of natural terms users would say: 'daily', 'standup', 'scrum update', 'status update', 'what did I do yesterday', 'prepare for meeting', 'morning update', 'team sync' - these are all phrases users would naturally use.

3 / 3

Distinctiveness Conflict Risk

Clear niche focused on standup/meeting updates with specific integrations (GitHub, Jira, Claude Code) and a defined workflow (4-question interview). Unlikely to conflict with general productivity or code review skills.

3 / 3

Total

12

/

12

Passed

Implementation

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a well-crafted skill with excellent actionability and workflow clarity. The multi-phase process is clearly documented with specific commands, question templates, and comprehensive examples. The main weakness is length—the skill could be more concise by moving reference material (anti-patterns, full example sessions) to separate files and trimming redundant explanations.

Suggestions

Move the detailed 'Example Session' and 'Anti-Patterns' sections to a separate REFERENCE.md file, keeping only a brief summary in the main skill

Remove the ASCII workflow diagram since the detailed phase descriptions already cover the same information more thoroughly

DimensionReasoningScore

Conciseness

The skill is reasonably efficient but includes some redundancy (e.g., the workflow diagram duplicates the detailed phase descriptions, and some explanations like 'This integration captures everything you worked on with Claude Code' are unnecessary). The anti-patterns table and NEVER section add value but could be more condensed.

2 / 3

Actionability

Provides fully executable bash commands, specific detection methods, exact question wording with options, complete output format examples, and a detailed example session showing the full flow. Copy-paste ready throughout.

3 / 3

Workflow Clarity

Excellent multi-step workflow with clear phases, explicit validation points (ask before pulling, user selects relevant items), and feedback loops (fallback if digest script fails, follow-up questions for vague responses). The ASCII diagram and phase breakdown make sequencing unambiguous.

3 / 3

Progressive Disclosure

Content is well-structured with clear sections, but the skill is quite long (~350 lines) and could benefit from splitting detailed content (like the full example session, anti-patterns table) into separate reference files. References to external script exist but inline content is heavy.

2 / 3

Total

10

/

12

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

Passed

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.