agentleFS
ntaffziintaffzii/Skill-Agents/skills/productivity/inbox-meeting-triage/SKILL.md

inbox-meeting-triage

Skill4 starsChanged 3 months agoMITView on GitHub

Triage personal email, Slack/Discord messages, calendar events, and meeting context into action items, daily plans, meeting prep notes, draft replies, and issue/task drafts. Use when the user asks to summarize inboxes, prepare for meetings, extract follow-ups, plan the day, or turn messages into tasks.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill to turn communication noise into a small set of decisions and actions.

    line 8
  2. Distinctive:

    Do not send replies automatically.

    line 34
  3. Distinctive:

    Do not create issues automatically.

    line 35
  4. Distinctive:

    Do not expose private message content in public-facing summaries.

    line 36

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Inbox Meeting Triage

Use this skill to turn communication noise into a small set of decisions and actions.

Workflow

  1. Gather supplied or configured sources.
    • Calendar events for time commitments.
    • Email messages for inbox actions.
    • Slack/Discord messages for chat actions.
    • Notion/Obsidian/memory for context.
  2. Classify each item.
    • Reply
    • Schedule
    • Decide
    • Delegate
    • Read later
    • Turn into issue/task
    • Archive/no action
  3. Draft outputs.
    • Meeting prep note.
    • Email/chat replies.
    • Issue/task drafts.
    • Obsidian-ready daily note section.
  4. Verify privacy.
    • Do not send replies automatically.
    • Do not create issues automatically.
    • Do not expose private message content in public-facing summaries.

Output Shape

Use compact sections:

  • Calendar
  • Inbox
  • Chat
  • Actions
  • Draft Replies
  • Issues/Tasks
  • Notes To Save

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.