collect-my-team-updates

collect-my-team-updates is a skill for Claude Code, Codex from akiotanaka847/qaio-desktop. It costs 82 tokens per session (1,283 once invoked), scanned A, original, MIT.

A weekly team-update process that sends a prompt through team chat or email, gathers replies, and compares them with your current priorities.

In plain words
What is it for?
Use it to send recurring update requests, review team responses, and identify unanswered updates or priority risks.
Why use it?
It shows which work is on track, drifting, blocked, or missing an update without requiring you to chase each person.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

Good fit Use it to send recurring update requests, review team responses, and identify unanswered updates or priority risks.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/akiotanaka847/qaio-desktop/collect-my-team-updates
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add akiotanaka847/qaio-desktop --skill collect-my-team-updates
Clone the repo
git clone --depth 1 https://github.com/akiotanaka847/qaio-desktop

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for collect-my-team-updates

README.md
[![agentmods](https://agentmods.dev/badge/skills/akiotanaka847/qaio-desktop/collect-my-team-updates/github.svg)](https://agentmods.dev/skills/akiotanaka847/qaio-desktop/collect-my-team-updates)
Your own site
<a href="https://agentmods.dev/skills/akiotanaka847/qaio-desktop/collect-my-team-updates"><img src="https://agentmods.dev/badge/skills/akiotanaka847/qaio-desktop/collect-my-team-updates/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for collect-my-team-updates

Your own site · 80×15
<a href="https://agentmods.dev/skills/akiotanaka847/qaio-desktop/collect-my-team-updates"><img src="https://agentmods.dev/badge/skills/akiotanaka847/qaio-desktop/collect-my-team-updates.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 82 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,283 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00082 $0.01283
Opus 5 $0.00041 $0.00642
Sonnet 5 $0.00016 $0.00257
Haiku 4.5 $0.00008 $0.00128

Measured 11d ago against content hash 4396a7002eca, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

collect-my-team-updates scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

store/agents/operations/.agents/skills/collect-my-team-updates/SKILL.md · 91 lines

How it starts

The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Collect My Team Updates

Team-facing weekly update loop. Skill dormant for true solo founder - moment founder hires 1+ people and lists in operating context, lights up.

When to use

  • "collect this week's updates from the team".
  • "are we on track for goals this week".
  • "send the Friday reminder and analyze what comes back".

Connections I need

I run external work through Composio. Before this skill runs I check the categories below are linked. Missing → I name the category, ask you to connect it from the Integrations tab, stop.

  • Team chat (Slack, Microsoft Teams) - Required. Best place to send the weekly prompt and read replies.
  • Inbox (Gmail, Outlook) - Optional. Fallback when team members live in email rather than chat.

If no team chat or inbox is connected I stop and ask you to connect your team chat first.

Information I need

I read your operations context first. For every required field that's missing I ask ONE plain-language question (best modality: connected app > file drop > URL > paste) and wait.

  • Team roster - Required. Why I need it: this skill only runs against your declared team, never random contacts. If missing I ask: "Who's on your team right now? Names plus how I should reach each person - best is to drop a roster sheet or list them in your operating context."
  • Active priorities - Required. Why I need it: I judge each update against what the company is actually trying to do this quarter. If missing I ask: "What are the 2 to 3 things the company is pushing on this quarter?"
  • Review day - Optional. Why I need it: sets the deadline for replies. If you don't have it I keep going with TBD and use a 48-hour window.
  • Your voice - Optional. Why I need it: the reminder sounds like you, not a bot. If you don't have it I keep going with TBD using a neutral tone - best is to connect your inbox so I can sample 20 to 30 sent messages.

Steps

  1. Read context/operations-context.md. If "Key contacts / Team" section absent, empty, or N≤1 (founder only), stop and say:

Read the full file on GitHub · 91 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 11d ago First seen · 91 lines · 82 tokens per session scan A 4396a7002eca

Subscribe to this mod's changes

collect-my-team-updates is a skill published in the GitHub repository akiotanaka847/qaio-desktop (2 stars, last pushed 8d ago), licensed MIT. It adds 82 tokens to every session and 1,283 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories