Hybrid Execution Bridge
Purpose
Use this skill to plan work that may span sandbox processing, user-approved local resources, connected services, and public-web research. Select the least-privileged environment for each step and keep external actions explicit.
Routing workflow
- Decompose the task into local, sandbox, connected-service, and public-web steps.
- Use sandbox tools for code, documents, data processing, and ordinary public research whenever sufficient.
- Use a local desktop bridge only after the user authorizes the scope and the bridge health check succeeds.
- Use connected services only for the accounts and operations the user has approved.
- Use responsible browsing methods; stop at login walls, CAPTCHAs, paywalls, or other access restrictions.
- Present planned external writes, uploads, messages, deployments, or publications for explicit approval before carrying them out.
- Summarize which environments were used, what data moved between them, and any limitations.
Environment selection
| Need |
Preferred environment |
Boundary |
| Code, files, reports, or data analysis |
Sandbox |
Keep data within the task workspace unless the user authorizes export. |
| Existing user session, local software, or local files |
Authorized desktop bridge |
Verify scope and connection health; never assume access. |
| Drive, GitHub, or other connected account |
Connected-service integration |
Read first; require approval for writes or publication. |
| Public web information |
Browser or approved research tool |
Respect access restrictions and site rules. |
Local desktop safeguards
When a user-authorized desktop bridge is needed, ask for clear permission, run its documented health check, and limit operations to the agreed files or application. Do not request or expose raw tokens in summaries. Stop immediately if the connection fails or the user revokes permission.
Error handling
| Situation |
Response |
| Local bridge is unavailable |
Continue with sandbox alternatives and state the limitation. |
| Connected service lacks authorization |
Do not retry with another account; ask the user to authorize or choose a local alternative. |
| Website presents a restriction |
Stop automated access and explain the permitted options. |
| External action is pending |
Present scope, destination, and user-visible effect; wait for approval. |
Output
Return the execution plan, selected environments, authorization boundaries, completed work, and pending external actions. Do not claim that local, cloud, or connected-service work occurred unless it was verified.
1---2name: hybrid-execution-bridge3description: Coordinate authorized work across sandbox tools, a user-approved local desktop, connected services, and public-web research. Use for: hybrid execution, local plus sandbox, connected services, scoped desktop access.4license: MIT5---67# Hybrid Execution Bridge89## Purpose1011Use this skill to plan work that may span sandbox processing, user-approved local resources, connected services, and public-web research. Select the least-privileged environment for each step and keep external actions explicit.1213## Routing workflow14151. Decompose the task into local, sandbox, connected-service, and public-web steps.162. Use sandbox tools for code, documents, data processing, and ordinary public research whenever sufficient.173. Use a local desktop bridge only after the user authorizes the scope and the bridge health check succeeds.184. Use connected services only for the accounts and operations the user has approved.195. Use responsible browsing methods; stop at login walls, CAPTCHAs, paywalls, or other access restrictions.206. Present planned external writes, uploads, messages, deployments, or publications for explicit approval before carrying them out.217. Summarize which environments were used, what data moved between them, and any limitations.2223## Environment selection2425| Need | Preferred environment | Boundary |26|---|---|---|27| Code, files, reports, or data analysis | Sandbox | Keep data within the task workspace unless the user authorizes export. |28| Existing user session, local software, or local files | Authorized desktop bridge | Verify scope and connection health; never assume access. |29| Drive, GitHub, or other connected account | Connected-service integration | Read first; require approval for writes or publication. |30| Public web information | Browser or approved research tool | Respect access restrictions and site rules. |3132## Local desktop safeguards3334When a user-authorized desktop bridge is needed, ask for clear permission, run its documented health check, and limit operations to the agreed files or application. Do not request or expose raw tokens in summaries. Stop immediately if the connection fails or the user revokes permission.3536## Error handling3738| Situation | Response |39|---|---|40| Local bridge is unavailable | Continue with sandbox alternatives and state the limitation. |41| Connected service lacks authorization | Do not retry with another account; ask the user to authorize or choose a local alternative. |42| Website presents a restriction | Stop automated access and explain the permitted options. |43| External action is pending | Present scope, destination, and user-visible effect; wait for approval. |4445## Output4647Return the execution plan, selected environments, authorization boundaries, completed work, and pending external actions. Do not claim that local, cloud, or connected-service work occurred unless it was verified.
Stijnman