skills/automation-skills/autonomous-sync-script/SKILL.md
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.
npx skillsauth add abcnuts/manus-skills autonomous-sync-scriptInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
4 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.
Use this skill when:
Tell Manus what files/directories to sync:
Sync /home/ubuntu/skills/my-new-skill to GitHub
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! ✅
The Process:
Why Google Drive?
1. Install rclone (if not already installed):
# macOS
brew install rclone
# Linux
sudo apt install rclone
2. Configure rclone with Google Drive:
rclone config
Follow prompts:
manus_google_drive3. 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.py
4. Test the setup:
rclone lsd manus_google_drive:
You should see your Google Drive folders listed.
In Manus:
Sync /home/ubuntu/skills/organize-github-repos to GitHub
Manus 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 GitHub
In Manus:
Sync these to GitHub:
- /home/ubuntu/skills/skill-a
- /home/ubuntu/skills/skill-b
- /home/ubuntu/docs/guide.md
Manus handles the rest and provides the sync command.
In Manus:
Sync /home/ubuntu/project with commit message "fix: resolve authentication bug"
Manus provides command with your custom message.
After setup: ~/gdrive_to_repo_sync.py
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 quotesgit add)Solution: Install rclone
brew install rclone # macOS
sudo apt install rclone # Linux
Check folder exists:
rclone lsd manus_google_drive: | grep github-sync
Common causes:
Solution: Set up GitHub authentication
gh auth login # Using GitHub CLI
# OR configure SSH keys
Solution: Make script executable
chmod +x ~/gdrive_to_repo_sync.py
github-sync-* folders from Google Drive periodicallycd ~/my-repo
git checkout feature-branch
python3 ~/gdrive_to_repo_sync.py <folder> . "commit message"
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/...
Modify script to add --dry-run flag:
if '--dry-run' in sys.argv:
print("Would commit:", files)
sys.exit(0)
Google Drive:
Git:
git push (SSH/HTTPS)Files:
origin onlyCheck Google Drive connection:
rclone about manus_google_drive:
List sync folders:
rclone lsd manus_google_drive: | grep github-sync
Verify Git repo:
cd ~/my-repo && git status
tools
Generate comprehensive demonstrations showing how to access projects and work across different environments (Manus terminals, personal computers, team collaboration). Use when users ask "how do I access this from another terminal/computer", "how do I share this with my team", "how do I get this on my Mac", or need clarification on Manus persistence vs GitHub usage.
development
Use when you have a spec or requirements for a multi-step task, before touching code
data-ai
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
development
Use when implementing any feature or bugfix, before writing implementation code