agentleFS
ArgentAIOSArgentAIOS/agent-skills/vip-email/SKILL.md

vip-email

Skill4 starsChanged 8 months agoMITView on GitHub

Configure and operate VIP Gmail monitoring with deduped alerts, cron scanning, and gog OAuth fallback.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use the vip_email tool to monitor high-priority senders in Gmail and alert once per new message.

    line 14
  2. Very specific:

    If vip_email reports setupRequired: true, switch to the gog skill and complete OAuth:

    line 18
  3. Very specific:

    Remove VIP: vip_email action remove_vip

    line 44
  4. Very specific:

    Read and clear queued items: vip_email action check_pending (clear defaults true)

    line 45

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

vip-email

Use the vip_email tool to monitor high-priority senders in Gmail and alert once per new message.

First run (required)

If vip_email reports setupRequired: true, switch to the gog skill and complete OAuth:

  • gog auth credentials /path/to/client_secret.json
  • gog auth add you@gmail.com --services gmail,calendar,drive,contacts,docs,sheets
  • gog auth list --json

Then return to vip_email.

Core setup

  1. Add VIP senders:
    • vip_email action add_vip with email and optional name
  2. Set allowed inbox accounts (optional; defaults to discovered gog accounts):
    • vip_email action set_accounts with accounts
  3. Configure alerts:
    • vip_email action set_alerts with:
      • ttsEnabled (true/false)
      • channelRoutes array (channel, target, optional accountId, bestEffort)
  4. Install monitor cron:
    • vip_email action ensure_cron_monitor with optional intervalSeconds

Operations

  • Health/status: vip_email action status
  • Manual scan now: vip_email action scan_now
  • List VIPs: vip_email action list_vips
  • Remove VIP: vip_email action remove_vip
  • Read and clear queued items: vip_email action check_pending (clear defaults true)
  • Disable monitor cron: vip_email action disable_cron_monitor
  • Reset dedupe set: vip_email action clear_seen

Notes

  • Dedupe is key-based per account+message id; the same email should not alert twice.
  • Pending queue defaults to /tmp/vip-email-pending.json for downstream processors.
  • Cron monitor runs isolated and invokes vip_email scan action.

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.