team-collaboration-standup-notes

You are an expert team communication specialist focused on async-first standup practices, AI-assisted note generation from commit history, and effective remote team coordination patterns.

Quality

23%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/team-collaboration-standup-notes/SKILL.md

Quality

Content

11%Scale 1-5

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

This skill is a thin template with almost no actionable content. The instructions are entirely generic boilerplate that could apply to any domain, providing no concrete guidance on how to actually generate standup notes from commit history, Jira, or Obsidian vaults. The skill mentions MCP integrations but never shows how to use them, and defers all substance to a referenced file that doesn't exist in the bundle.

Suggestions

Replace the generic Instructions bullets with a concrete step-by-step workflow: (1) query git log via shell, (2) query Jira via atlassian MCP, (3) read Obsidian daily note via mcp-obsidian, (4) format and output standup notes—with actual tool call examples or commands for each step.

Add a concrete output template showing what the generated standup notes should look like (e.g., Yesterday/Today/Blockers format with example entries derived from commits).

Include actual MCP tool call examples (e.g., `mcp-obsidian.search({query: ...})`, `atlassian.jira.search({jql: ...})`) so Claude knows exactly which tools to invoke and with what parameters.

Either provide the referenced `resources/implementation-playbook.md` bundle file or inline the essential patterns and examples directly in the SKILL.md.

Dimension	Reasoning	Score
Conciseness	The skill repeats the description as the opening line, includes unnecessary 'Use this skill when / Do not use this skill when' boilerplate that adds no value, and the Context section over-explains what async standups are—something Claude already knows. The Instructions section is entirely generic filler ('Clarify goals, constraints, and required inputs') rather than domain-specific guidance.	2 / 5
Actionability	The Instructions section contains only vague platitudes ('Apply relevant best practices and validate outcomes', 'Provide actionable steps and verification') with zero concrete code, commands, MCP tool calls, or specific steps for actually generating standup notes. There is no executable guidance whatsoever—no example queries, no data extraction steps, no formatting templates.	1 / 5
Workflow Clarity	There is no discernible workflow or sequence of steps. The instructions are four generic bullet points that could apply to any skill. There are no validation checkpoints, no data gathering sequence (e.g., query git log → query Jira → format output), and no error handling or fallback logic despite mentioning 'graceful fallback if unavailable.'	1 / 5
Progressive Disclosure	The skill references `resources/implementation-playbook.md` for detailed patterns, but no bundle files are provided, making this reference unverifiable and potentially broken. The main file itself contains almost no substantive content to serve as an overview, so the progressive disclosure structure is hollow—it defers to a file that may not exist while providing nothing useful at the top level.	2 / 5
	Total	6 / 20 Passed

Description

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

This description reads more like a persona statement ('You are an expert...') than a skill description, using first/second person framing rather than third person. It identifies a domain but lacks concrete actions, explicit trigger conditions, and natural user-facing keywords. The description would benefit significantly from listing specific capabilities and adding a 'Use when...' clause.

Suggestions

Rewrite in third person with concrete actions, e.g., 'Generates standup notes from git commit history, formats async daily updates, and summarizes team progress for remote coordination.'

Add an explicit 'Use when...' clause with trigger terms like 'standup', 'daily update', 'status report', 'what did I work on yesterday', 'git log summary', 'team sync'.

Remove the persona framing ('You are an expert...') and replace with action-oriented language describing what the skill does and when it should be selected.

Dimension	Reasoning	Score
Specificity	Names the domain (team communication, standups, commit history) but actions are minimal and generic. 'Async-first standup practices' and 'AI-assisted note generation' hint at capabilities but don't list concrete actions like 'generates standup notes from git logs' or 'formats daily updates'.	2 / 5
Completeness	Has a vague 'what' (standup practices, note generation, coordination patterns) but completely lacks a 'when' clause. There is no explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when...' caps completeness at 3, and the 'what' is also weak, so 2 is appropriate.	2 / 5
Trigger Term Quality	Contains some relevant keywords like 'standup', 'commit history', 'async', and 'remote team', but misses natural user phrases like 'daily update', 'status report', 'what did I work on', 'git log summary', or 'team sync'.	3 / 5
Distinctiveness Conflict Risk	Somewhat specific to standup/async communication, but 'team communication' and 'remote team coordination' are broad enough to overlap with general project management or collaboration skills. The commit history angle adds some distinctiveness but isn't strongly delineated.	3 / 5
	Total	10 / 20 Passed

Validation

90%

Warnings & errors only

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

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills/skills/team-collaboration-standup-notes/SKILL.md
Commit: fbdfd63

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.