Install
$ agentstack add skill-lkim0402-agent-teamflow-teamflow-update ✓ 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
teamflow-update
Read AGENTS.md, then follow the workflow below. This workflow does not require .agent-teamflow; it updates the install itself. Treat the user's remaining request text as $ARGUMENTS.
Pull the latest agent-teamflow into the install directory and re-register the user-scope runtime adapters. Use this when a teammate ships a new skill or a runbook is updated upstream.
Run this workflow in an isolated worker if the current agent runtime supports one; otherwise run it in the main session. Keep git/setup output concise and report only the final summary.
Setup
The install directory is the directory containing this runbook's parent — for the documented global install, that is usually ~/.agent-teamflow. If a runtime wrapper passes an absolute runbook path, derive the install dir from that path.
If .git does not exist at that path: stop and tell the user the install looks corrupted — they should reclone with the README's quick-start command.
Execution
Step 1. Capture the pre-update state
cd
PRE_HEAD=$(git rev-parse HEAD)
PRE_SUBJECT=$(git log -1 --format='%h %s')
Step 2. Fetch and fast-forward
git fetch origin
POST_HEAD=$(git rev-parse origin/HEAD 2>/dev/null || git rev-parse origin/main)
If PRE_HEAD equals POST_HEAD: print Already up to date at . and stop. Skip Step 3.
Otherwise:
git pull --ff-only
If git pull fails because the working tree has local changes (the user customized the runbooks): stop and report — the user must resolve manually. Do NOT discard their changes.
Step 3. Re-run setup
./setup
Capture the output. The script prints adapter install counts for Claude Code and/or Codex.
Step 4. Summarize the diff
Show the user a terse list of new commits, not the full log:
git log --format='%h %s' "${PRE_HEAD}..HEAD"
Step 5. Report
Updated agent-teamflow:
From:
To:
New commits:
Adapters regenerated:
If no new commits: Already up to date at . (and skip everything else).
Hard rules
- Fast-forward only — never rebase, never merge. If the install dir has diverged from origin, report and stop so the user can decide.
- Never run
git reset --hardor any destructive git op to "fix" the install. If something is wrong, tell the user. - Never edit files in the install dir — the only mutation is
git pulland re-running./setup. - No emojis.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: lkim0402
- Source: lkim0402/agent-teamflow
- 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.