New: 97,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

Devtools Import Boundary

by LedgerHQ in LedgerHQ/ledger-live

Enforce import boundaries inside the devtools scope. An agent skill from LedgerHQ/ledger-live.

MITAuto-check passed

Install Devtools Import Boundary

skills CLI
$ npx skills add LedgerHQ/ledger-live --skill devtools-import-boundary -a claude-code

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

GitHub CLI
$ gh skill install LedgerHQ/ledger-live devtools-import-boundary --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/LedgerHQ/ledger-live.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/devtools-import-boundary .claude/skills/devtools-import-boundary && 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
devtools-import-boundary
GitHub stars
621
Token cost
~674 tokens
SKILL.md length
316 words
Files
1
Skills in repo
50
Repo updated
First seen
Licence
MIT

At a glance

Enforce import boundaries inside the devtools scope. An agent skill from LedgerHQ/ledger-live.

  • Any work in devtools/
  • SKILL.md covers Rules, Why, Consequences of a violation and Correct pattern, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Devtools Import Boundary is an agent skill from LedgerHQ/ledger-live. Enforce import boundaries inside the devtools scope. Use for any work in "devtools/".

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

The repository describes itself as: Mono-repository for Ledger Wallet apps and related packages. The licence is MIT.

When your agent uses it

  • Any work in devtools/

Example prompts

  • “devtools/”
  • “/devtools-import-boundary”

What it can do on your machine

Read from SKILL.md and the folder at commit a3861a2. 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.

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

  • Network

    No URLs in SKILL.md.

    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

Devtools Import Boundary loads about 674 tokens when it runs. Until then it costs about 28 tokens; SKILL.md has 316 words of instructions outside code blocks.

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

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 LedgerHQ/ledger-live at commit a3861a2, republished under its MIT licence (© LedgerHQ). 316 words, ~674 tokens.

