📦
content-creator
88Create Brand-Consistent Marketing Content
Marketing teams need content that stays consistent across channels. This skill helps plan, write, analyze, and optimize content for brand voice and SEO.
Writing & Content View
Skills team-collaboration-standup-notes
📦
team-collaboration-standup-notes
Content revision r2 Medium Risk ⚙️ External commands📁 Filesystem access
Create Clear Async Standup Notes
Remote teams often need updates from scattered work records. This skill turns approved project context into a concise standup draft for human review.
Supports: Claude Codex Code(CC)
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Agent request
Review the Skillstore skill "team-collaboration-standup-notes" from https://skillstore.io/skills/sickn33-team-collaboration-standup-notes.md and its manifest at https://skillstore.io/api/skills/sickn33-team-collaboration-standup-notes/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 "team-collaboration-standup-notes". Completed API authentication, fixed a queue retry issue, and have a database migration planned today.
Expected outcome:
- Yesterday: Completed API authentication and resolved the queue retry issue.
- Today: Finish and test the database migration.
- Blockers: None reported.
Using "team-collaboration-standup-notes". Waiting for database replica access and reviewing JIRA-234 today.
Expected outcome:
- Yesterday: Investigated the migration validation approach.
- Today: Review JIRA-234 and prepare migration tests.
- Blockers: Waiting for read-only database replica access from the database team.
Security Audit
Medium Riskv6 • 9/6/2026 Open versioned report
Most static detections are Markdown formatting or read-only command examples and are false positives. The supplied Bash implementation genuinely collects local Git, Jira, Obsidian, and calendar data, writes it to a predictable temporary file, and sends context to an AI CLI. Users should review data permissions and the draft before any publication.
2
Files scanned
822
Lines analyzed
14
Review items
0
False positives ignored
Confirmed security concerns (2)
Medium
Sensitive Work Context Is Sent to an AI CLI
The sample workflow collects Git, Jira, Obsidian, and calendar data and passes the resulting context to a Claude CLI. This can disclose internal project or personal information unless the user has approved the service and data scope.
The script explicitly collects these sources and invokes claude-ai for generation. The actual handling policy of that CLI is not specified, so the impact depends on the user configuration and authorization.
Medium
Draft Context Uses a Predictable Temporary File
The sample script writes aggregated work data to /tmp/standup-context.json before processing it. A predictable shared temporary path can expose data to other local users or be affected by symlink and race conditions.
The documented path is a fixed filename under /tmp and holds commits, tickets, vault changes, and meetings. Local environment permissions determine exploitability.
Capability review items (14)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Medium
Shell command substitution
DATE=$(date +%Y-%m-%d)
The implementation script executes date to construct output state. It is benign but is a real external command when a user runs the supplied script.
Medium
Shell command substitution
USER=$(git config user.name)
The implementation script runs git config to collect the local user name for the generated context.
Medium
Shell command substitution
USER_EMAIL=$(git config user.email)
The implementation script runs git config to collect the local user email, which is personal data included in the generated context.
Medium
Shell command substitution
COMMITS=$(git log --author="$USER" --since="24 hours ago" \
The implementation script executes git log and captures local commit metadata for later processing.
Medium
Shell command substitution
JIRA_DONE=$(jira issues list --assignee currentUser() \
The supplied script executes the Jira CLI and captures ticket data, which can contain non-public project information.
Medium
Shell command substitution
JIRA_PROGRESS=$(jira issues list --assignee currentUser() \
The supplied script executes the Jira CLI and captures in-progress ticket data for processing.
Medium
Shell command substitution
OBSIDIAN_CHANGES=$(obsidian_get_recent_changes --days 2)
The supplied script invokes an Obsidian integration and captures recent vault changes.
Medium
Shell command substitution
MEETINGS=$(gcal --today --format=json)
The supplied script invokes a calendar CLI and captures current-day event data.
Medium
Shell command substitution
"commits": $(echo "$COMMITS" | jq -R -s -c 'split("\n")'),
The implementation script executes an echo and jq pipeline to serialize collected commit data into a context file.
Medium
Shell command substitution
STANDUP_NOTE=$(claude-ai << 'PROMPT'
The supplied script invokes a Claude CLI to generate a note from collected work data. This is real command execution and has data-handling implications.
Medium
Shell command substitution
Context: $(cat /tmp/standup-context.json)
The script reads the generated context file as part of the Claude CLI prompt construction.
Medium
Unix shell invocation
#!/bin/bash
The playbook provides a runnable Bash script beginning with a Bash shebang; it executes the documented collection workflow when copied and run.
Medium
Temp directory access
cat << EOF > /tmp/standup-context.json
The supplied script writes collected work and calendar context to a predictable file under /tmp, exposing it to local temporary-directory risks.
Medium
Temp directory access
Context: $(cat /tmp/standup-context.json)
The supplied script reads the predictable temporary context file containing collected work data.
Risk Factors
⚙️ External commands (26)
resources/implementation-playbook.md:36-39 resources/implementation-playbook.md:39-40 resources/implementation-playbook.md:40-43 resources/implementation-playbook.md:43-44 resources/implementation-playbook.md:44-45 resources/implementation-playbook.md:45-47 resources/implementation-playbook.md:110-114 resources/implementation-playbook.md:187 resources/implementation-playbook.md:479 resources/implementation-playbook.md:625 resources/implementation-playbook.md:626 resources/implementation-playbook.md:627 resources/implementation-playbook.md:633-634 resources/implementation-playbook.md:638 resources/implementation-playbook.md:642 resources/implementation-playbook.md:648 resources/implementation-playbook.md:652 resources/implementation-playbook.md:660 resources/implementation-playbook.md:669-677 resources/implementation-playbook.md:681 resources/implementation-playbook.md:622 SKILL.md:29 SKILL.md:34 SKILL.md:35 SKILL.md:43 SKILL.md:47
📁 Filesystem access (2)
Audited by: claude 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.
Copy report link
https://skillstore.io/skills/sickn33-team-collaboration-standup-notes/audits/6?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-team-collaboration-standup-notes?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-team-collaboration-standup-notes?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-team-collaboration-standup-notes/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-team-collaboration-standup-notes.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
sickn33. (2026). team-collaboration-standup-notes security audit report (audit version 6) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-team-collaboration-standup-notes/audits/6BibTeX citation
@techreport{sickn33-sickn33-team-collaboration-standup-notes-2026,
author = {sickn33},
title = {team-collaboration-standup-notes security audit report (audit version 6)},
institution = {Skillstore},
year = {2026},
number = {6},
url = {https://skillstore.io/skills/sickn33-team-collaboration-standup-notes/audits/6},
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: "team-collaboration-standup-notes security audit report (audit version 6)"
version: "unspecified"
type: report
authors:
- name: "sickn33"
date-released: "2026-09-06"
url: "https://skillstore.io/skills/sickn33-team-collaboration-standup-notes/audits/6"
identifiers:
- type: other
value: "skillstore:sickn33-team-collaboration-standup-notes:audit:6"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: High 55
Architecture
85
Maintainability
87
Content
68
Community
83
Spec Compliance
What You Can Build
Prepare a daily engineering update
Turn recent commits and assigned tickets into a short draft for a daily async standup.
Coordinate a distributed team
Create consistent updates that highlight priorities, meetings, dependencies, and requests for help.
Document project progress
Use a repeatable note structure to summarize completed tasks and next steps across project records.
Try These Prompts
Draft a simple standup
Create a concise standup draft from these accomplishments, today priorities, and blockers. Use Yesterday, Today, and Blockers headers.
Summarize recent commits
Summarize these recent commit messages into three outcome-focused standup bullets. Preserve ticket references and avoid technical detail that does not help the team.
Combine approved sources
Using only this approved Git, Jira, note, and calendar context, create a standup draft. Flag uncertain links between commits and tickets instead of guessing.
Review a standup for publication
Review this standup draft for accuracy, sensitive information, unclear ownership, and missing blockers. Return recommended edits before I share it.
Best Practices
- Confirm which data sources are approved before collecting context.
- Use outcome-focused bullets and include clear ownership for blockers.
- Review drafts for accuracy and sensitive information before posting.
Avoid
- Do not publish generated updates without human review.
- Do not include secrets, private customer data, or unnecessary personal details.
- Do not infer ticket status or completion from incomplete context.
Frequently Asked Questions
What information can this skill use?
It provides patterns for using approved Git commits, Jira tickets, Obsidian notes, and calendar events.
Does it post messages automatically?
The skill provides a sample workflow. Any posting should require explicit human review and confirmation.
Can I use it without Jira?
Yes. The guidance supports graceful fallback when Jira data is unavailable.
Should I share all commit details?
No. Share only information needed for the update and remove sensitive details.
Can it identify blockers?
It can help structure explicit blockers and highlight patterns that may need review.
Which output formats are supported?
The playbook includes guidance for Markdown-based updates such as Slack, Discord, email, and Obsidian notes.
Developer Details
Author
sickn33License
MIT
Skillstore revision
r2
Version notice
The author did not declare a version.
Ref
ae6ba0f1a47f0b4427a656b2202f2ff34bfea6be
Maintenance freshness
9/6/2026
Usage
9 downloads · 88 views
File structure
More from sickn33
View all📦
prompt-engineering-patterns
85Improve LLM Prompts With Proven Patterns
Inconsistent prompts waste time and make AI outputs hard to trust. This skill guides prompt design with reusable patterns, examples, evaluation steps, and optimization workflows.
Productivity View
📦
senior-architect
81Review Architecture Workflows and Project Paths
Architecture reviews need a consistent starting point and clear project boundaries. This skill provides workspace-scoped tool templates, command examples, and generic design references.
Coding & Development View
📦
senior-fullstack
81Review Fullstack Project Foundations
Fullstack project setup can require many tools and checks. This skill provides basic local wrappers, common commands, and general engineering guidance.
Coding & Development View
📦
prompt-engineer
81Optimize AI Prompts With Prompt Engineer
Writing clear prompts is hard when goals are vague or complex. This skill turns rough requests into structured prompts using proven prompt frameworks.
Productivity View
📦
product-manager-toolkit
80Prioritize Product Work With Research Insights
Product teams need faster ways to rank features, synthesize interviews, and document decisions. This skill provides RICE scoring, interview analysis, and PRD templates for structured planning.
Productivity View
Related Skills
View all📦
get-my-team-posting
70Turn One Company Message Into Team Posts
by prateeks367
Teams often publish identical employee posts that feel scripted and weaken trust. This skill turns one approved message into distinct drafts based on each person's experience, voice, and willingness to share.
Communication View
📦
weekly-report
77Create Clear Weekly Work Reports
by zhaobolun-code
Turning scattered project notes into a formal weekly report takes time and can omit important work. This skill creates a consistent report from execution documents or README version records.
Productivity View
📦
launch
82Plan a Product Launch That Builds Momentum
by coreyhaines31
Launch planning becomes difficult when teams lack a clear sequence, audience strategy, and readiness criteria. This skill creates a phased plan from validation through post-launch adoption.
Communication View
📦
gws-gmail
81Manage Gmail with Google Workspace CLI
by googleworkspace
Managing Gmail through API commands requires accurate resource names and parameters. This skill guides Claude and Codex through supported Gmail CLI workflows.
Communication View
📦
reactivation-specialist
81Build a compliant email reactivation program
by aaron-he-zhu
Lapsed subscriber lists can reduce deliverability and create consent risk. This skill designs a staged win-back program with fresh consent signals and clear suppression outcomes.
Communication View
📦
email-sequence-designer
81Design a lifecycle email sequence
by aaron-he-zhu
Email teams often lack a clear lifecycle map and send too frequently. This skill creates flow plans with timing, exits, and safeguards before copywriting begins.
Communication View