summarize-status

Generates concise Markdown status summaries for Todero project and workspace scopes via its summary-slot API.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/nabitllc/todero --skill summarize-status-nabitllc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: summarize-status
Source: https://github.com/nabitllc/todero/tree/main/packages/skills-catalog/catalog/bundled/todero-operations/summarize-status
Command: npx skills add https://github.com/nabitllc/todero --skill summarize-status-nabitllc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams using Todero to orchestrate AI agents need a quick, human-readable answer to "what needs my attention right now" without reading every issue and comment on a board. This Skill reads a project or workspace scope, identifies the 1–3 concrete actions blocking progress, and writes a short summary back to the scope's summary slot. ## Core Features & Use Cases - Action-first summaries: Opens every summary with 1–3 specific unblock actions with inline links, followed by a brief plain-language status. - Scoped reads and writes: Works against Todero's company-scoped summary-slot API for project, workspaces overview, project workspace, and execution workspace scopes, with optimistic concurrency via baseRevisionId. - Live progress streaming: Emits STATUS lines and a delimited summary draft so the UI card shows progress while the summary is generated. - Use Case: A manager clicks Refresh on a project summary card; the assigned agent reads the project's issues and blocker chains, then writes a one-glance summary naming the exact PR to merge or question to answer. ## Quick Start Assign a summary-generation issue naming the scope and slot, then have the agent read the current slot and issues and write the new Markdown revision back to the summary slot.

Frequently Asked Questions about summarize-status

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a status summary for a Todero project?

Assign a summary-generation issue naming the scope kind, scope id, and slot. The agent reads the current slot and project issues via the company-scoped API, then writes a new Markdown revision with PUT to the summary-slot endpoint.

What scopes can a Todero status summary cover?

Summaries support four scope kinds: project, workspaces_overview, project_workspace, and execution_workspace. The workspaces overview scope has no scopeId; all other reads and writes stay within a single company.

Can the summarizer change issues or code while summarizing?

No. The skill is strictly read-and-report: it reads issues, comments, and blocker chains but only writes one Markdown revision to the requested summary slot. Requests to change issue state or edit code are out of scope.

How are concurrent summary writes handled in Todero?

Each write includes the baseRevisionId from the current slot read, so the API can detect concurrent modifications. The write also records the generationIssueId and model for traceability.

What happens when a scope has no activity to summarize?

The agent writes an honest summary stating nothing needs the reader and names the next thing worth watching. Fabricating status not supported by the source data is explicitly prohibited.