Skip to main content
Add this documentation as a skill to your AI coding assistant so your agent can reference the Finance.dev docs while helping you build integrations, write code, and troubleshoot issues.

​
Before you begin

Make sure you have all of the following before starting:
  • The Finance.dev welcome page open at https://finance.dev/welcome
  • Node.js 18 or later installed
  • A terminal session open in the project where you want to use the skill
  • An AI coding assistant that supports the skills protocol
Use this command: 
npx skills add https://finance.dev/docs

​
Step 1: Run the install command

Open https://finance.dev/welcome. In the Add Skill to your AI agents section, copy this command: 
npx skills add https://finance.dev/docs
Open Windows CMD, Windows Terminal, or another interactive terminal. Move to the project where you want to use the skill: 
cd path\\to\\your-project
Run the install command: 
npx skills add https://finance.dev/docs
After you press Enter, the CLI starts loading the Finance.dev skill package. You should see output similar to this: 
Source: https://finance.dev/docs
Discovering skills from well-known endpoint...
Found 1 skill
Skill: engine
What this means:
  • Source: https://finance.dev/docs confirms the CLI is using the Finance.dev documentation URL
  • Discovering skills from well-known endpoint... means the CLI is fetching the skill definition
  • Found 1 skill means the source returned one installable skill
  • Skill: engine is the current install name exposed by the Finance.dev endpoint

​
Step 2: Review the agent selection screen

After the skill is discovered, the CLI loads the supported agent list and opens the interactive selection screen. You should see a screen similar to this: 
Which agents do you want to install to?
Universal (.agents/skills) -- always included
Additional agents
Search:
up/down move, space select, enter confirm
Selected: ...
What each part means:
  • Universal (.agents/skills) lists shared agent targets that are included through the .agents/skills location
  • Additional agents lists agent-specific integrations such as Claude Code, OpenClaw, and other supported tools
  • Search: lets you filter the visible agent list
  • Selected: shows the agents currently selected in this run
How to use the screen:
  1. Press the up or down arrow key to move the highlight.
  2. Press Space to select the highlighted agent.
  3. Press Space again to remove that agent from the selection.
  4. Keep checking the Selected: line at the bottom.
  5. Press Enter only when the selected list is exactly what you want.
Important check: Before you confirm anything, read the Selected: line carefully. That line tells you the real selection state that will be used for the installation.

​
Step 3: Finish the installation

After you confirm the agent list, the CLI may show additional setup steps before installation completes.

​
Installation scope

The CLI may ask where you want the skill to be installed. You may see options similar to these: 
Installation scope
Project
Global
What these options mean:
  • Project installs the skill for the current project only
  • Global installs the skill for your user account so it can be available across multiple projects
If you are not sure which to choose, select Project unless you specifically want the skill available everywhere on your machine.

​
Installation method

After the scope step, the CLI may ask how the skill should be installed. You may see options similar to these: 
Installation method
Symlink (Recommended)
Copy to all agents
Choose the option that matches your situation:
  • Symlink (Recommended) keeps one shared copy of the skill and links the selected agents to it. This is easier to update later because there is only one main copy to maintain.
  • Copy to all agents creates a separate copy of the skill for each selected agent. Use this if symlinks are not supported in your environment or if you specifically want separate copies for each agent.
Simple rule:
  1. Choose Symlink if you want the easiest maintenance and updates.
  2. Choose Copy to all agents only if you know you need separate copies or if symlinks do not work in your setup.

​
Complete the setup

Continue through the remaining prompts until the CLI finishes the setup. When the installation completes successfully, restart the AI agents you selected so they reload the new skill. You can then test the installation by asking your AI assistant questions such as:
  • “What does the Finance.dev API offer?”
  • “How do I authenticate with the Finance.dev API?”
If the assistant answers using Finance.dev concepts such as OAuth2, endpoints, scopes, orders, or market data, the skill is loaded.

​
Step 4: Understand the cancelled install behavior

If you cancel the installation after selecting agents and then run the same command again, the CLI may restore the previous agent selections without showing a separate restore message.
This is the important behavior to watch for in the same CMD or Windows Terminal session:
  1. You run the install command.
  2. You reach the Which agents do you want to install to? screen.
  3. You change one or more agent selections.
  4. You cancel the installation before the full setup finishes.
  5. You run npx skills add https://finance.dev/docs again.
  6. The agent-selection screen opens again.
  7. The Selected: line may already contain the agents from the previous cancelled run.
If that happens and the CLI does not show a separate restore prompt, the behavior matches the issue description.

​
Expected result

After cancelling the installation before completion, the next run should do one of these:
  1. Start fresh with the default selections only.
  2. Show a clear restore message before reusing previous selections.
An example of a clear restore message would be: 
Previous selections detected. Do you want to continue with them or reset?

​
Actual result

After cancelling the installation and starting the command again, the CLI can restore the previous selections without clearly telling you that it is doing that. Why this happens: The interactive installer remembers the last selected agents and can reuse them as the starting state on the next interactive run. Because that state is stored outside the current prompt screen, starting a new terminal window does not guarantee a fresh selection list.

​
Step 5: What to do if selections are restored

If you rerun the command after cancelling, do this before pressing Enter on the agent-selection screen:
  1. Look at the Selected: line immediately.
  2. Do not assume the CLI reset the list to the defaults.
  3. Remove any agents you do not want.
  4. Add any agents that are missing.
  5. Confirm the selection only after the Selected: line matches your intended setup.
If you want to reduce the chance of mistakes, use one of these options:
  1. Pass explicit --agent values instead of relying on interactive selection.
  2. Review every preselected agent before continuing.
  3. Clear the stored selection state before rerunning the interactive flow.

​
Step 6: Verify the correct agents were updated

After installation finishes:
  1. Restart each AI agent that you selected during setup.
  2. Ask a Finance.dev-specific question in each one.
  3. Confirm that the expected agents answer with Finance.dev documentation context.
  4. If an unexpected agent has the skill, rerun the install flow and correct the selections before finishing.

​
Troubleshooting

IssueSolution
Command not foundEnsure Node.js 18 or later is installed. Run node -v to verify.
Skill not loadingRestart the AI agent completely after installation.
Outdated infoRun npx skills add https://finance.dev/docs again to refresh the skill.
Previous selections appear after a cancelled installReview the Selected: line carefully. The CLI may restore the previous interactive selection state.
You want to avoid restored selectionsUse explicit --agent values or clear the stored selection state before running the interactive install again.