Installation

Choose an installation method

The homepage offers Agent, MCP, and Command line. Agent provides an installation prompt, MCP connects your tool to the free catalog, and Command line installs the published ZIP with the open-source skills CLI. Choose Codex, Claude Code, or Cursor to get the matching instructions.

Choose one method and follow it through verification. The examples below use Orbit Wallet and automatically include this website’s address and the published Skill version. Use the homepage to choose a different Skill or agent. The current free collection does not require an account.

For a manual installation, download the ZIP, inspect its contents, and extract the product folder into the Skills directory supported by your tool. Do not install only SKILL.md: its references and runnable source are part of the package.

Install with Agent

1. Open your target project in the coding agent so it can inspect the project and write files there.
2. On the homepage, choose Agent, your tool, and a Skill. Copy its installation prompt. The Codex example below installs Orbit Wallet.
3. Send the prompt to that agent. It reads install.md, inspects the ZIP, and installs the complete folder in the project’s Skills directory. If that Skill is already present, compare and back it up before replacing anything.
4. Ask it to report the installed path and version and confirm discovery. If discovery has not refreshed, start a new agent session in the same project.

Read https://skills.onebtcdesign.com/demos/orbit-wallet/install.md. Install the orbit-wallet Skill into .agents/skills/ for this Codex project. Inspect the package, preserve existing installations, and verify Skill discovery.

For this example, success means .agents/skills/orbit-wallet/ contains SKILL.md, references/, and project/, and Codex can read the installed Skill. A copied prompt alone does not mean installation is complete.

Connect with MCP

The public endpoint is /api/mcp on this website, using standard Streamable HTTP. Choose MCP and your agent on the homepage to copy the full connection command or configuration with the current website’s address.

The read-only tools search_skills, get_skill, and get_installation provide free-Skill discovery, details, installation URLs, and commands. Connecting does not write files to your computer or install a Skill by itself. Ask your agent to install a chosen Skill separately; this MCP server has no financial transaction or account permissions.

1. Choose MCP and your tool on the homepage, or copy the matching configuration below. The address is filled from the website you are reading.
2. For Codex or Claude Code, open a terminal in the target project and run its connection command with the tool’s CLI installed. Claude Code uses its default local project scope. For Cursor, merge the JSON into .cursor/mcp.json without removing existing servers.
3. Refresh the MCP connection or start a new agent session. Confirm that jesn-design-skills exposes search_skills, get_skill, and get_installation.
4. Send the discovery example below to your agent. Review the Skill details and installation destination before choosing to install.
5. Ask your local agent to perform the installation separately, using the returned instructions. Back up an existing copy first, then verify the installed Skill.

codex mcp add jesn-design-skills --url 'https://skills.onebtcdesign.com/api/mcp'

claude mcp add --transport http jesn-design-skills 'https://skills.onebtcdesign.com/api/mcp'

Cursor’s example is file content, not a terminal command. If .cursor/mcp.json already has mcpServers, add the jesn-design-skills entry inside that object.

{
  "mcpServers": {
    "jesn-design-skills": {
      "url": "https://skills.onebtcdesign.com/api/mcp"
    }
  }
}

Use the jesn-design-skills MCP server.
Call search_skills with query "wallet", then read orbit-wallet with get_skill.
Use get_installation for skillId "orbit-wallet" and agent "codex".
Show me the Skill details and installation destination before installing.

The example requests Codex instructions. Use agent "claude-code" or "cursor" for those tools. When you have chosen the Skill and destination, send a separate install request:

Install orbit-wallet in the current project using the MCP installation instructions for my agent.
Inspect the ZIP first. If the target already exists, back it up and ask before replacing it.
After installation, report the path and version, read SKILL.md and its references, and confirm that the agent discovers the Skill.

MCP is connected when the agent can call the tools and return real catalog results. Skill installation is a separate success check: confirm the local files and discovery after running the install request.

Install from the terminal

