agentsclimarketplace

Status update

Skill tmusser/context-to-action-skills/skills/status-update

Claude skills for turning messy business context into clear asks, decisions, owners, updates, and follow-ups.

Install
npx -y skills add tmusser/context-to-action-skills --skill status-update

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Create concise status updates for teams, managers, executives, customers, or partners.

SKILL.md

1.7 KB, as published. Nobody here has run it

status-update

Purpose

Create a concise update from messy conversation state without losing the ask, risk, or next milestone.

Modes

  • team
  • manager
  • executive
  • customer / partner

Inputs

  • Slack or email context
  • Project or ticket context
  • Meeting notes
  • Customer context
  • Pasted update notes
  • A reduce-to-facts ledger or conversation-state record

Guardrails

  • Read before write.
  • Do not send the update unless explicitly asked.
  • Keep risks separate from blockers.
  • Tune tone and detail to the audience.
  • Label assumptions and source gaps.
  • Keep the output short enough to send quickly.

Portable Output Contract

  • Use only the useful subset of source-backed facts, assumptions, source gaps, stakeholder sensitivities, potential misreads, and the suggested next action.
  • Use the smallest useful output.
  • Label assumptions and preserve source gaps, source anchors, and confidence labels.
  • When consuming upstream state, do not promote an assumption, inference, open question, proposed action, or stakeholder position into a fact, decision, commitment, owner, or deadline without new source support.
  • Keep unresolved approvals, owners, timing, and blockers explicit in the update.
  • Do not send, publish, update tickets, create events, or mutate systems unless explicitly asked.

Output

  • Conversation state
  • Status
  • What changed
  • Progress
  • Risks / blockers
  • Stakeholder sensitivities
  • Asks
  • Next milestone
  • Suggested audience-specific version

Success Standard

The user should get a send-ready update in under 5 minutes.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.