Install
$ agentstack add skill-shalomb-agent-skills-daily-standup ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Daily Standup Skill
Automate the bridge between synchronized engineering discussions and asynchronous project tracking.
Purpose
- Status Updates: Move cards and post technical rationale to GitHub issues.
- Bias for Action: Enforce an options-based resolution format for blockers.
- Proactive Intervention: Detect stalled items and flag "Reality Gaps" between claims and system state.
Capabilities
- Context Discovery: Auto-infer Project and current Iteration.
- Semantic Mapping: Link transcript discussion points to specific GitHub issues.
- Stall Detection: Flag items blocked for 2+ days without progress.
- Lead Briefing: Prioritize critical path unblocking for the Engineering Lead.
Technical Guides
references/status-update.template.md: Mandatory action-oriented comment format.references/intervention-logic.md: Rules for stall detection and reality checking.
Orchestration Flow
- Phase 1: Knowledge Gathering
- Identify Project, Iteration, and Working Set.
- Discover the most recent VTT file in
~/Downloads.
- Phase 2: Deep Analysis
- Call
meeting-notesskill to parse transcript. - Fetch issue history for all matches to detect stalls.
- Perform Reality Checks (Refer to
intervention-logic.md).
- Phase 3: Proposal Generation
- Apply the Bias for Action template to each update.
- Generate Lead Briefing with priority escalations.
- Phase 4: User Validation & Execution
- Display Plan and Briefing; execute confirmed updates via
gh.
Maintained by: contributors | Version: 1.2 | Last Updated: 2026-03-14
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: shalomb
- Source: shalomb/agent-skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.