Download SKILL.mdSave it as .claude/skills/devtools-import-boundary/SKILL.md (or your agent's skills folder).
name
devtools-import-boundary
description
Enforce import boundaries inside the devtools scope. Use for any work in "devtools/**".

DevTools import boundaries

Every @devtools/* package is self-contained. The only permitted cross-package imports within the devtools scope are listed in the table below; all others are forbidden.

Rules

PackageMay import from @devtools/*
@devtools/registryany @devtools/<tool>
@devtools/shell@devtools/transport, @devtools/registry
@devtools/bindings@devtools/registry only
@devtools/wire@devtools/transport, @devtools/protocols
@devtools/protocols@devtools/transport only
@devtools/relay@devtools/transport only
@devtools/transport-panel@devtools/transport only
@devtools/<tool>none

All other @devtools/* → @devtools/* imports are forbidden.

Why

The devtools architecture decouples tools from the shell through the registry. The shell lazy-loads tools via metadata.loader; tools never know the shell exists. If a tool imports the shell or another tool directly:

  • The lazy-load boundary collapses — the tool is bundled eagerly.
  • A circular dependency becomes likely (tool → shell → registry → tool).
  • The tool can no longer be rendered standalone, outside the shell.

If bindings or shell import a tool package directly (instead of through the registry):

  • The registry's discriminated union is bypassed and TypeScript loses the narrowing guarantee on DevToolsConfig.
  • The import() split point disappears, defeating code-splitting.

Consequences of a violation

  • Tool imports shell or registry: The tool becomes coupled to shell internals; standalone rendering and unit-testing break.
  • Tool imports another tool: Cross-tool coupling; removing or renaming one tool requires editing the other.
  • Shell or bindings import a tool directly: Eager bundle; code-split lost; registry union integrity broken.

Correct pattern

Cross-cutting concerns (shared types, utilities) must not live in a tool package. Extract them to a standalone library with no @devtools/* scope, then import that from whichever packages need it.

App state and wiring for a tool arrive as props, built in @devtools/bindings — the single sanctioned bridge to Ledger Live internals. A tool that needs more data from the app gets new props, not a new import.

Documentation

When adding a new package under devtools/, its README.md must state:

  • Which @devtools/* packages it may import, per the table above.
  • That all other @devtools/* imports are forbidden, with a pointer to this rule.

© LedgerHQ, MIT. 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 .agents/skills/devtools-import-boundary of LedgerHQ/ledger-live.

Open the folder on GitHubat commit a3861a2

Compare with similar skills

Devtools Import Boundary 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.

Devtools Import Boundary compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Devtools Import Boundary this skillLedgerHQ/ledger-live621—~674Automated safety check: PassMIT
Importasgeirtj/system_prompts_leaks69k—~3.5kAutomated safety check: PassCC0-1.0
Nx Importnrwl/nx29k5 repos~3.5kAutomated safety check: PassMIT
Enforce Rules For Typescriptmoeru-ai/airi50k—~3.4kAutomated safety check: PassMIT
Type Only Importsthedaviddias/Front-End-Checklist74k—~558Automated safety check: PassMIT
Import Memoryasgeirtj/system_prompts_leaks69k—~2.7kAutomated safety check: WarnCC0-1.0

Similar skills

  • Import

    asgeirtj/system_prompts_leaks

    Handle explicit /import requests for read-only transcript recovery and a resume checkpoint, or continue work from other coding agents and unnamed artifacts.

    69k GitHub stars~3.5k tokensUpdated 2 days ago
    Agent WorkflowsAuto-check passed

  • Nx Import

    nrwl/nx

    Import, merge, or combine repositories into an Nx workspace using nx import.

    29k GitHub starsUsed in 5 repos~3.5k tokens
    DevelopmentAuto-check passed

  • Enforce Rules For Typescript

    moeru-ai/airi

    Enforce AIRI's TypeScript and Vue source rules for imports, naming, comments, JSDoc, fallbacks, stateful and protocol code, and module design.

    50k GitHub stars~3.4k tokensUpdated today
    DevelopmentAuto-check passed

  • Type Only Imports

    thedaviddias/Front-End-Checklist

    A skill your agent uses when auditing import statements in TypeScript files, setting up a new TypeScript project, or investigating unexpected bundle inclusions from type-only dependencies.

    74k GitHub stars~558 tokensUpdated yesterday
    Auto-check passed

  • Import Memory

    asgeirtj/system_prompts_leaks

    Import a memory export from another AI assistant into Claude's memory — conversationally, additively, and with the content treated as data.

    69k GitHub stars~2.7k tokensUpdated 2 days ago
    Auto-check: warnings

  • Hermes Imports

    affaan-m/ECC

    Convert local Hermes operator workflows into sanitized ECC skills and release-pack artifacts.

    274k GitHub starsUsed in 1 repo~752 tokens
    Auto-check passed

More from LedgerHQ/ledger-live

All 50 skills in this repo

  • Impacting PRs

    LedgerHQ/ledger-live

    Find which open PRs are impacted by a migration/sunset/refactor and notify their authors — blocking review when the old path is already gone from develop, heads-up comment when it is only deprecated…

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

  • Cloud Sync Module

    LedgerHQ/ledger-live

    Write, review or debug a cloudSyncModule.ts — a CloudSyncDataManager that syncs one slice of user data through Ledger Sync (Cloud Sync).

    621 GitHub stars~2.4k tokensUpdated today
    Auto-check passed

  • Codeownership

    LedgerHQ/ledger-live

    Maintain CODEOWNERS file and team directories. An agent skill from LedgerHQ/ledger-live.

    621 GitHub stars~687 tokensUpdated today
    Auto-check passed

  • Coin Families Contract

    LedgerHQ/ledger-live

    Coin-specific families logic must live in families/. An agent skill from LedgerHQ/ledger-live.

    621 GitHub stars~1k tokensUpdated today
    Auto-check passed

  • Data Layer Advanced

    LedgerHQ/ledger-live

    Structure a Ledger Wallet data layer where one API response serves several entities.

    621 GitHub stars~509 tokensUpdated today
    Auto-check passed

  • Debug Rn Native Crash

    LedgerHQ/ledger-live

    Investigate native React Native crashes (Fabric/Hermes/iOS) in ledger-live-mobile when JS error logs are missing or unhelpful.

    621 GitHub stars~1.2k tokensUpdated today
    Auto-check passed

Questions about Devtools Import Boundary

What does Devtools Import Boundary do?

Enforce import boundaries inside the devtools scope. An agent skill from LedgerHQ/ledger-live. Devtools Import Boundary is an agent skill from LedgerHQ/ledger-live. Enforce import boundaries inside the devtools scope.

When should I use Devtools Import Boundary?

Devtools Import Boundary fits situations like: any work in devtools/.

How do I install Devtools Import Boundary in Claude Code?

Run `npx skills add LedgerHQ/ledger-live --skill devtools-import-boundary -a claude-code`. Or copy the skill folder (.agents/skills/devtools-import-boundary in LedgerHQ/ledger-live) into .claude/skills/devtools-import-boundary in your project. Claude Code loads it when a task matches its description.

How do I install Devtools Import Boundary in Codex?

Run `npx skills add LedgerHQ/ledger-live --skill devtools-import-boundary -a codex`. Or copy the skill folder (.agents/skills/devtools-import-boundary in LedgerHQ/ledger-live) into .agents/skills/devtools-import-boundary in your project. Codex loads it when a task matches its description.

Can I use Devtools Import Boundary 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 LedgerHQ/ledger-live --skill devtools-import-boundary -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/devtools-import-boundary, .gemini/skills/devtools-import-boundary, .github/skills/devtools-import-boundary and .opencode/skills/devtools-import-boundary in your project.

What does Devtools Import Boundary need to run?

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

Does Devtools Import Boundary access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Devtools Import Boundary 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 Devtools Import Boundary use?

Devtools Import Boundary is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Devtools Import Boundary use?

About 674 tokens (SKILL.md is roughly 2.7k 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 Devtools Import Boundary?

Skills that share tags, products or a category with Devtools Import Boundary: Import (asgeirtj/system_prompts_leaks, 69k stars), Nx Import (nrwl/nx, 29k stars), Enforce Rules For Typescript (moeru-ai/airi, 50k stars) and Type Only Imports (thedaviddias/Front-End-Checklist, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Devtools Import Boundary?

LedgerHQ (a GitHub organization) maintains it in LedgerHQ/ledger-live, which has 621 GitHub stars. The repository holds 50 skills in this directory. The repository was last updated on October 7, 2026.

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