> For the complete documentation index, see [llms.txt](https://docs.talus.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.talus.network/talus-docs-v2.1.0/guides/getting-started/coding-skills.md). # Use Nexus Coding Skills {% hint style="info" %} **Audience:** Developers using an AI coding assistant to build or diagnose Nexus applications. **Goal:** Install Nexus coding skills, choose the skill for your task, and use its guidance in your project. {% endhint %} The [Nexus skills collection](https://github.com/Talus-Network/skills) gives a coding assistant task-specific instructions and reference material for Nexus development. Skills cover Tool implementation, Talus Agent Package (TAP) development, API applications, execution diagnosis, and payment tracking. They are optional development aids; each Nexus guide remains usable on its own. Installing a coding skill adds guidance to your assistant. Publishing a Tool or [registering a Nexus protocol Skill](/talus-docs-v2.1.0/guides/agent-usage/register-skill-package.md) is a separate on-chain workflow. ### Install the skills Install [Node.js with npm](https://nodejs.org/en/download) so that `npx` is available, and have Git and a supported coding assistant installed. From your project directory, run: ```bash npx skills add Talus-Network/skills ``` Choose the skills and coding assistant in the installer. The default installation scope is your project; confirm the selected skills, assistant, and destination in the completion output. The [Skills CLI documentation](https://github.com/vercel-labs/skills#readme) describes supported assistants and installation options. To preview the available skills without installing them: ```bash npx skills add Talus-Network/skills --list ``` To install only the execution-diagnosis skill: ```bash npx skills add Talus-Network/skills --skill nexus-onchain-task-debugging ``` ### Choose a skill | Skill | Use it for | | --------------------------------- | --------------------------------------------------------------------------------------------------------------------- | | `nexus-onchain-tool-development` | Build and validate a Sui Move Tool, including its authorization, output, and tests. | | `nexus-offchain-tool-development` | Build a Rust HTTP Tool, integrate an external provider, and verify metadata and signed HTTP behavior. | | `nexus-tap-development` | Build a TAP and its artifacts, or an API dashboard, dApp, or backend for an existing TAP. | | `nexus-onchain-task-debugging` | Investigate pending, failed, or inconsistent Executions using Task, input, Tool, authorization, and payment evidence. | | `nexus-cli-payment-tracking` | Reconcile funding, reserves, execution charges, refunds, and Tool revenue. | Use payment tracking for an accounting question and execution diagnosis when the cause may involve inputs, Tools, authorization, or workflow state. For an application over an existing TAP, use the TAP skill and describe the API application you need. ### Use a skill in your project Open the project in your coding assistant and ask it to use the installed skill by name. Include the desired outcome, relevant files, network and object IDs when applicable, and the actions you want it to take. For example, replace `` with the execution you want to inspect: ``` Use nexus-onchain-task-debugging to investigate why Execution is pending on Sui Testnet. Keep the investigation read-only, distinguish confirmed causes from missing evidence, and explain the next check. ``` For development work, describe the behavior to implement and the checks that should demonstrate it works. The skill supplies the Nexus workflow; your request supplies the project-specific requirements. ### Confirm the installation and next step List installed skills from the project directory: ```bash npx skills list ``` Confirm that the intended skill is listed for your assistant. If `npx` is unavailable, install Node.js with npm. If the assistant does not offer the skill, check the selected assistant and installation scope, then reopen the project or session according to that assistant's instructions. The skills installer does not install the Nexus CLI, SDK, or Sui toolchain. Follow [Developer Setup](/talus-docs-v2.1.0/guides/getting-started/setup.md) when your task needs those tools, or the [Nexus API guide](/talus-docs-v2.1.0/guides/nexus-api.md) for an application over an existing TAP. Review the assistant's changes and its reported build, test, or read-only evidence before continuing to the task's next step. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.talus.network/talus-docs-v2.1.0/guides/getting-started/coding-skills.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.