searching-documents-with-google-drive
Search and download documents from Google Drive using rclone. Exports Google Docs as Markdown by default. Use when users ask to find files in Google Drive, download documents from Drive, export Google Docs, or sync Drive content locally. Triggers on requests mentioning Google Drive, gdrive, or document downloads from cloud storage.
What this skill does
# Google Drive Document Access ## Overview Search for and download documents from Google Drive using rclone. Google Docs are automatically exported as Markdown for easy reading and processing. Scripts are located at `scripts/`. **Reference Documentation:** - [scripts/](scripts/) — Shell scripts for search, download, and sync operations - [digital-science-reference.md](digital-science-reference.md) — Digital Science documentation links **Authentication:** See the Authentication section in [digital-science-reference.md](digital-science-reference.md) for rclone setup. The remote must be named `gdrive`. ## Quick Start ```bash # Check rclone is configured ./scripts/check_rclone.sh # Search for files ./scripts/search_gdrive.sh "meeting notes" # Search shared files ./scripts/search_gdrive.sh "standup" --shared # Download a file (exports Google Docs as Markdown) ./scripts/download_gdrive.sh "Documents/Report" ./output # Download by file ID ./scripts/download_gdrive.sh --id "FILE_ID" ./output # Download matching shared files ./scripts/download_gdrive.sh --shared --include "pattern*" ./output ``` ## Common Tasks | Task | Command | |------|---------| | Check setup | `./scripts/check_rclone.sh` | | Search files | `./scripts/search_gdrive.sh "pattern"` | | Search shared files | `./scripts/search_gdrive.sh "pattern" --shared` | | Download file | `./scripts/download_gdrive.sh "path/to/file" ./output` | | Download by ID | `./scripts/download_gdrive.sh --id "FILE_ID" ./output` | | Download folder | `./scripts/download_gdrive.sh "Folder" ./output --bulk` | | Download shared files | `./scripts/download_gdrive.sh --shared --include "pattern*" ./output` | | Limit downloads | `./scripts/download_gdrive.sh --shared --include "pattern*" ./output --limit 20` | ## Export Formats Google Docs can be exported in different formats: | Format | Flag | Use Case | |--------|------|----------| | Markdown | `--format md` (default) | Easy reading and processing | | Word | `--format docx` | Office compatibility | | PDF | `--format pdf` | Final documents | | Plain text | `--format txt` | Minimal formatting | | HTML | `--format html` | Web content | Example: `./scripts/download_gdrive.sh "Report" ./output --format docx` ## File ID Extraction Extract file IDs from Google Drive URLs: - `https://docs.google.com/document/d/FILE_ID/edit` → use FILE_ID - `https://drive.google.com/file/d/FILE_ID/view` → use FILE_ID ## Preview Before Download Use dry-run to see what would be downloaded: ```bash ./scripts/download_gdrive.sh "Large Folder" ./output --bulk --dry-run ``` ## Direct rclone Commands For advanced use cases: ```bash rclone ls gdrive:"Documents" # List files rclone lsjson gdrive:"path" --no-traverse # Get file info as JSON rclone sync gdrive:"Source" ./local --drive-export-formats md # Sync folder ``` ## Troubleshooting | Issue | Solution | |-------|----------| | "remote not configured" | Run `rclone config` to set up gdrive remote | | "Cannot connect" | Run `rclone config reconnect gdrive:` | | Empty search results | Check path spelling; try searching from root | | File not downloading | Verify file permissions; check if file is in Trash | | Shared files not found | Use `--shared` flag | | Too many files | Use `--limit N` to download only N most recent |
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.