Individual skill

hybrid-execution-bridge

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.

.grok/skills/hybrid-execution-bridge/SKILL.md

Read pinned source

Source commit bf31cc83a43ed8069d0d5070c68df4250273eb29

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: Yes
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Instructions only
Last checked: Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 14
Repository last updated: Oct 21, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

agent-skills Repository topic
ai-agents Repository topic
grok Repository topic
prompt-engineering Repository topic
workflow-automation Repository topic
research Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 3,284 bytes

Read excerpt


# 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

1. Decompose the task into local, sandbox, connected-service, and public-web steps.
2. Use sandbox tools for code, documents, data processing, and ordinary public research whenever sufficient.
3. Use a local desktop bridge only after the user authorizes the scope and the bridge health check succeeds.
4. Use connected services only for the accounts and operations the user has approved.
5. Use responsible browsing methods; stop at login walls, CAPTCHAs, paywalls, or other access restrictions.
6. Present planned external writes, uploads, messages, deployments, or publications for explicit approval before carrying them out.