aiskillstore/standup-formatter
skills/chaiwithjai/standup-formatter/SKILL.md
Use when generating standup reports, daily updates, or team status summaries. Formats work activity into concise standup format.
$ install --global
skillsauthnpx skillsauth add aiskillstore/marketplace standup-formatterInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Mar 31, 2026, 3:08 PM67.6s2 files scanned
SKILL.md
- name:
- standup-formatter
- description:
- Use when generating standup reports, daily updates, or team status summaries. Formats work activity into concise standup format.
<essential_principles>
Standup Philosophy
Purpose
Standups exist to:
- Share blockers that need help
- Coordinate on dependencies
- Keep work visible
Standups do NOT exist to:
- Report hours worked
- Justify existence
- Detail every task
The Ideal Standup
Done: What you completed (outcomes, not activities) Today: What you're working on (1-2 focus items) Blockers: What's preventing progress (specific, actionable)
Time Budgets
- Speaking: 60 seconds max per person
- Written: 3-5 bullet points total
- Detail level: Enough to understand, not to replicate
Format Guidelines
Good Examples
Done: Merged PR for user auth (#234)
Today: Starting payment integration
Blockers: Waiting on API spec from backend team
Bad Examples
Done: Worked on stuff, had meetings, reviewed some code,
wrote tests, fixed bugs, updated docs, etc.
Today: More of the same
Blockers: Nothing
Async vs Sync
Async (written):
- More detail acceptable
- Include links to PRs/tickets
- Post by 9am team time
Sync (spoken):
- Extremely concise
- No reading from notes
- Save details for follow-ups </essential_principles>
- Individual - Your personal standup
- Team - Aggregate team status
- Project - Status for specific project
For what timeframe?
- Yesterday/today (daily)
- This week (weekly)
- Custom dates
Source data?
- Git activity
- Calendar events
- Manual input </intake>
## Standup - [Date]
### Done
- [Completed item 1]
- [Completed item 2]
### Today
- [Focus item 1]
- [Focus item 2]
### Blockers
- [Blocker with specific need] / None
Team Standup
## Team Standup - [Date]
### [Person 1]
- Done: [summary]
- Today: [focus]
- Blockers: [if any]
### [Person 2]
...
Related Skills
aiskillstore/hig-components-content
development
VerifiedTrustedCommunity
Apple Human Interface Guidelines for content display components. Use this skill when the user asks about charts component, collection view, image view, web view, color well, image well, activity view, lockup, data visualization, content display, displaying images, rendering web content, color pickers, or presenting collections of items in Apple apps. Also use when the user says how should I display charts, what's the best way to show images, should I use a web view, how do I build a grid of items, what component shows media, or how do I present a share sheet. Cross-references: hig-foundations for color/typography/accessibility, hig-patterns for data visualization patterns, hig-components-layout for structural containers, hig-platforms for platform-specific component behavior.
244SKILL.mdUpdated Apr 10, 2026
aiskillstore/helpdesk-automation
tools
VerifiedTrustedCommunity
Automate HelpDesk tasks via Rube MCP (Composio): list tickets, manage views, use canned responses, and configure custom fields. Always search tools first for current schemas.
244SKILL.mdUpdated Apr 10, 2026
aiskillstore/haskell-pro
testing
VerifiedTrustedCommunity
Expert Haskell engineer specializing in advanced type systems, pure functional design, and high-reliability software. Use PROACTIVELY for type-level programming, concurrency, and architecture guidance.
244SKILL.mdUpdated Apr 10, 2026
aiskillstore/graphql
tools
VerifiedTrustedCommunity
GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper controls, clients can craft queries that bring down your server. This skill covers schema design, resolvers, DataLoader for N+1 prevention, federation for microservices, and client integration with Apollo/urql. Key insight: GraphQL is a contract. The schema is the API documentation. Design it carefully.
244SKILL.mdUpdated Apr 10, 2026