agent deep links

AI Community

Skill notes

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.md for known-good link formats and support level.

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:

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
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
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@ComposioHQ · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Author source file SKILL.md

# 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.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.