Twg Status Rollups logo

Twg Status Rollups

Organization
zenobi-us
twg-status-rollups

Use with root `twg` for status rollups, personal work summaries, and decision-readiness or go/no-go briefs. Routes to `pr-tree`, `org-tree`, `work-tree`, or `workitem-tree`.

Overview

Publisherzenobi-us
Repositorydotfiles
Skill nametwg-status-rollups
Stars
67
Forks
6
Bundled files
2
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 2 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by zenobi-us on GitHub. Read the source before you install it.

Installation

Install the Twg Status Rollups AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/zenobi-us/dotfiles.git /tmp/dotfiles
mkdir -p .claude/skills
cp -r /tmp/dotfiles/files/devtools/agent/bundles/developer/skills/atlassian/twg-status-rollups .claude/skills/twg-status-rollups
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Twg Status Rollups in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Twg Status Rollups on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Twg Status Rollups is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

twg-status-rollups

Use with the root twg skill. Get exact command grammar from live twg help, twg help <terms>, or twg help describe <path>.

CLI launcher fallback

Run twg <command>. On shell command not found, use $HOME/.local/bin/twg (macOS/Linux) / $env:LOCALAPPDATA\Programs\twg\bin\twg.exe (PowerShell), then tell user to add that directory to PATH. Do not treat auth or command errors as PATH failures.

Use When

  • "What did I/person/team/org work on?" or weekly personal update
  • Short-window personal update, standup, handoff, or restart after time away
  • "Status of project/goal/topic/focus area"
  • "Is this project ready to launch?" or go/no-go decision brief
  • Leadership, monthly, annual, cycle, appraisal, or goal-alignment readout
  • Org bottlenecks, priorities, stale goals, or project risks

First Move

Resolve scope before retrieval:

  • Person/team/org: resolve identity, roster, or org-tree groups.
  • Project, goal, focus area, or topic: resolve native key, ARI, URL, name, or central project/page/workitem anchors.

Establish the time window. If absent, ask when precision matters; otherwise use a recent bounded window and state it. Keep personal summaries to 1 year or less.

Tree Routing Matrix

  • pr-tree: merged/open PRs, reviews, shipped work, or repo momentum by manager or team. Default for PR-constrained evidence.
  • org-tree: manager chain, roster, and reporting structure; use for grouping, not delivery evidence.
  • workitem-tree: Jira issue load and active/done movement by org tree.
  • work-tree: multi-surface org counts across Jira, PRs, goals, projects, docs, or videos. Not for PR-only or Jira-only asks.

Fast Path: PR-Based Leadership Rollup

For PR-based leadership prompts:

  1. Preserve the requested scope and window; for "last 2 weeks," use --since 14d.
  2. Use pr-tree first. It groups by reporting-tree directReports; add org-tree only for hierarchy context.
  3. If option shape is uncertain, inspect twg help describe "pr-tree" before the data call; do not probe incompatible flag combinations.
  4. Start count-first, then make at most one supported sampling/full-fetch pass for repo or theme evidence. Synthesize at manager/team level from that tree. Do not issue per-person queries merely to populate every group; use one targeted PR follow-up only when a material theme lacks representative proof.
  5. Add one secondary surface only for a named gap.

Target 2-4 calls.

Evidence Policy

  • Match evidence to prompt constraints; merged-PR-only conclusions require PR evidence.
  • Start count-first on tree surfaces; hydrate examples only for themes, risks, or owner attribution.
  • Rank broad lists before minimal hydration.
  • Distinguish authored delivery from review, coordination, and influence.
  • Stop when evidence is sufficient. After two identical backend failures, stop that path and report the gap.

Recipe Cards

Person Or Personal Update

Resolve the person, then pull recent Jira work, PRs, docs/pages, meetings, and project/goal involvement. Load references/personal-work-summary.md for exact subject, notification, PR hydration, and outcome-first rules. Separate delivery, review, docs/strategy, coordination, and influence.

Short-Window Personal Update / Standup

Load references/personal-work-summary.md. Resolve the person, preserve the requested project and window, prioritize material work, and distinguish evidence gaps from confirmed blockers.

Team Or Org Leadership Readout

Resolve org-tree first. Group before per-person details. Use org-level signals, then hydrate only outliers that change momentum, blockers, review load, or ownership.

Project Or Goal Status

Fetch the native project/goal first. Include owner, state, update, links, dates, and recency. Hydrate only risk, progress, or dependency evidence.

Decision Readiness / Go-No-Go

Load references/decision-readiness.md. Resolve the native project or decision anchor first and keep explicit links as the scope boundary. Identify the gates, then give the requested decision or recommendation with confidence, gaps, and change conditions. Do not infer owners.

Topic Status

Resolve/search once, select central project, goal, page, or workitem anchors, then hydrate those before using broad work/activity queries.

References

  • references/personal-work-summary.md - standups, catch-ups, and broader personal status evidence
  • references/decision-readiness.md - cross-domain go/no-go and approval evidence

Appraisal / Performance Evidence

Resolve person and horizon. Separate delivery, review, collaboration, docs/strategy, project/goal impact, and stakeholder signals. Avoid count-only ranking; add caveats when evidence is weak.

Output Shape

  • Executive summary first, with 3-6 high-signal observations.
  • Table with owner/team/workstream, positive signals, risk signals, current focus, confidence, and evidence.
  • Risks and leadership attention ranked by impact and owner.
  • Confidence and gaps, including stale updates, missing product coverage, ACL gaps, or sampled evidence boundaries.

Anti-Patterns

  • Do not make a status report a list of every artifact.
  • Do not infer goal/project health from issue counts alone.
  • Do not fan out across every org member if manager/team-level grouping answers the prompt.
  • Do not use search snippets as final evidence for status or risk.
  • Start explicit merged/open PR rollups with pr-tree, not the other trees.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Twg Status Rollups AI skill do?

Use with root `twg` for status rollups, personal work summaries, and decision-readiness or go/no-go briefs. Routes to `pr-tree`, `org-tree`, `work-tree`, or `workitem-tree`.

Why use Twg Status Rollups on TypingMind?

Because you install it once and use it with any model. Twg Status Rollups is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Twg Status Rollups in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/zenobi-us/dotfiles/tree/master/files/devtools/agent/bundles/developer/skills/atlassian/twg-status-rollups. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Twg Status Rollups?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Twg Status Rollups?

As many as you like. As long as a model supports skills, you can use Twg Status Rollups with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Twg Status Rollups AI skill free?

Yes. It is published on GitHub by zenobi-us under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