agentsclimarketplace
Sign in

Team collaboration standup notes

Skill ulpi-io/plugin-marketplace/plugins/sickn33/skills/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.From its SKILL.md

Install
npx -y skills add ulpi-io/plugin-marketplace --skill team-collaboration-standup-notes

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.1 KB, 348 tokens by cl100k_base, as published. Nobody here has run it

Standup Notes Generator

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.

Use this skill when

  • Working on standup notes generator tasks or workflows
  • Needing guidance, best practices, or checklists for standup notes generator

Do not use this skill when

  • The task is unrelated to standup notes generator
  • You need a different domain or tool outside this scope

Context

Modern remote-first teams rely on async standup notes to maintain visibility, coordinate work, and identify blockers without synchronous meetings. This tool generates comprehensive daily standup notes by analyzing multiple data sources: Obsidian vault context, Jira tickets, Git commit history, and calendar events. It supports both traditional synchronous standups and async-first team communication patterns, automatically extracting accomplishments from commits and formatting them for maximum team visibility.

Requirements

Arguments: $ARGUMENTS (optional)

  • If provided: Use as context about specific work areas, projects, or tickets to highlight
  • If empty: Automatically discover work from all available sources

Required MCP Integrations:

  • mcp-obsidian: Vault access for daily notes and project updates
  • atlassian: Jira ticket queries (graceful fallback if unavailable)
  • Optional: Calendar integrations for meeting context

Instructions

  • Clarify goals, constraints, and required inputs.
  • Apply relevant best practices and validate outcomes.
  • Provide actionable steps and verification.
  • If detailed examples are required, open resources/implementation-playbook.md.

Resources

  • resources/implementation-playbook.md for detailed patterns and examples.

What ships with it: 1 file

30.2 KB alongside SKILL.md

resources/

Gives 0 of the 12 instructions most note taking skills give in 348 tokens

Counted across 632 of the 857 authors here whose files we hold, read 2026-09-06

  • Use standard Markdown links for external URLsin 16 of 632, across 8 files
  • Use wikilinks for internal vault connectionsin 15 of 632, across 7 files
  • Embed content using the exclamation mark prefixin 14 of 632, across 6 files
  • Ask for clarification if the user request is ambiguousin 13 of 632
  • Add frontmatter properties at the top of the filein 12 of 632, across 4 files
  • Verify note renders correctly in reading viewin 12 of 632, across 4 files
  • Include a visual element on every slidein 11 of 632, across 5 files
  • Left-align body text and listsin 11 of 632, across 5 files
  • Maintain 0.5 inch minimum marginsin 11 of 632, across 5 files
  • Wrap formulas containing double quotes in single quotesin 11 of 632, across 5 files
  • Repeat one distinctive visual motif across all slidesin 10 of 632, across 4 files
  • Use 36pt or larger for slide titlesin 10 of 632, across 4 files

Said here and by no other author read

  • Clarify goals and constraints
  • Apply best practices
  • Validate outcomes
  • Provide actionable steps
  • Provide verification steps
  • Open implementation playbook for examples

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.