Skip to content
Skill

Standup

Use when a team exists but current status is unknown — backlog changed, context switch happened, or session just started

Install
Scripts
None
Platforms
Claude Code, Codex, Cursor
GitHub stars
14
Last commit
7 months ago
License
MIT
Listing updated
today

When your agent uses it

Use when a team exists but current status is unknown — backlog changed, context switch happened, or session just started. Syncs status, surfaces blockers, checks learning health. Keywords: status, sync, blockers, progress, team, check-in, reorient.

From the skill's SKILL.md. Your agent reads this description to decide when to load the skill.

What it can access

From a static check of its 1 file (9 KB) on GitHub on 17 November 2026. Nothing was run. Read the files before you install a skill: it can tell your agent to run anything its tools allow.

Install

This skill ships in the tackline plugin. In Claude Code, add the marketplace and install the plugin (it may include other skills too):

/plugin marketplace add tyevans/tackline
/plugin install tackline@tackline

Or copy only this skill to ~/.claude/skills/standup:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/tyevans/tackline.git "$tmp" &&
mkdir -p ~/.claude/skills &&
rm -rf ~/.claude/skills/standup &&
cp -R "$tmp/skills/teams/standup" ~/.claude/skills/standup &&
rm -rf "$tmp"

For one project only, put the folder in .claude/skills/standup inside it instead.

Claude Code docs on skills

Copy the skill folder to ~/.agents/skills/standup to use it in every repository:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/tyevans/tackline.git "$tmp" &&
mkdir -p ~/.agents/skills &&
rm -rf ~/.agents/skills/standup &&
cp -R "$tmp/skills/teams/standup" ~/.agents/skills/standup &&
rm -rf "$tmp"

For one repository only, put the folder in .agents/skills/standup inside it instead.

Codex docs on skills

Copy the skill folder to ~/.cursor/skills/standup to use it in every project:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/tyevans/tackline.git "$tmp" &&
mkdir -p ~/.cursor/skills &&
rm -rf ~/.cursor/skills/standup &&
cp -R "$tmp/skills/teams/standup" ~/.cursor/skills/standup &&
rm -rf "$tmp"

For one project only, put the folder in .cursor/skills/standup inside it instead.

Cursor docs on skills

Run in a terminal (add --scope workspace to install it for the current workspace only):

gemini skills install https://github.com/tyevans/tackline.git --path skills/teams/standup

Or copy the folder to ~/.gemini/skills/standup yourself.

Gemini CLI docs on skills

For GitHub Copilot in VS Code, copy the skill folder to ~/.copilot/skills/standup:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/tyevans/tackline.git "$tmp" &&
mkdir -p ~/.copilot/skills &&
rm -rf ~/.copilot/skills/standup &&
cp -R "$tmp/skills/teams/standup" ~/.copilot/skills/standup &&
rm -rf "$tmp"

For one project only, put the folder in .github/skills/standup inside it instead.

VS Code docs on skills

Get the folder:

git clone --depth 1 https://github.com/tyevans/tackline.git

Then copy tackline/skills/teams/standup into your agent's skills folder as standup. Agents that support SKILL.md read one folder per skill.

The SKILL.md format

Standup FAQ

How do I install Standup in Claude Code?

Copy the skill folder from GitHub to ~/.claude/skills/standup to use it in all your projects, or to .claude/skills/standup in one project. Or install the tackline plugin, which includes it: /plugin marketplace add tyevans/tackline, then /plugin install tackline@tackline.

Does Standup run scripts?

No. It is instructions only, with no scripts. This comes from a static check of the files on GitHub; nothing was run. Read the files before you install it.

Which AI agents can use Standup?

Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf and Goose. Each reads skills in the SKILL.md format from its own folder; the install steps on this page list them.

More from tyevans/tackline

  1. Use when items need categorical triage (critical/warning/ok), not numeric scoring

    • Open source
    • 14 GitHub stars
  2. Use when you want to stress-test a proposal, plan, or findings before acting on them

    • Open source
    • 14 GitHub stars
  3. Use when a goal is too large to tackle as one unit

    • Open source
    • 14 GitHub stars
  4. Use when deciding between two approaches and you need a structured tradeoff comparison

    • Open source
    • 14 GitHub stars
  5. Use when you want to browse available skills or find the right pipeline for a workflow

    • Open source
    • 14 GitHub stars
  6. Use when prior output is too verbose and needs condensing

    • Open source
    • 14 GitHub stars