krystophny/sloptools

sloptools

Local Go binary that exposes mail, calendar, contacts, tasks, canvas, handoff, items/artifacts/actors, workspace, and temp-file operations as a CLI. The same surface that the sloppy MCP daemon serves on 127.0.0.1:9420 (the MCP server is named sloppy; the CLI binary and this skill are named sloptools), but driven directly from bash instead of via an MCP client.

Use this skill whenever the user asks for anything involving:

• email (Gmail, Exchange/EWS, IMAP) — list / get / send / reply / flag / categorize / server-side filters / out-of-office
• calendars and events (Google, ICS) — list / range queries / freebusy / create / update / delete / RSVP / ICS export
• contacts and contact groups
• tasks (Google Tasks, Todoist) and task lists
• the slopshell canvas (open session, render artifact, status)
• handoffs between agents (handoff.create|peek|consume|revoke|status)
• workspace items, artifacts, actors, triage, assignment
• short-lived temp files under .sloptools/artifacts/tmp

Discover

sloptools tools list                       # tabular: name<TAB>description
sloptools tools list --format json         # full JSON Schema array (use jq to grep)
sloptools tools list --format json | jq '.[] | select(.name | test("mail_"))'

Call a tool

Three argument styles, pick whichever is cleanest:

# whole arguments object as JSON
sloptools tools call mail_message_list --args '{"folder":"INBOX","limit":20}'

# arguments from a file
sloptools tools call mail_send --args-file /tmp/draft.json

# repeated key=value flags (each value parses as JSON if it parses, else string)
sloptools tools call calendar_events --arg days=7 --arg query="standup"

Stdout is the tool's structuredContent (preferred) or joined text content. Exit code: 0 success, 1 tool-level error (isError=true), 2 JSON-RPC / invocation error (unknown tool, bad args).

Common recipes

# recent mail, compact metadata only
sloptools tools call mail_message_list --args '{"sphere":"work","folder":"INBOX","limit":10}'
sloptools tools call mail_message_list --args '{"sphere":"private","folder":"INBOX","limit":10}'

# read one full message body after choosing it from the compact list
sloptools tools call mail_message_get --args '{"sphere":"work","message_id":"<id>"}'

# send a reply
sloptools tools call mail_reply --args-file /tmp/reply.json

# next 7 days of events, compact list without descriptions
sloptools tools call calendar_events --arg days=7

# create an event
sloptools tools call calendar_event_create --args '{"calendar_id":"primary","summary":"Standup","start":"2026-04-26T09:00:00+02:00","end":"2026-04-26T09:15:00+02:00"}'

# read a contact by id
sloptools tools call contact_get --arg id="people/c1234"

# create a handoff payload for another agent
sloptools tools call handoff.create --args '{"kind":"file","payload":{"path":"/tmp/draft.md"}}'

Notes

• The store lives at ~/.local/share/sloppy/sloppy.db; pass --data-dir if you need an alternate data dir.
• Prefer sphere (work / private) for read/list operations. Use account_id only when a specific account is required or when sending/mutating mail.
• For "recent email" requests, start with folder:"INBOX" and limit:5 or limit:10; do not add a days filter unless the user asks for a date window.
• Keep list calls small: limit 5-10 for mail and calendar triage. mail_message_list is metadata-only by default; use mail_message_get for a chosen message, or include_body=true only when a full list with bodies is explicitly needed.
• Do not run multiple sloptools tools call processes in parallel; the direct CLI uses the local SQLite store and serialized calls avoid lock contention.
• For account management itself: sloptools external-account list|add|update|remove.
• Mail operations route to whichever provider is configured for the chosen account (Gmail OAuth, EWS, IMAP) — the same surface the MCP daemon uses, no protocol differences.
• sloptools mail send and sloptools mail reply are convenience flag-driven wrappers; tools call mail_send is the direct route when arguments are already in JSON form.