standup-meeting
Run Effective Daily Standups
Teams lose focus when standups become long status meetings. This skill structures updates, blockers, action items, and async check-ins.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "standup-meeting" from https://skillstore.io/skills/supercent-io-standup-meeting.md and its manifest at https://skillstore.io/api/skills/supercent-io-standup-meeting/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "standup-meeting". Run a standup for a team working on authentication, profile pages, and database migration.
Expected outcome:
A concise standup agenda with each member's yesterday, today, and blockers sections, plus action items for access and documentation.
Using "standup-meeting". Summarize a standup where one story is blocked by production database access.
Expected outcome:
A meeting summary that lists sprint progress, the blocked database migration, the owner, the expected resolution time, and follow-up tasks.
Using "standup-meeting". Create an async update format for a remote team.
Expected outcome:
A chat-ready daily update template with sections for completed work, planned work, blockers, and current sprint progress.
Security Audit
SafeThe static external command findings are false positives caused by markdown code fences and inline tags in documentation examples. The network findings are ordinary reference links, and the blocker findings are standup section headings with no reconnaissance behavior. No prompt injection, malicious intent, command execution, or data exfiltration evidence was found.
Risk Factors
⚙️ External commands (9)
🌐 Network access (2)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/supercent-io-standup-meeting/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/supercent-io-standup-meeting?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/supercent-io-standup-meeting?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/supercent-io-standup-meeting/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/supercent-io-standup-meeting.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
supercent-io. (2026). standup-meeting security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/supercent-io-standup-meeting/audits/5BibTeX citation
@techreport{supercent-io-supercent-io-standup-meeting-2026,
author = {supercent-io},
title = {standup-meeting security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/supercent-io-standup-meeting/audits/5},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "standup-meeting security audit report (audit version 5)"
version: "unspecified"
type: report
authors:
- name: "supercent-io"
date-released: "2026-07-07"
url: "https://skillstore.io/skills/supercent-io-standup-meeting/audits/5"
identifiers:
- type: other
value: "skillstore:supercent-io-standup-meeting:audit:5"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Facilitate a Daily Scrum
Run a short meeting that captures yesterday's work, today's plan, and current blockers.
Coordinate Remote Updates
Create a concise async standup format for distributed team members in different time zones.
Track Sprint Blockers
Summarize blocked work, assign owners, and record follow-up action items after the standup.
Try These Prompts
Help me run today's daily standup for a five-person agile team. Use the three-question format and capture action items.
Create an async standup template for my remote team. Include yesterday, today, blockers, and sprint progress.
Facilitate a board-based standup using these columns: In Progress, Blocked, Ready for Review, and Done. Summarize risks and owners.
Turn these standup notes into minutes with a summary, individual updates, blockers, decisions, and prioritized action items.
Best Practices
- Keep the meeting time-boxed to 15 minutes.
- Move detailed problem solving to a separate follow-up discussion.
- Record blocker owners and due times before the meeting ends.
Avoid
- Turning the standup into a manager status report.
- Letting technical debates consume the meeting.
- Ending without owners for urgent blockers.
Frequently Asked Questions
What meeting format does this skill support?
Can it help with remote teams?
Does it connect to project management tools?
How does it handle blockers?
Is this only for Scrum teams?
Can Claude, Codex, or Claude Code use it?
Developer Details
Author
supercent-ioLicense
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
36e07d5e13068e5be64447e8f20b427cf2cbd21a
Maintenance freshness
7/18/2026
Usage
7 downloads · 150 views
File structure
📄 SKILL.md