autonomous-sync-script
Skill0 starsChanged 3 months agoMITView on GitHub
Automate GitHub sync via Google Drive with a single command. Use when you need to commit and push code/skills to GitHub without manual file transfer. Uploads to Google Drive, then provides a one-line command for automatic commit and push. Apply automatically when the request matches; the user does not need to mention this skill.
- Installs packages
- Commits and pushes
In this repository76 other files it gives its agents.
- app-store-submission-packagerSkill
- digital-product-inventorSkill
- ios-testflight-github-actionsSkill
- meta-ads-analyzerSkill
- get-to-know-a-clientSkill
- investigate-before-recommendSkill
- production-system-auditSkill
- similarweb-analyticsSkill
- stock-analysisSkill
- system-architectSkill
- autonomous-github-syncSkill
- github-gem-seekerSkill
- organize-github-reposSkill
- using-git-worktreesSkill
- brainstorm-logosSkill
- brand-driven-ux-overhaulSkill
- canvas-designSkill
- excel-generatorSkill
- frontend-designSkill
- inspirational-music-video-productionSkill
- theme-factorySkill
- video-generatorSkill
- multiplayer-game-builderSkill
- promo-code-systemSkill
- realistic-ai-persona-builderSkill
- role-based-access-controlSkill
- serverless-debuggingSkill
- vertical-expansion-blueprintSkill
- manus-mcp-configuratorSkill
- mcp-auto-recoverySkill
- mcp-builderSkill
- mcp-connector-testerSkill
- mcp-ecosystem-optimizerSkill
- voice-ai-integrationSkill
- api-endpoint-builderSkill
- database-schema-generatorSkill
- testing-frameworkSkill
- deployment-automationSkill
- error-monitoring-setupSkill
- github-workflow-automationSkill
- analytics-dashboardSkill
- email-system-builderSkill
- feature-flag-systemSkill
- user-authentication-systemSkill
- cron-job-schedulerSkill
- file-upload-systemSkill
- notification-systemSkill
- payment-integrationSkill
- search-implementationSkill
- debug-mining-engineSkill
- doc-coauthoringSkill
- docxSkill
- internet-skill-finderSkill
- pdfSkill
- pptxSkill
- project-handoff-ingestionSkill
- serverless-debuggingSkill
- skill-arsenal-builderSkill
- skill-creatorSkill
- skill-demo-builderSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. About 0 are common, 13 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈13
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Read the task-specific instructions in this file before acting.
- Distinctive: line 23
Use this skill when:
- Distinctive: line 57
You: run the command on your local machine
- Distinctive: line 64
No direct GitHub API access needed from sandbox
- Distinctive: line 93
Follow OAuth flow to authenticate
- Distinctive: line 242
Use descriptive commit messages: - Follow Conventional Commits
- Distinctive: line 243
Review before running: - Check what Manus uploaded to Google Drive
- Very specific: line 244
Clean up old folders: - Delete old github-sync-* folders from Google Drive periodically
- Distinctive: line 245
Test with small changes: - Verify workflow before syncing large projects
- Distinctive: line 291
Only accessible to your Google account
- Distinctive: line 295
No credentials stored by script
- Distinctive: line 300
No sensitive data logged
- Distinctive: line 327
skill-development-workflow: - Create new skills
- Distinctive: line 329
organize-github-repos: - Verify GitHub repo alignment
≈ “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.
Files
Workflow
- Read the task-specific instructions in this file before acting.
- Apply the documented constraints, resources, and verification steps.
- Confirm the result against the requested outcome before completion.
Autonomous Sync Script
Overview
This skill automates the process of syncing files from Manus to your GitHub repository via Google Drive. Instead of manually downloading files and committing them, this skill uploads everything to Google Drive and provides a single command to run on your local machine that automatically downloads, commits, and pushes to GitHub.
Key Benefit: Turn a 6-step manual process into a single command.
When to Use This Skill
Use this skill when:
- Syncing new skills - Push newly created skills to your GitHub repo
- Updating existing code - Sync modified files to GitHub
- Batch operations - Sync multiple files/directories at once
- Automating workflow - Reduce manual steps in your development process
Quick Start
Step 1: Specify What to Sync (In Manus)
Tell Manus what files/directories to sync:
Sync /home/ubuntu/skills/my-new-skill to GitHubStep 2: Run the Command (On Your Local Machine)
Manus will provide a command like:
python3 ~/gdrive_to_repo_sync.py github-sync-1770720864 ~/my-repo "feat: add my-new-skill"Copy and run it. Done! ✅
How It Works
The Process:
- Manus uploads your files to Google Drive (timestamped folder)
- Manus gives you a one-line command with the folder name
- You run the command on your local machine
- Script downloads files from Google Drive
- Script copies files to your local Git repository
- Script commits and pushes to GitHub automatically
Why Google Drive?
- Bridge between Manus sandbox and your local machine
- No direct GitHub API access needed from sandbox
- You maintain full control over what gets committed
One-Time Setup
On Your Local Machine
1. Install rclone (if not already installed):
# macOS
brew install rclone
# Linux
sudo apt install rclone2. Configure rclone with Google Drive:
rclone configFollow prompts:
- Choose "n" for new remote
- Name it:
manus_google_drive - Choose "Google Drive"
- Follow OAuth flow to authenticate
3. Get the sync script:
The script is included in this skill at scripts/gdrive_to_repo_sync.py.
Copy it to your home directory:
cp /path/to/this/skill/scripts/gdrive_to_repo_sync.py ~/
chmod +x ~/gdrive_to_repo_sync.py4. Test the setup:
rclone lsd manus_google_drive:You should see your Google Drive folders listed.
Usage Examples
Example 1: Sync a Single Skill
In Manus:
Sync /home/ubuntu/skills/organize-github-repos to GitHubManus provides:
✅ Uploaded to Google Drive: github-sync-1770720864
📋 Run this command on your local machine:
python3 ~/gdrive_to_repo_sync.py github-sync-1770720864 ~/my-repo "feat: add organize-github-repos skill"You run:
python3 ~/gdrive_to_repo_sync.py github-sync-1770720864 ~/my-repo "feat: add organize-github-repos skill"Result:
✅ Downloaded from Google Drive
✅ Copied to repository
✅ Committed changes
✅ Pushed to GitHubExample 2: Sync Multiple Files
In Manus:
Sync these to GitHub:
- /home/ubuntu/skills/skill-a
- /home/ubuntu/skills/skill-b
- /home/ubuntu/docs/guide.mdManus handles the rest and provides the sync command.
Example 3: Custom Commit Message
In Manus:
Sync /home/ubuntu/project with commit message "fix: resolve authentication bug"Manus provides command with your custom message.
The Sync Script
Script Location
After setup: ~/gdrive_to_repo_sync.py
Script Usage
python3 ~/gdrive_to_repo_sync.py <gdrive-folder> <repo-path> "<commit-message>"Arguments:
<gdrive-folder>- Folder name from Manus (e.g.,github-sync-1770720864)<repo-path>- Path to your local Git repository (e.g.,~/my-repo)<commit-message>- Git commit message in quotes
What the Script Does
- Downloads files from Google Drive folder
- Copies to your local repository (preserving structure)
- Stages changes (
git add) - Commits with your message
- Pushes to origin (current branch)
- Cleans up temporary files
Troubleshooting
"rclone not found"
Solution: Install rclone
brew install rclone # macOS
sudo apt install rclone # Linux"Google Drive folder not found"
Check folder exists:
rclone lsd manus_google_drive: | grep github-syncCommon causes:
- Typo in folder name (case-sensitive)
- rclone not configured correctly
- Using wrong Google account
"Git push failed"
Solution: Set up GitHub authentication
gh auth login # Using GitHub CLI
# OR configure SSH keys"Permission denied"
Solution: Make script executable
chmod +x ~/gdrive_to_repo_sync.pyBest Practices
- Use descriptive commit messages - Follow Conventional Commits
- Review before running - Check what Manus uploaded to Google Drive
- Clean up old folders - Delete old
github-sync-*folders from Google Drive periodically - Test with small changes - Verify workflow before syncing large projects
- Keep script updated - Pull latest version if bugs are fixed
Advanced Usage
Sync to Specific Branch
cd ~/my-repo
git checkout feature-branch
python3 ~/gdrive_to_repo_sync.py <folder> . "commit message"Sync to Subdirectory
The script preserves directory structure from Google Drive.
In Manus, organize files in the structure you want:
/tmp/sync-package/
└── skills/
└── my-skill/
└── ...Result in repo: repo/skills/my-skill/...
Dry Run (Preview)
Modify script to add --dry-run flag:
if '--dry-run' in sys.argv:
print("Would commit:", files)
sys.exit(0)Security
Google Drive:
- rclone stores credentials securely
- Folders are timestamped (not predictable)
- Only accessible to your Google account
Git:
- Uses your existing authentication
- No credentials stored by script
- Standard
git push(SSH/HTTPS)
Files:
- Permissions preserved where possible
- No sensitive data logged
Limitations
- Requires local execution - Can't be fully autonomous without local agent
- Google Drive dependency - Adds latency vs direct GitHub API
- Manual branch management - Doesn't auto-create branches
- No conflict resolution - Requires manual intervention for conflicts
- Single remote - Pushes to
originonly
Future Enhancements
- Webhook-based automatic sync (no manual command)
- Direct GitHub API integration (bypass Google Drive)
- Automatic branch creation
- Conflict resolution
- Multi-remote support
- Notifications (Slack/Discord)
Related Skills
- skill-development-workflow - Create new skills
- autonomous-github-sync - Original implementation (this improves on it)
- organize-github-repos - Verify GitHub repo alignment
Support
Check Google Drive connection:
rclone about manus_google_drive:List sync folders:
rclone lsd manus_google_drive: | grep github-syncVerify Git repo:
cd ~/my-repo && git statusChangelog
v1.0.0 (2026-02-10)
- ✅ Initial release
- ✅ Google Drive upload automation
- ✅ One-command sync script
- ✅ Comprehensive documentation
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.

