claudeaceae/.claude/skills/email
.claude/skills/email/SKILL.md
--- name: email description: Check and manage email inbox. Use when checking for unread emails, triaging inbox, handling spam, or managing email actions. Trigger words: email, inbox, mail, unread, messages, spam, unsubscribe. context: fork allowed-tools: - Bash - Read - WebFetch --- # Email Inbox Management Check your email, triage messages, and take action on your inbox. ## Step 1: Run Email Triage ```bash ~/.claude-mind/system/bin/email-triage ``` This fetches all unread emails and
$ install --global
skillsauthnpx skillsauth add claudeaceae/samara-main .claude/skills/emailInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 24, 2026, 8:50 PM1.7s1 file scanned
SKILL.md
- name:
- description:
- Check and manage email inbox. Use when checking for unread emails, triaging inbox, handling spam, or managing email actions. Trigger words: email, inbox, mail, unread, messages, spam, unsubscribe.
- context:
- fork
Email Inbox Management
Check your email, triage messages, and take action on your inbox.
Step 1: Run Email Triage
~/.claude-mind/system/bin/email-triage
This fetches all unread emails and categorizes them:
- GitHub Invitations: Org/repo invites - accept these promptly
- Actionable: Direct correspondence, support tickets - may need response
- GitHub Notifications: PR comments, mentions - usually handled via API, can archive
- Marketing/Spam: Unsubscribe aggressively, then delete
- Informational: Receipts, shipping - archive after noting relevant info
Step 2: Handle GitHub Invites First
These are high priority - someone is waiting:
# List pending repo invites
gh api user/repository_invitations --jq '.[] | {id: .id, repo: .repository.full_name}'
# Accept a repo invite
gh api -X PATCH user/repository_invitations/INVITE_ID
# List pending org invites
gh api user/memberships/orgs --jq '.[] | select(.state == "pending") | {org: .organization.login}'
# Accept org invite
gh api -X PATCH user/memberships/orgs/ORG_NAME -f state=active
After accepting, mark the invite emails as read.
Step 3: Handle Marketing/Spam
Be aggressive - unsubscribe and delete:
# Unsubscribe (uses browser automation)
~/.claude-mind/system/bin/email-unsubscribe "UNSUBSCRIBE_URL"
# Delete the email
~/.claude-mind/system/bin/email-action delete EMAIL_ID
For bulk marketing, process all of them. Don't leave spam sitting in inbox.
Step 4: Handle Actionable Emails
For emails that need response or attention:
- If it requires a reply, draft and send via
~/.claude-mind/system/bin/send-email - If it's informational but important, note it in today's episode
- If no action needed, archive or mark read
~/.claude-mind/system/bin/email-action archive EMAIL_ID
~/.claude-mind/system/bin/email-action mark-read EMAIL_ID
Step 5: Archive GitHub Notifications
These are already handled via the GitHub API during wake cycles:
~/.claude-mind/system/bin/email-action archive EMAIL_ID
Mindset
- Inbox zero is the goal - process everything, don't let emails pile up
- Unsubscribe liberally - if it's marketing, get off the list
- GitHub invites matter - someone extended trust, respond promptly
- Security emails - read carefully, don't click suspicious links
- When in doubt, archive - better than deleting if you might need it
Quick Check
If just doing a status check, report:
- Unread count by category
- Any urgent items (invites, security alerts)
- Whether inbox needs attention or is clean
Related Skills
claudeaceae/.claude/skills/webhook
development
VerifiedTrustedCommunity
# /webhook --- name: webhook description: Manage webhook sources - list, add, test, and view incoming events context: fork triggers: - webhook - add webhook - create webhook - webhook setup - incoming webhooks --- Manage the webhook receiver system. Use this skill to add new webhook sources, test existing ones, and view incoming events. ## What You Can Do 1. **List sources** - Show all registered webhook sources 2. **Add source** - Create a new webhook source with secure secret 3.
9SKILL.mdUpdated Apr 16, 2026
claudeaceae/wallet
testing
VerifiedTrustedCommunity
Check crypto wallet balances, transaction history, and addresses
9SKILL.mdUpdated Apr 16, 2026
claudeaceae/.claude/skills/voice-call
testing
VerifiedTrustedCommunity
# /voice-call - FaceTime Voice Calling Place and receive FaceTime Audio calls with live transcription and voice/text responses. ## Quick Start ```bash # Full voice conversation (responds via FaceTime audio) ~/.claude-mind/system/bin/voice-call --voice-response # Call with text responses (via iMessage) ~/.claude-mind/system/bin/voice-call --text-response # Call a specific number ~/.claude-mind/system/bin/voice-call +15551234567 --voice-response ``` ## Prerequisites Run `audio-setup --check
9SKILL.mdUpdated Apr 16, 2026
claudeaceae/.claude/skills/sync
tools
VerifiedTrustedCommunity
--- name: sync description: Check for drift between repo and running system. Use when checking if scripts or Samara are out of sync, verifying system integrity, or before/after rebuilds. Trigger words: sync, organism sync, check drift, system drift, repo sync. context: fork allowed-tools: - Bash - Read - Grep --- # Sync Skill Check for drift between the repo and running system, and optionally fix it. ## What This Does Runs the `sync-organism` script to detect differences between: - `~/
9SKILL.mdUpdated Apr 16, 2026