agent-deep-links
- Repo stars 11,183
- Author repo awesome-codex-skills
Agent Deep Links
Overview
Use this skill when a user asks for clickable links that should open directly in an app (usually from Slack). This includes verifying whether a target app supports deep links at all, selecting the right URL shape, and providing fallbacks when deep links are unsupported.
Workflow
- Identify target app + target object:
- Thread/conversation
- File/folder
- Settings/new window
- Read
references/deep-link-matrix.mdfor known-good link formats and support level. - If support is unknown, verify locally before sending:
- Check URL schemes in the app bundle:
/usr/libexec/PlistBuddy -c 'Print :CFBundleURLTypes' /Applications/<App>.app/Contents/Info.plist - Smoke test launch behavior:
open '<scheme>://...'
- Check URL schemes in the app bundle:
- Construct Slack-safe link syntax:
<url|label>
- If unsupported or uncertain, send a fallback:
- Plain path + command
- Documented CLI open command
- Statement that no official deep-link format is known
Output Rules
- Prefer absolute paths for file/folder links.
- Keep labels short and action-oriented (
Open in Cursor,Open in Codex). - Do not claim deep-link support unless it is in the matrix or just verified.
- For uncertain app routes, clearly mark as inferred/experimental.
Common Templates
- Codex thread:
<codex://threads/<thread-uuid>|Open in Codex>
- Cursor file:
<cursor://file/<absolute-path>:<line>:<column>|Open in Cursor>
- VS Code file:
<vscode://file/<absolute-path>:<line>:<column>|Open in VS Code>
- VS Code Insiders file:
<vscode-insiders://file/<absolute-path>:<line>:<column>|Open in VS Code Insiders>
Use references/deep-link-matrix.md for the full cross-app matrix and support notes.
- Fluxly category
- AI
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 88 / 100 · heuristic scan, not runtime safety proof
- Author / version / license
- @ComposioHQ · no license declared
- Fluxly token estimate
- Lean
- Fluxly setup estimate
- Guided setup
- External API key
- No requirement detected
- Detected OS requirements
- Unspecified
- Runtime requirements
- Unspecified
- Detected file/system behavior
-
- Read-only
- Shell exec
- Detected network behavior
- Local-only
- Install commands
- None (reference only)
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools,默认拥有全部工具权限。
The current SKILL.md does not define a fixed output example. Use this skill when a user asks for clickable links that should open directly in an app (usually from Slack). This includes verifying whether a target app supports deep links at all, selecting the right URL shape, and providing fallbacks when deep links are…
Identify target app + target object: Thread/conversation File/folder
Prefer absolute paths for file/folder links. Keep labels short and action-oriented (Open in Cursor, Open in Codex). Do not claim deep-link support unless it is in the matrix or just verified.
Codex thread: <codex://threads/<thread-uuid>|Open in Codex> Cursor file:
# Agent Deep Links
## Overview
Use this skill when a user asks for clickable links that should open directly in an app (usually from Slack). This includes verifying whether a target app supports deep links at all, selecting the right URL shape, and providing fallbacks when deep links are unsupported.
## Workflow
1. Identify target app + target object:
- Thread/conversation
- File/folder
- Settings/new window
2. Read `references/deep-link-matrix.md` for known-good link formats and support level.
3. If support is unknown, verify locally before sending:
- Check URL schemes in the app bundle:
```bash
/usr/libexec/PlistBuddy -c 'Print :CFBundleURLTypes' /Applications/<App>.app/Contents/Info.plist
```
- Smoke test launch behavior:
```bash
open '<scheme>://...'
```
4. Construct Slack-safe link syntax:
- `<url|label>`
5. If unsupported or uncertain, send a fallback:
- Plain path + command
- Documented CLI open command
- Statement that no official deep-link format is known
## Output Rules
- Prefer absolute paths for file/folder links.
- Keep labels short and action-oriented (`Open in Cursor`, `Open in Codex`).
- Do not claim deep-link support unless it is in the matrix or just verified.
- For uncertain app routes, clearly mark as inferred/experimental.
## Common Templates
- Codex thread:
- `<codex://threads/<thread-uuid>|Open in Codex>`
- Cursor file:
- `<cursor://file/<absolute-path>:<line>:<column>|Open in Cursor>`
- VS Code file:
- `<vscode://file/<absolute-path>:<line>:<column>|Open in VS Code>`
- VS Code Insiders file:
- `<vscode-insiders://file/<absolute-path>:<line>:<column>|Open in VS Code Insiders>`
Use `references/deep-link-matrix.md` for the full cross-app matrix and support notes. Author text anchors workflow facts; Fluxly only indexes current sections, terms, files, and commands.
sections -> Overview → Workflow → Output Rules → Common Templates
terms -> Use this skill when a user asks for clickable links that should open directly in an app (usually from Slack). · 1. Identify target app + target object: - Thread/conversation - File/folder - Settings/new window 2. · - Prefer absolute paths for file/folder links. · Use references/deep-link-matrix.md for the full cross-app matrix and support notes.
files/cmd -> references/deep-link-matrix.md · <url|label> · Open in Cursor · Open in Codex · <codex://threads/<thread-uuid>|Open in Codex> · <cursor://file/<absolute-path>:<line>:<column>|Open in Cursor> · <vscode://file/<absolute-path>:<line>:<column>|Open in VS Code> · <vscode-insiders://file/<absolute-path>:<line>:<column>|Open in VS Code Insiders>
body sha256 -> 06a64a3f18eb
Decide Fit First
Design Intent
How To Use It
Boundaries And Review