Integrations
Google Drive integration
Your working docs.Ready for your agent.
Connect Google Drive to Claude Code, Codex, Cursor or any MCP agent through CoreSpeed. Your agent finds a working document in your Drive, reads Google Docs, Sheets and Slides as text, and turns them into a brief with the scope, the constraints and the open questions. It uses your own Google account and changes no file.
Give this to your agent
set up https://corespeed.io/SKILL.mdConnect Google Drive after setup. Access follows the connected account and its permissions.
From a folder of filesto a useful starting point.
Requests you can make once Google Drive is connected. The data is fictional.
- Google DriveSearch: rollout
- Acme rollout notesGoogle Doc · edited 2 days ago
- Acme rollout timelineGoogle Sheet · edited last week
- Onboarding checklistGoogle Doc · edited Oct 2
Find the working document
A file you can access
- Google DriveGoogle Doc
Acme rollout notes
- Scope: customer onboarding.
- Constraint: scope approval comes first.
- Still open: the launch date.
Read the useful context
No file changed
- CodexAnswer
Project brief
The useful part, together.
- Bring forward: goals and rollout constraints.
- Ask next: who approves the scope?
Start from a clear brief
Review before sharing
Find the context.Move the work forward.
Find the project document, read its context, and turn it into a brief you can use.
Reads fromGoogle Drive
All connectors →Find the Acme rollout Google Doc in Drive. Read its text and draft a brief with scope, constraints, and open questions. Do not change the file.
google-drive__list_filesok
Acme rollout notes · edited 2 days ago
Keep your agent.Bring your work.
One CoreSpeed account, across compatible agents.
- 1
Set up CoreSpeed
Give your agent the setup line. It adds CoreSpeed and signs you in.
- 2
Connect Google Drive
Authorize the account and the content you need.
- 3
Start with one task
Ask for a summary, a brief, or a draft. Review the answer.
Setup guidesClaude CodeCodexCursor