Individual skill
connected-services-bridge
Connects approved external services such as Drive, GitHub, Notion, calendars, SharePoint, and Outlook through their available connectors. Use for: discovering connected-service capabilities, preparing a scoped integration, or completing a user-approved external action.
.grok/skills/connected-services-bridge/SKILL.md
Source commit bf31cc83a43ed8069d0d5070c68df4250273eb29
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 4, 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
- engineering Derived category
- productivity Derived category
- productivity-notes 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
CHANGELOG.mddoc · 191 bytesSKILL.mdcore · 2,403 bytes
Read excerpt
# Connected Services Bridge
Use this skill to discover available connected-service capabilities and perform **scoped, user-authorized** actions across approved services.
## Workflow
1. Identify the requested service, data scope, intended action, and expected output. Ask a focused question if any of these are ambiguous.
2. Discover the relevant connector and inspect its documented operation and parameter schema. Do not assume tool names, permissions, or data locations.
3. Use the least-privileged operation that can satisfy the request. Prefer a read-only check before any write.
4. For a consequential action, present the target service, destination, affected files or records, and rollback option. Obtain explicit approval before creating, updating, sending, deleting, committing, or sharing anything.
5. Perform the approved action. Verify the returned identifier, link, or status without exposing credentials, tokens, or private content.
6. Report the result, the exact scope completed, and any local fallback artifact if the service was unavailable.
## Reliability