agentsclimarketplace

Clear ask

Skill tmusser/context-to-action-skills/skills/clear-ask

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 clear-ask

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

Turn vague workplace context into a crisp ask with clear ownership and timing.

SKILL.md

1.7 KB, as published. Nobody here has run it

clear-ask

Purpose

Convert a fuzzy request, thread, or note into a direct ask someone can understand and act on.

Use For

  • Turning a rambling draft into a clear request
  • Clarifying what decision is actually needed
  • Making ownership and timing explicit before sending a message

Inputs

  • Slack or email draft
  • Meeting notes
  • Project context
  • Pasted workplace context
  • A reduce-to-facts ledger or conversation-state record

Guardrails

  • Read before write.
  • Do not send the message unless explicitly asked.
  • Separate known facts from assumptions.
  • Flag missing owner, timing, or decision context.
  • Prefer the smallest useful ask.

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 ask and draft.
  • Do not send, publish, update tickets, create events, or mutate systems unless explicitly asked.

Output

  • Clean ask
  • Audience
  • Owner
  • Deadline / timing
  • Decision needed
  • Missing info
  • Potential misread
  • Why this ask is clearer
  • Suggested message

Success Standard

The output should remove ambiguity and make the next action obvious within 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.