1. Check node --version in your terminal. The skills@1.7.4 CLI requires Node.js 22.20 or later.
2. Open the terminal in the project that should receive the Skill. Back up any existing installation before continuing.
3. Copy the command for your agent below, or choose Command line, your agent, and a different Skill on the homepage. Run one command. If asked for a scope, choose Project for a project installation.
4. Wait for the CLI to report a successful installation. Open the same project in your agent and complete the verification below before starting a task.

node --version

npx skills@1.7.4 add 'https://skills.onebtcdesign.com/downloads/orbit-wallet-0.1.0.zip' --agent codex

npx skills@1.7.4 add 'https://skills.onebtcdesign.com/downloads/orbit-wallet-0.1.0.zip' --agent claude-code

npx skills@1.7.4 add 'https://skills.onebtcdesign.com/downloads/orbit-wallet-0.1.0.zip' --agent cursor

These commands install the versioned ZIP from this website, including project/, references/, and local resources. Codex and Cursor use .agents/skills/orbit-wallet/ in the project; Claude Code uses .claude/skills/orbit-wallet/. The CLI may create links to a shared copy, so a linked agent folder can be a valid installation.

Verify and start your first task

1. Ask the agent to locate the installed Skill in the current project and report its path and version. The version is available in the package’s manifest.json.
2. Confirm that SKILL.md, references/, and project/ are together and project/vendor/ is present. Ask it to read the Skill and its design and acceptance references.
3. Confirm the agent discovers the Skill. If it does not, check the folder structure and open a new session in the same project before installing another copy.
4. Give it one concrete change with your brand, target page, and requirements. Review the result and the checks it ran before expanding the task.

Find the installed orbit-wallet Skill in this project.
Report its path and version from manifest.json.
Confirm that references/, project/, and project/vendor/ are present.
Read SKILL.md, references/design.md, and references/acceptance.md.
Confirm discovery and summarize the design constraints before making changes.

Use the installed orbit-wallet Skill to adapt the wallet page to my brand.
Read its design and acceptance references first.
Reuse this project’s components and preserve precise amount calculations.
Use the brand assets and requirements I provide, then verify the changed page on desktop and mobile.

Package structure

orbit-wallet/
  SKILL.md
  agents/openai.yaml
  references/
    design.md
    acceptance.md
  project/
    README.md
    package.json
    pnpm-lock.yaml
    vendor/
    …

Each package has one root folder. The root is the installable Skill; project/ is the independent application. Shared modules are included in project/vendor/, so the application does not depend on this website’s repository.

Run the source

Use Node.js 22.12 or later and pnpm 10.30.3 for the bundled source. The skills CLI separately requires Node.js 22.20 or later. Enter the installed Skill’s project/ folder before running these commands; do not run them from the Skills parent directory. The development server prints its local address, and each product uses its own port.

pnpm install --frozen-lockfile
pnpm dev

pnpm build
pnpm typecheck
pnpm test

Update deliberately

Check the version before replacing an installation. Keep local modifications or back them up first, then ask your agent to compare the new instructions and source. Re-run the acceptance checks after updating.

If something does not work

• Skill not discovered: check that SKILL.md is directly inside the named Skill folder, not an extra nested extraction folder. Use the correct project, check the selected agent’s Skills directory, and start a new session before reinstalling.
• MCP search returns nothing: current search content is English. Try an English keyword such as wallet, vault, or trading, or ask the agent to list available Skills before narrowing the search.
• MCP will not connect: confirm the copied address and that your client can reach it. localhost points to the client’s own computer, so a cloud agent cannot use a server running only on your computer. For a local website, keep its development service running.
• Opening /api/mcp in a browser returns 405: this endpoint accepts MCP POST requests, not an ordinary page visit. Check the connection from an MCP client and try a tool call instead.
• CLI fails before installing: check Node.js 22.20+, registry access, and the copied ZIP address. Back up existing files before retrying; adding --yes does not fix a failed download and may skip replacement confirmation.
• The source will not run: enter the Skill’s project/ folder, keep vendor/ and the lockfile, and follow project/README.md. If its port is occupied, reuse or stop that project’s existing service before starting another.