wind-find-finance-skill

Discovery Process

1. Trigger Scope: Users inquire about AIMarket/Wind financial capabilities, or raise questions related to financial data, analysis, or tools without specifying a particular skill, or the specified financial skill's

   SKILL.md

   is not found locally. If the user's intent is clear and the corresponding skill is already installed, use the corresponding skill directly without going through this entry.
2. First attempt to run the update detection script, execute

   node <path>

   if any path is found:

   • scripts/check-updates.mjs

     in the current skill directory

   • %USERPROFILE%\.agents\skills\wind-find-finance-skill\scripts\check-updates.mjs

   • ~/.agents/skills/wind-find-finance-skill/scripts/check-updates.mjs

   If stderr contains the

   [wind-skills]

   update prompt, fully inform the user when triggered for the first time in the same session; if version-related errors occur, suggest running

   npx skills update -g -y

   .
3. Read

   references/skills-catalog.md

   , categorize the user's question into data retrieval/query, analysis/decision-making, exploration/capability consultation, and recommend 1-5 relevant skills according to the catalog.
4. Detect whether the recommended skills are installed, in the following order:

   • .agents/skills/<name>/SKILL.md

     in the current agent

   • %USERPROFILE%\.agents\skills\<name>\SKILL.md

   • ~/.agents/skills/<name>/SKILL.md

   If the path does not exist, reading fails, or the skill is only mentioned in IDE tabs/historical context, it is considered not installed; do not perform large-scale recursive searches.
5. If installed, hand over to the corresponding skill for further processing. When necessary skills are missing, seek user confirmation before installation, and clearly ask about the installation scope: install to the current agent or all agents.
   Use commands without

   -g

   for the current agent, and commands with

   -g

   for all agents. After user confirmation, the AI directly executes the installation instead of only providing the command for the user to copy. Before installation, test the connectivity and response speed of GitHub and Gitee, and select the currently available, more stable/faster source. Gitee is not a backup source, nor is GitHub a fixed preferred source; the decision is based on test results. If installation fails with the preferred source, switch to another detected available source and retry.
   GitHub source commands:
   bash

   npx skills add Wind-Information-Co-Ltd/wind-skills --skill <name> -y
   npx skills add Wind-Information-Co-Ltd/wind-skills --skill <name> -g -y

   Gitee source commands:
   bash

   npx skills add https://gitee.com/wind_info/wind-skills.git --skill <name> -y
   npx skills add https://gitee.com/wind_info/wind-skills.git --skill <name> -g -y

   After installation, check whether the corresponding

   SKILL.md

   exists; continue execution after confirming it is saved to disk. Do not require users to restart or refresh the session by default; only prompt when actual calls fail and it is clearly due to the client not loading the new skill. If the catalog indicates "configuration required after installation" for API Key/Token/dependencies, guide the user to complete the corresponding configuration after installation.

Routing Rules

wind-mcp-skill

wind-mcp-skill

references/skills-catalog.md

wind-mcp-skill

Boundaries

~/.cache/wind-aimarket/wind-find-update-state.json

references/skills-catalog.md

npx skills update -g -y