New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Ade Deeplinks

by arul28 in arul28/ADE

A skill your agent uses when an agent needs to mint, share, or open ADE deeplinks (lane, work session, file, commit, artifact, branch, PR, Linear issue) so users — or the agent itself — can jump…

AGPL-3.0Auto-check passedDevelopment

Install Ade Deeplinks

skills CLI
$ npx skills add arul28/ADE --skill ade-deeplinks -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install arul28/ADE ade-deeplinks --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/arul28/ADE.git skills-src && mkdir -p .claude/skills && cp -r skills-src/apps/desktop/resources/agent-skills/ade-deeplinks .claude/skills/ade-deeplinks && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
ade-deeplinks
GitHub stars
114
Token cost
~3.2k tokens
SKILL.md length
998 words
Files
1
Skills in repo
28
Repo updated
First seen
Licence
AGPL-3.0

At a glance

A skill your agent uses when an agent needs to mint, share, or open ADE deeplinks (lane, work session, file, commit, artifact, branch, PR, Linear issue) so users — or the agent itself — can jump…

  • An agent needs to mint
  • SKILL.md covers What a deeplink is, When to use which form, Minting a deeplink — ade link and Pairing a browser — ade sync web, plus 6 more sections
  • Reaches ade-app.dev
  • Open ADE deeplinks (lane

What it does

Ade Deeplinks is an agent skill from arul28/ADE. Use this skill when an agent needs to mint, share, or open ADE deeplinks (lane, work session, file, commit, artifact, branch, PR, Linear issue) so users — or the agent itself — can jump straight to a specific ADE surface from anywhere (GitHub PR description, Linear issue, Slack, email, terminal, mobile).

Its SKILL.md is about 3.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Pull requests. It works with Linear, GitHub and Slack. The licence is AGPL-3.0.

When your agent uses it

  • An agent needs to mint
  • Open ADE deeplinks (lane
  • Linear issue) so users —
  • The agent itself — can jump straight to a specific ADE surface from anywhere (GitHub PR description

Example prompts

  • “/ade-deeplinks”

What it can do on your machine

Read from SKILL.md and the folder at commit fbbd974. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash and jsonc).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • ade-app.dev

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Ade Deeplinks loads about 3.2k tokens when it runs. Until then it costs about 80 tokens; SKILL.md has 998 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~80
When it runs · the whole SKILL.md, loaded when a task matches
~3.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from arul28/ADE at commit fbbd974, republished under its AGPL-3.0 licence (© arul28). 998 words, ~3,173 tokens.

Download SKILL.mdSave it as .claude/skills/ade-deeplinks/SKILL.md (or your agent's skills folder).
name
ade-deeplinks
description
Use this skill when an agent needs to mint, share, or open ADE deeplinks (lane, work session, file, commit, artifact, branch, PR, Linear issue) so users — or the agent itself — can jump straight to a specific ADE surface from anywhere (GitHub PR description, Linear issue, Slack, email, terminal, mobile).

ADE deeplinks are URLs that route directly to a specific ADE entity. Two forms, identical semantics:

ade://lane/<uuid>                                # local-only — focuses an existing lane
ade://session/<id>[?lane=<lane-uuid>&event=<n>&offset=<bytes>]  # Work session + anchors
ade://file/<repo-relative-path>[?line=<n>&lane=<lane-uuid>]      # Files tab
ade://commit/<sha>[?lane=<lane-uuid>]            # Lanes git detail, or GitHub fallback with envelope
ade://artifact/<artifact-id>                     # local proof/history artifact
ade://repo/<owner>/<repo>/branch/<branch>        # cross-machine — find or offer-to-create lane
ade://pr/<owner>/<repo>/<number>                 # PR detail view
ade://linear-issue/<ADE-123>[?branch=<branch>]   # Linear handoff — opens the Linear pane

https://ade-app.dev/open?type=lane&id=<uuid>
https://ade-app.dev/open?type=session&id=<id>[&lane=<lane-uuid>]
https://ade-app.dev/open?type=file&path=<path>[&line=<n>&lane=<lane-uuid>]
https://ade-app.dev/open?type=commit&sha=<sha>[&lane=<lane-uuid>]
https://ade-app.dev/open?type=artifact&id=<artifact-id>
https://ade-app.dev/open?type=branch&repo=<owner/repo>&branch=<branch>[&pr=<n>]
https://ade-app.dev/open?type=pr&repo=<owner/repo>&number=<n>
https://ade-app.dev/open?type=linear-issue&issue=<ADE-123>[&branch=<branch>]

The HTTPS form is the share-friendly variant (it gets a Vercel-rendered OpenGraph card in Slack/Discord/iMessage/Gmail/Linear). The web landing page tries the ade:// upgrade and falls back to an install card. Both forms parse to the same target shape.

Lane, session, commit, and artifact ids are local — the UUID/id is meaningful only on the machine that created it. ADE can attach an envelope to local links as query params:

repo=<owner>/<repo>&branch=<branch>&pr=<number>&linear=<ADE-123>

The envelope does not change the primary target; it gives receivers a portable fallback chain. If the local id is unknown, ADE can offer to switch to the matching project, create/open the branch or PR, open the Linear issue, or open a commit on GitHub. Branch links are portable — they fetch/import the remote branch as a lane if the receiver does not have it yet. Linear-issue links are portable — they open ADE's Linear pane for the issue and show setup if the active project has not connected Linear.

When to use which form

NeedUse
Jump back to MY lane from another terminal on the same Macade://lane/<uuid>
Jump back to a Work session on this Macade://session/<id>
Jump to a chat event or terminal scrollback byte offsetade://session/<id>?event=<n> / ?offset=<bytes>
Open a file and reveal a lineade://file/src/app.ts?line=42
Open a commit from a local lane or GitHub fallbackade://commit/<sha>?lane=<uuid>&repo=owner/repo
Open a local proof artifact/history entryade://artifact/<artifact-id>
Share a branch with a teammate or your other deviceshttps://ade-app.dev/open?type=branch&…
Drop into a PR's detail tabhttps://ade-app.dev/open?type=pr&…
Linear "Open in coding tool" hand-off (opens Linear pane)https://ade-app.dev/open?type=linear-issue&…
bash
ade link lane <lane-uuid>                                  # local lane link
ade link session <session-id> [--lane <lane-uuid>]          # local Work session link
ade link file <path> [--line N] [--lane <lane-uuid>]        # file link
ade link commit <sha> [--lane <lane-uuid>]                  # commit link
ade link artifact <id>                                      # proof/history artifact
ade link branch <owner/repo> <branch> [--pr <number>]      # cross-machine branch
ade link pr <owner/repo> <number>                          # PR detail
ade link linear-issue <ADE-123> [--branch <branch>]        # Linear hand-off
ade link <url>                                             # round-trip an existing link

# Flags
--ade            # emit ade:// instead of https:// (default: https)
--no-envelope    # skip best-effort repo/branch/PR envelope lookup
--web            # emit the hosted web client URL (https://app.ade-app.dev/...)
--no-clipboard   # print without copying

Every form copies to the clipboard by default and prints the URL to stdout. When a live ADE runtime is bound, ade link lane, session --lane, and commit --lane attach repo/branch/PR envelope params best-effort. Use --no-envelope to skip that lookup and --no-clipboard in scripts.

Concrete examples:

bash
ade link file apps/desktop/src/shared/deeplinks.ts --line 12 --ade --no-clipboard
ade link commit abc1234 --lane 550e8400-e29b-41d4-a716-446655440000 --no-clipboard

Pairing a browser — ade sync web

Run ade sync web --text on, or pointed at, an ADE machine to print the web-client pairing link and 6-digit code. Open the link in any browser, enter the code, and the ADE web client (Work, Lanes, Files, PRs) pairs to that machine — the browser analogue of scanning the phone pairing QR.

Use --open to launch the pairing link in the default browser. Human output copies the link by default; add --no-clipboard for scripts. The same link from desktop Settings > Sync > Web client or the iOS "Pair a browser" screen does the same thing.

bash
ade open <url>                                             # any ade:// or https://ade-app.dev/open URL
ade open --linear-issue <ADE-123> --branch <branch>        # Linear coding-tool entry point

The CLI hands the URL to the OS, which routes through the registered ade:// protocol back to a running ADE desktop window (or launches ADE cold). If the focused window's project doesn't match the deeplink's repo, the cross-repo banner appears with a "Switch to <project>" button.

Wiring Linear hand-off — ade linear install

bash
ade linear install               # writes ~/.linear/coding-tools.json
ade linear install --dry-run     # show what would be written

Adds an entry so Linear's "Open issue in coding tool" picker can launch ADE. The template uses Linear's documented placeholders ({{issue.identifier}}, {{issue.branchName}}) — Linear does NOT expose the GitHub repo, so the desktop renderer opens the active project's Linear pane to the issue. If the project is not connected to Linear yet, ADE shows a setup modal that routes to Settings > Integrations > Linear.

RPC for programmatic dispatch

For agents working through the ADE RPC layer, deeplinks dispatch via the existing app/navigate method:

jsonc
// JSON-RPC over the ADE socket (`ade serve` / desktop RPC port)
{ "method": "app/navigate", "params": {
    "target": { "kind": "lane", "laneId": "<uuid>" }
}}
{ "method": "app/navigate", "params": {
    "target": { "kind": "work", "sessionId": "<session-id>", "laneId": "<uuid>" }
}}
{ "method": "app/navigate", "params": {
    "target": { "kind": "file", "path": "src/app.ts", "line": 42, "laneId": "<uuid>" }
}}
{ "method": "app/navigate", "params": {
    "target": { "kind": "commit", "sha": "<sha>", "laneId": "<uuid>", "envelope": { "repoOwner": "anthropics", "repoName": "claude-code", "branch": "feat-x" } }
}}
{ "method": "app/navigate", "params": {
    "target": { "kind": "artifact", "artifactId": "<artifact-id>" }
}}
{ "method": "app/navigate", "params": {
    "target": { "kind": "branch", "repoOwner": "anthropics", "repoName": "claude-code", "branch": "feat-x" }
}}
{ "method": "app/navigate", "params": {
    "target": { "kind": "pr", "repoOwner": "anthropics", "repoName": "claude-code", "prNumber": 1234 }
}}
{ "method": "app/navigate", "params": {
    "target": { "kind": "linear-issue", "issueIdentifier": "ADE-123", "branch": "arul/ade-123-feat" }
}}

Use app/navigate (not deeplinks.open) when you have structured fields. Use ade open <url> when you already have a stringified deeplink (e.g. something a user pasted).

Show full SKILL.md (410 more words)Show less

ADE automatically appends an "Open in ADE" footer to PR descriptions it creates or adopts (idempotent via an HTML marker), and pushes ADE lane/chat links with repo envelopes to any Linear issue linked to the lane (Linear attachment + one-time comment). Agents do not need to call ade link for those flows — they fire on PR creation / Linear-link events.

Linear card/comment matrix:

Linear-related actionWho adds the ADE link
ade lanes create --linear-issue-json / ade lanes create-from-linearADE posts the lane attachment/comment
ade lanes link-linear-issue / ade chat attach-linear-issue / ade linear attach --this-sessionADE posts lane/chat attachments when a lane/session is known
ade chat create --from-linear-issue or ade lanes create-from-linear --start-chatADE posts the chat attachment after the issue is attached
ade prs create on a linked laneADE posts the PR attachment/footer
ade linear comment, set-state, assign, label, or graphqlThe agent should include the relevant ADE link in any Linear comment it writes

If you create new Linear state directly (for example with ade linear graphql), mint the Linear-pane link yourself and comment it back to the issue:

bash
ade link linear-issue ADE-123 --no-clipboard
ade linear comment ADE-123 "Created via ADE. Open in ADE: <paste link>"

When handing off a newly created or adopted PR, include both links: the GitHub PR URL (githubUrl / html_url) and the ADE PR link. ade prs create prints the ADE link as adeUrl; for a PR that came from another path, mint it:

bash
ade link pr <owner/repo> <number> --no-clipboard

Prefer the default HTTPS form in chat, PR comments, and terminal output: it is clickable and shareable, and on a machine with ADE installed it upgrades into ade://pr/<owner>/<repo>/<number> and lands in the PRs tab. The PR body also gets the automatic "Open in ADE" footer, but that footer is not a substitute for the links in your final message.

When you copy a deeplink from the desktop UI, the lane right-click menu offers Copy lane link, Copy branch link (cross-machine), Copy PR link, and Copy Linear-issue link. The Work session context menu also offers Copy session deep link for returning to the selected terminal/chat session on the same desktop.

  • Clone a repository you don't have — the user always confirms via the inbound modal that reuses the PRs-tab "Create lane from PR branch" preflight (with its existing safety blocks).
  • Mutate state for pure navigation — opening an existing lane is silent; creating one is not.
  • Trust the URL params blindly — the parser rejects bad UUIDs, traversal segments, malformed Linear identifiers, and non-https hosts on the mirror form.

Quick command palette for the CTO

bash
# Mint links the user can paste anywhere
ade link branch anthropics/claude-code feat-deeplinks               # share with teammates
ade link pr anthropics/claude-code 1234                             # PR detail
ade link linear-issue ADE-512 --branch arul/ade-512-feat            # Linear hand-off
ade link file apps/desktop/src/shared/deeplinks.ts --line 12         # source location
ade link commit abc1234 --lane <lane-uuid>                           # commit detail
ade link artifact proof-123                                          # proof/history artifact
ade link session <session-id> --lane <lane-uuid>                    # Work session
ade link lane "$(ade lanes list --text | head -2 | tail -1 | awk '{print $1}')"  # current lane

# Open a link locally (any of these reach a running ADE)
ade open ade://lane/<uuid>
ade open ade://session/<session-id>
ade open "https://ade-app.dev/open?type=branch&repo=a/b&branch=feat"
ade open --linear-issue ADE-123 --branch feat-x

# One-time setup so Linear's "Open in coding tool" calls into ADE
ade linear install

© arul28, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in apps/desktop/resources/agent-skills/ade-deeplinks of arul28/ADE.

Open the folder on GitHubat commit fbbd974

Compare with similar skills

Ade Deeplinks next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Ade Deeplinks compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Ade Deeplinks this skillarul28/ADE114—~3.2kAutomated safety check: PassAGPL-3.0
Draft Pull Request Creatorwordpress-mobile/WordPress-Android3.2k—~881Automated safety check: NotesGPL-2.0
Process PR Reviewsnexu-io/nexu3.3k—~2.5kAutomated safety check: PassMIT
Managing Git Workflowhashintel/hash1.7k—~1.2kAutomated safety check: PassAGPL-3.0
Human Writingkylesnowschwartz/SimpleClaude114—~4kAutomated safety check: PassNone
Linear PRnesszer/linear-cli138—~364Automated safety check: NotesMIT

Similar skills

  • Draft Pull Request Creator

    wordpress-mobile/WordPress-Android

    Commits and pushes current changes, writes a pull request title and body from the branch history and template, and opens a draft PR on GitHub after you approve it.

    3.2k GitHub stars~881 tokensUpdated today
    DevelopmentAuto-check: notes

  • Process PR Reviews

    nexu-io/nexu

    A skill your agent uses when the user asks to process, triage, fetch, view, count, list, or resolve review feedback in a GitHub PR.

    3.3k GitHub stars~2.5k tokensUpdated 5 mo ago
    DevelopmentAuto-check passed

  • Managing Git Workflow

    hashintel/hash

    Git and pull-request workflow for HASH, including conditional Linear conventions and merge-queue diagnostics.

    1.7k GitHub stars~1.2k tokensUpdated today
    DevelopmentAuto-check passed

  • Human Writing

    kylesnowschwartz/SimpleClaude

    A skill your agent uses when writing or editing a Slack message, email, pull request body, GitHub issue, Reddit post, agenda, or doc.

    114 GitHub stars~4k tokensUpdated 3 days ago
    DevelopmentAuto-check passed

  • Linear PR

    nesszer/linear-cli

    Create GitHub PRs linked to Linear issues. An agent skill from nesszer/linear-cli.

    138 GitHub stars~364 tokensUpdated 24 days ago
    DevelopmentAuto-check: notes

  • Linear Work Rhythm

    langfuse/langfuse

    Answer "what should I do today" for a Langfuse maintainer, from the tracker rather than from memory: which projects you lead, which owe an update before the Monday engineering weekly, what shipped…

    36k GitHub stars~3.4k tokensUpdated today
    AI & LLM EngineeringAuto-check passed

More from arul28/ADE

All 28 skills in this repo

  • Ade App Control

    arul28/ADE

    A skill your agent uses when you need to run or drive a local Electron/desktop app and capture what it does — launch it or attach to a running renderer, read its logs or answer its terminal prompts…

    114 GitHub stars~3.4k tokensUpdated today
    Auto-check passed

  • Ade Autoresearch

    arul28/ADE

    Iteratively optimize an ADE tab's CPU/memory/IPC/render performance.

    114 GitHub stars~4.2k tokensUpdated today
    Auto-check passed

  • Ade Browser

    arul28/ADE

    A skill your agent uses for any browser behavior at all — opening a URL, checking a localhost page, clicking or filling a form, logging in, screenshotting, inspecting the DOM, or verifying a page…

    114 GitHub stars~3.3k tokensUpdated today
    Auto-check passed

  • Ade Harnesses

    arul28/ADE

    A skill your agent uses when you need to run a chat, a CLI session, or a subagent on a specific setup — any model you pay for inside any harness (e.g.

    114 GitHub stars~1.6k tokensUpdated today
    Auto-check passed

  • Ade Lanes Git

    arul28/ADE

    A skill your agent uses when creating, inspecting, syncing, committing, pushing, archiving, or rebasing ADE lanes and lane worktrees through ade lanes and ade git.

    114 GitHub stars~594 tokensUpdated today
    Auto-check passed

  • Ade Linear

    arul28/ADE

    A skill your agent uses whenever your task is a Linear issue (or an ADE chat/lane launched with a Linear issue attached) and you need to read or update that issue — change its workflow state…

    114 GitHub stars~2k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Ade Deeplinks

What does Ade Deeplinks do?

A skill your agent uses when an agent needs to mint, share, or open ADE deeplinks (lane, work session, file, commit, artifact, branch, PR, Linear issue) so users — or the agent itself — can jump…. Ade Deeplinks is an agent skill from arul28/ADE. Use this skill when an agent needs to mint, share, or open ADE deeplinks (lane, work session, file, commit, artifact, branch, PR, Linear issue) so users — or the agent itself — can jump straight to a specific ADE surface from anywhere (GitHub PR description, Linear issue, Slack, email, terminal, mobile).

When should I use Ade Deeplinks?

Ade Deeplinks fits situations like: an agent needs to mint; open ADE deeplinks (lane; linear issue) so users —; the agent itself — can jump straight to a specific ADE surface from anywhere (GitHub PR description.

How do I install Ade Deeplinks in Claude Code?

Run `npx skills add arul28/ADE --skill ade-deeplinks -a claude-code`. Or copy the skill folder (apps/desktop/resources/agent-skills/ade-deeplinks in arul28/ADE) into .claude/skills/ade-deeplinks in your project. Claude Code loads it when a task matches its description.

How do I install Ade Deeplinks in Codex?

Run `npx skills add arul28/ADE --skill ade-deeplinks -a codex`. Or copy the skill folder (apps/desktop/resources/agent-skills/ade-deeplinks in arul28/ADE) into .agents/skills/ade-deeplinks in your project. Codex loads it when a task matches its description.

Can I use Ade Deeplinks in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add arul28/ADE --skill ade-deeplinks -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ade-deeplinks, .gemini/skills/ade-deeplinks, .github/skills/ade-deeplinks and .opencode/skills/ade-deeplinks in your project.

What does Ade Deeplinks need to run?

SKILL.md names no scripts, command-line tools or credentials: Ade Deeplinks is instructions for the agent only.

Does Ade Deeplinks access the network?

SKILL.md names 1 domain. In commands or code: ade-app.dev; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Ade Deeplinks safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Ade Deeplinks use?

Ade Deeplinks is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Ade Deeplinks use?

About 3.2k tokens (SKILL.md is roughly 13k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Ade Deeplinks?

Skills that share tags, products or a category with Ade Deeplinks: Draft Pull Request Creator (wordpress-mobile/WordPress-Android, 3.2k stars), Process PR Reviews (nexu-io/nexu, 3.3k stars), Managing Git Workflow (hashintel/hash, 1.7k stars) and Human Writing (kylesnowschwartz/SimpleClaude, 114 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Ade Deeplinks?

arul28 (a GitHub user) maintains it in arul28/ADE, which has 114 GitHub stars. The repository holds 28 skills in this directory. The repository was last updated on October 8, 2026.

Source: arul28/ADE on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.