Skip to content
Agentmart
Submit a tool

clawflow-inbox-triage

Example ClawFlow authoring pattern for inbox triage.

Skill by S3YED

IndexedMIT★ 12
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/s3yed-clawflow-inbox-triage

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Example ClawFlow authoring pattern for inbox triage. Use when messages need different treatment based on intent, with some routes notifying immediately, some waiting on outside answers, and others rolling into a later summary.

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/clawflow-inbox-triage

What's inside

Skill name
clawflow-inbox-triage
Description
Example ClawFlow authoring pattern for inbox triage. Use when messages need different treatment based on intent, with some routes notifying immediately, some waiting on outside answers, and others rolling into a later summary.
License
MIT
Instructions
58 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# ClawFlow inbox triage

This is a concrete example of how to think about ClawFlow without turning the core runtime into a DSL.

## Goal

Triage inbox items with one owner flow:

- business → post to Slack and wait for reply
- personal → notify the owner now
- everything else → keep for end-of-day summary

## Pattern

1. Create one flow for the inbox batch.
2. Run one detached task to classify new items.
3. Resume the flow when classification completes.
4. Route each item in the calling logic.
5. Persist only the summary bucket and the current wait target.

## Suggested flow outputs

- `business_threads`
- `personal_items`
- `eod_summary`

## Minimal runtime calls

```ts
const flow = createFlow({
  ownerSessionKey,
  goal: "triage inbox",
});

runTaskInFlow({
  flowId: flow.flowId,
  runtime: "acp",
  task: "Classify inbox messages",
  currentStep: "wait_for_classification",
});

resumeFlow({
  flowId: flow.flowId,
  currentStep: "route_items",
});

appendFlowOutput({
  flowId: flow.flowId,
  key: "eod_summary",
  value: { subject: "Newsletter", route: "later" },
});
```

## Related example

- `skills/clawflow/examples/inbox-triage.lobster`

From S3YED/appie-kit, MIT.

More from S3YED/appie-kit

Signals

Stars
12
Forks
2
Open issues
0
Last commit (this folder)
May 8, 2026 (5 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
Website
weblyfe.ai
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from S3YED

Cite this page

clawflow-inbox-triage skill. Agent Mart. https://agentmart.dev/skills/s3yed-clawflow-inbox-triage (last updated 2026-10-24)