Skills standup-formatter
📦

standup-formatter

Content revision r1 Safe ⚙️ External commands

Format Clear Standup Updates

Daily status updates often become too long or vague for fast team coordination. This skill turns work notes into concise standup reports with clear outcomes, focus items, and blockers.

Supports: Claude Codex Code(CC)
🥉 77 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "standup-formatter" from https://skillstore.io/skills/chaiwithjai-standup-formatter.md and its manifest at https://skillstore.io/api/skills/chaiwithjai-standup-formatter/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.

Markdown detail GET /skills/chaiwithjai-standup-formatter.md Signed manifest GET /api/skills/chaiwithjai-standup-formatter/manifest Signed lockfile GET /api/skills/chaiwithjai-standup-formatter/lockfile

Test it

Using "standup-formatter". Merged the auth pull request, reviewed payment API notes, and need backend confirmation on webhook fields.

Expected outcome:

Done: Merged the user auth pull request. Today: Review payment API integration details. Blockers: Need backend confirmation on webhook fields.

Using "standup-formatter". Team notes from Alex, Priya, and Sam with mixed completed work, current focus, and one dependency.

Expected outcome:

A team standup grouped by person, with each update reduced to Done, Today, and Blockers.

Using "standup-formatter". Weekly project notes covering shipped work, planned testing, and a design decision waiting on approval.

Expected outcome:

A project status update that highlights completed outcomes, near-term focus, and the pending design approval.

Security Audit

Safe
v8 • 7/6/2026 Open versioned report

The static findings are false positives caused by Markdown code fences in SKILL.md. I found no shell execution instructions, prompt injection text, or semantic evidence of malicious behavior.

1
Files scanned
112
Lines analyzed
0
Review items
0
False positives ignored

Risk Factors

⚙️ External commands (7)
SKILL.md:35-39 SKILL.md:39-42 SKILL.md:42-47 SKILL.md:47-83 SKILL.md:83-96 SKILL.md:96-100 SKILL.md:100-110
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History →
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.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/chaiwithjai-standup-formatter/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/chaiwithjai-standup-formatter/security.svg)](https://skillstore.io/skills/chaiwithjai-standup-formatter?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/chaiwithjai-standup-formatter?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/chaiwithjai-standup-formatter/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/chaiwithjai-standup-formatter.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

ChaiWithJai. (2026). standup-formatter security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/chaiwithjai-standup-formatter/audits/8

BibTeX citation

@techreport{chaiwithjai-chaiwithjai-standup-formatter-2026, author = {ChaiWithJai}, title = {standup-formatter security audit report (audit version 8)}, institution = {Skillstore}, year = {2026}, number = {8}, url = {https://skillstore.io/skills/chaiwithjai-standup-formatter/audits/8}, 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-formatter security audit report (audit version 8)" version: "unspecified" type: report authors: - name: "ChaiWithJai" date-released: "2026-07-06" url: "https://skillstore.io/skills/chaiwithjai-standup-formatter/audits/8" identifiers: - type: other value: "skillstore:chaiwithjai-standup-formatter:audit:8" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
85
Maintainability
85
Content
70
Community
83
Spec Compliance

What You Can Build

Prepare a Personal Daily Standup

Convert rough notes into a short update for yesterday, today, and blockers.

Summarize Team Status

Organize multiple teammate updates into a consistent team standup format.

Report Project Progress

Turn project activity into a focused update that highlights outcomes and dependencies.

Try These Prompts

Format My Notes 
Format these notes into a concise individual standup: [paste notes]. Use Done, Today, and Blockers.
Create an Async Update 
Create an async standup for [date] from these notes: [paste notes]. Keep it clear and include useful links.
Combine Team Updates 
Format these teammate updates into a team standup. Group by person and highlight blockers that need follow-up: [paste updates].
Refine for Stakeholders 
Turn this project activity into a standup-style stakeholder update. Emphasize outcomes, current focus, dependencies, and risks: [paste activity].

Best Practices

  • Provide outcome-focused notes instead of long activity logs.
  • Call out blockers with the specific help or decision needed.
  • Mention whether the update is for async writing or a spoken standup.

Avoid

  • Do not include every meeting or minor task if it does not affect coordination.
  • Do not mark blockers as none when a dependency is unresolved.
  • Do not use the skill as a substitute for detailed project documentation.

Frequently Asked Questions

Can this skill create individual standups?
Yes. It formats personal updates into Done, Today, and Blockers sections.
Can it summarize a whole team?
Yes. It can organize multiple teammate updates under each person.
Does it collect git or calendar data automatically?
No. It asks about possible source data, but the user must provide the details.
Is it better for written or spoken standups?
It supports both. Written updates can include more detail, while spoken updates should stay shorter.
Can it include blockers?
Yes. It highlights blockers and encourages specific requests for help.
Does it support weekly updates?
Yes. The intake allows daily, weekly, and custom timeframes.

Developer Details

License

MIT

Skillstore revision

r1

Version notice

The author did not declare a version.

Repository

https://github.com/ChaiWithJai/claude-code-mastery/tree/main/examples/skills/standup-formatter

Ref

dd4a3ef9f20ddf38830950b4bb713df96b431fd6

Maintenance freshness

7/18/2026

Usage

6 downloads · 210 views

File structure

📄 SKILL.md