[BUG] Cowork: bundled Google Drive skill leads with a curl/script route that returns 401 (no credential in the sandbox shell); connector tools work

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report
• [x] I am using the latest version of Claude Desktop

What's Wrong?

Product: Cowork (Claude Desktop) with the Google Drive connector and its bundled Google Drive skill.

The bundled Google Drive skill tells the agent to start with its bundled scripts / a curl route to the Drive API. In the Cowork sandbox, that route returns 401 Unauthorized, because no Google credential is available to the shell. The connector's own tools (for example create_file) work in the same session. Following the skill wastes turns on a route that can't work there, and the agent has to find the connector tools by trial and error.

Seen in two separate sessions.

What Should Happen?

In environments where the shell has no Drive credential (Cowork), the skill should send the agent to the connector's tools first. Or the scripted route should get a credential, or fail with a message saying to use the connector tools instead.

Error Messages/Logs

HTTP 401 Unauthorized (from the skill's scripted / curl route to the Drive API)

Steps to Reproduce

1. Connect Google Drive in Cowork.
2. Ask the agent to create a file in Drive. It loads the bundled Google Drive skill and follows its scripted route, which returns 401.
3. Ask it to use the connector's create_file tool instead: that works.

Claude Model

Not sure / Multiple models

Is this a regression?

I don't know

Claude Desktop Version

2.26454.2 when observed; current 2.31226.1

Operating System

Windows 11 Pro

Related

#95292 (separate issue: update_file can't replace a file's content).