inbox/SKILL.md
# FAZM Inbox Agent Read ~/fazm/inbox/skill/AGENT-VOICE.md first — it has your persona, tone rules, examples, and investigation workflow. **Channel: Email (async, one-shot)** ## Workflow ### Step 1: Understand the email(s) Read all emails and the full thread history provided in the prompt. You may receive multiple unprocessed emails from the same user (e.g., they sent a bug report, then a follow-up, then a correction). Treat them as one batch: read all of them, then categorize the combined i
npx skillsauth add m13v/fazm inboxInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Read ~/fazm/inbox/skill/AGENT-VOICE.md first — it has your persona, tone rules, examples, and investigation workflow.
Channel: Email (async, one-shot)
Read all emails and the full thread history provided in the prompt. You may receive multiple unprocessed emails from the same user (e.g., they sent a bug report, then a follow-up, then a correction). Treat them as one batch: read all of them, then categorize the combined intent:
If the emails cover multiple categories (e.g., a bug report and a feature request), address all of them.
Follow the investigation workflow in AGENT-VOICE.md based on the category.
Send a reply via:
node ~/analytics/scripts/send-email.js \
--to "USER_EMAIL" \
--subject "Re: ORIGINAL_SUBJECT" \
--body "YOUR_REPLY" \
--product fazm
Follow all tone rules from AGENT-VOICE.md, plus these email-specific rules:
Send the report per AGENT-VOICE.md with subject: FAZM Inbox: RE_SUBJECT — FROM_EMAIL
node ~/fazm/inbox/scripts/mark-processed.js EMAIL_ID [EMAIL_ID2] [EMAIL_ID3]
Mark ALL email IDs from the batch, not just one.
Database (Neon Postgres):
psql "$DATABASE_URL" -c "YOUR QUERY"
Key tables: fazm_workflow_users (user records), fazm_emails (all messages)
PostHog:
curl -s -H "Authorization: Bearer $POSTHOG_PERSONAL_API_KEY" \
"https://us.posthog.com/api/projects/331630/events/?person_id=PERSON_ID&limit=50"
Email sending: ~/analytics/scripts/send-email.js (needs RESEND_API_KEY and DATABASE_URL from ~/analytics/.env.production.local)
development
# test-release: Smoke Test a Fazm Release Smoke test a Fazm release. Use when the user says "test the release", "smoke test", or "verify the build works". **This skill does NOT build anything.** It tests the shipped product via Sparkle auto-update. ## Channel → Machine Mapping Both the local production app (`/Applications/Fazm.app`) and the MacStadium remote are on the `staging` channel. Staging releases get tested on **both** machines; the primary test is the **local** machine (more reliabl
devops
Release a new version of OMI Desktop. Analyzes changes since last release, generates changelog, and runs the full release pipeline.
development
Maintainer-only workflow for handling GitHub Secret Scanning alerts on OpenClaw. Use when Codex needs to triage, redact, clean up, and resolve secret leakage found in issue comments, issue bodies, PR comments, or other GitHub content.
development
Maintainer workflow for OpenClaw releases, prereleases, changelog release notes, and publish validation. Use when Codex needs to prepare or verify stable or beta release steps, align version naming, assemble release notes, check release auth requirements, or validate publish-time commands and artifacts.