tidy
AGENTS.md2 starsChanged 3 months agoMITView on GitHub
Verify gog CLI is installed and authenticated: All scripts in scripts/ support DRY_RUN=true for preview mode.
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 32,671 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository10 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- gmail-analyzeSkill
- gmail-classifySkill
- gmail-filterSkill
- gmail-labelSkill
- gogSkill
- prj-drive-cleanupSkill
- prj-driveSkill
- prj-gmail-cleanupSkill
- prj-inboxSkill
The file
We split this AGENTS.md into the rules it gives an agent
7 rules. About 0 are common, 3 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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
- Distinctive: line 5
Verify gog CLI is installed and authenticated:
- Very specific: line 106
All scripts in scripts/ support DRY_RUN=true for preview mode.
- Very specific: line 118
Always dry-run first: DRY_RUN=true ./scripts/script.sh
- Very specific: line 119
Use category filter: CATEGORY=promotions DRY_RUN=true ./scripts/ai_categorize.sh
- Distinctive: line 121
Ask user before executing bulk operations
- Distinctive: line 122
Keep emails in inbox (don't archive unless asked)
- Very specific: line 127
Check uncategorized count: gog gmail search "has:nouserlabels" --max 1 --plain
≈ “Common” is an estimate: at least 1 in 5 of the 41,581 AGENTS.md 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.
Files
Tidy - Agent Instructions
Prerequisites
Verify gog CLI is installed and authenticated:
gog gmail labels listCommands
Gmail
/inbox- Quick status (uncategorized count)/gmail-cleanup- Full workflow (analyze → propose → execute)gmail-analyzeskill - Inbox pattern analysisgmail-classifyskill - AI email classificationgmail-filterskill - Create/manage Gmail filtersgmail-labelskill - Create labels + batch-apply
Google Drive
/drive- Quick status (storage, recent files, files in root)/drive-cleanup- Full workflow (analyze → organize → cleanup)
Skills Reference
| Skill | When to load |
gog | Any gog CLI command reference |
prj-inbox | Quick inbox check |
prj-gmail-cleanup | Full cleanup workflow |
prj-drive | Quick Drive check |
prj-drive-cleanup | Full Drive cleanup |
gmail-analyze | Finding patterns in unlabeled emails |
gmail-classify | Categorizing emails by content |
gmail-filter | Setting up automation rules |
gmail-label | Label taxonomy + batch operations |
Label Hierarchy
Finance/ Investments, Taxes, Insurance, Payments
Services/ Tech, Gaming, Automotive, Shopping
Projects/ Travel, Purchases, Legal
Admin/ Security, Jobs, Notifications
Status/ Pending, Important, ArchiveCommon gog Commands
# List all labels
gog gmail labels list
# Create new label
gog gmail labels create "Category/Sub"
# Add label to thread
gog gmail labels modify THREAD_ID --add "Label"
# Search unlabeled emails
gog gmail search "has:nouserlabels" --max 100 --plain
# Create filter
gog gmail settings filters create --from "domain.com" --add-label "Label"
# Search by Gmail category (unlabeled only)
gog gmail search "in:promotions has:nouserlabels -in:spam -in:trash" --max 100 --plain
gog gmail search "in:social has:nouserlabels -in:spam -in:trash" --max 100 --plain
gog gmail search "in:updates has:nouserlabels -in:spam -in:trash" --max 100 --plain
# Primary only (exclude all categories)
gog gmail search "has:nouserlabels -in:promotions -in:social -in:updates -in:forums -in:spam -in:trash" --max 100 --plainCommon gog Drive Commands
# Storage info
gog drive about --plain
# List files
gog drive ls --plain # Root folder
gog drive ls --parent=FOLDER_ID --plain # Specific folder
gog drive ls --query="mimeType='application/vnd.google-apps.folder'" --plain # Folders only
# Search and filter
gog drive search "filename" --max=100 --plain
gog drive ls --query="modifiedTime<'2023-01-01'" --max=100 --plain # Old files
gog drive ls --query="quotaBytesUsed>104857600" --max=50 --plain # Large files (>100MB)
gog drive ls --query="'root' in parents" --plain # Files in root
# File operations
gog drive get FILE_ID --json # Metadata
gog drive mkdir "Name" --parent=PARENT_ID # Create folder
gog drive move FILE_ID --parent=DEST_ID # Move file
gog drive delete FILE_ID # To trash
gog drive rename FILE_ID "NewName" # Rename
# Permissions
gog drive permissions FILE_ID --plain # Check sharingScripts
All scripts in scripts/ support DRY_RUN=true for preview mode.
| Script | Purpose |
scripts/categorize_emails.sh | Label emails by sender domain (supports CATEGORY env var) |
scripts/ai_categorize.sh | Pattern-match subjects and senders (supports CATEGORY env var) |
scripts/migrate_labels.sh | Migrate old label structure |
scripts/drive_organize.sh | Create standard Drive folder hierarchy |
scripts/gmail_core.py | Python Gmail operations (stdlib only, no deps) |
Best Practices
- Always dry-run first:
DRY_RUN=true ./scripts/script.sh - Use category filter:
CATEGORY=promotions DRY_RUN=true ./scripts/ai_categorize.sh- Options:
promotions,social,updates,primary,all
- Options:
- Ask user before executing bulk operations
- Keep emails in inbox (don't archive unless asked)
- Report results summary after operations
Workflow
- Check uncategorized count:
gog gmail search "has:nouserlabels" --max 1 --plain - Analyze patterns in unlabeled emails
- Propose label assignments to user
- Execute with user approval
- Report summary
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
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.

