Agent skill · Testing & QA

email-to-tasks

Convert an email (or a whole thread) into real tasks — the actual asks extracted from the prose, each with owner, deadline, and the done-test, so nothing lives in the inbox as its own reminder. Use when asked what am I actually being asked to do here, turn this thread into a task list, extract the action items from this email, or I keep re-reading this thread. Produces the ask extraction with quoted sources, the task list in owner-verb-deadline form, and the reply that confirms the commitments.

mohitagw15856github.com/mohitagw15856GitHub ↗
claude-codecursorMIT
Install
npx skills add mohitagw15856/pm-claude-skills --skill email-to-tasks --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 4 KB
Bundled scripts: none
Path: skills/email-to-tasks/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,255
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Email To Tasks Skill Long emails and longer threads hide their asks: three requests buried in paragraph four, a soft deadline in the sign-off, an implied "you'll handle this?" nobody confirmed. Until the asks are extracted, the *thread itself* becomes the task — re-read five times, actioned zero. This skill mines the actual requests (quoted, so nothing is invented), converts each into owner-verb-deadline form with a done-test, and drafts the confirming reply that turns assumptions into commitments. ## What This Skill Produces - **The ask extraction** — every explicit and implied request, quoted from the source text - **The task list** — each: owner · verb-first action · deadline (stated or proposed) · the done-test - **The ambiguity list** — asks too vague to action, each with the clarifying question that fixes it - **The confirming reply** — the short message that locks owners and dates before anyone's assumption diverges ## Required Inputs Ask for these if not provided: - **The email/thread** — verbatim; extraction quotes its sources - **Who the user is in it** — extraction is role-relative: their tasks, tasks they're delegating, and tasks that are someone else's problem are th

What's inside
Steps it walks through
  1. What This Skill Produces
  2. Required Inputs
  3. Framework: The Extraction Rules
  4. Output Format
  5. Your Tasks
  6. You're Delegating / Others Own
  7. Commitments You Made
  8. Too Vague To Action
  9. The Confirming Reply
  10. Quality Checks
  11. Anti-Patterns
More from pm-claude-skills
All skills →
About this skill
What does the email-to-tasks skill do?

Convert an email (or a whole thread) into real tasks — the actual asks extracted from the prose, each with owner, deadline, and the done-test, so nothing lives in the inbox as its own reminder. Use when asked what am I actually being asked to do here, turn this thread into a task list, extract the action items from this email, or I keep re-reading this thread. Produces the ask extraction with quoted sources, the task list in owner-verb-deadline form, and the reply that confirms the commitments.

How do I install it?

Run `npx skills add mohitagw15856/pm-claude-skills --skill email-to-tasks --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going