DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to sync Skills bundled in npm packages (experimental) with Skills

Link Skills that ship inside npm dependencies into your project so they update with the package.

Authorization notice. Skills is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Remote script. Packages you sync can bring in Skills that instruct your agent, so review the linked SKILL.md files before your agent uses them.

Who it is forA developer whose project depends on an npm package that bundles instructions for coding agents, such as agent-browser in the README example.

The problemSkills shipped inside an npm package do not reach your agent unless you wire them up by hand, and they can go stale when the package updates.

The outcomePackaged Skills are linked into your project and follow the dependency version.

What you need first

  • Node.js 22.20 or later
  • A terminal opened in your project folder
  • A supported coding agent installed on your machine, such as Claude Code, Codex, or Cursor

Steps

  1. Install the package and the CLI as dev dependencies with npm install -D skills agent-browser.
  2. Run npx skills experimental_sync -y from the project folder.
  3. Check the linked Skills in the project and confirm they match the package version.
  4. Read docs/commands.md#skills-experimental_sync before relying on this feature, because the README says its behavior may change.

Prompt for your agent

In this project, run npm install -D skills <package name>, then npx skills experimental_sync -y. Report which skills were linked and confirm they came from the installed package. Note that this feature is experimental.

Caveat. The README labels this feature experimental and says its options and behavior may change, so pin your CLI version if you depend on it.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page