Skills for other agents

Before you start

Install Renku first and confirm renku about works in a terminal. Your agent must support local command execution and Agent Skills. The available tools and media review experience depend on the agent.

The commands below use the independent skills tool. Install Node.js and Git according to that tool’s requirements; Renku does not bundle it. Running npx skills may download the tool and ask for confirmation.

Find your agent’s identifier in the supported agents list. The examples use cursor; replace that value with your agent’s identifier. Avoid selecting all agents.

Install for one project

Open a terminal in the folder your agent will work in, then run:

npx skills add GoRenku/studio-skills --agent cursor --skill '*' --copy

Choose project scope if prompted, review the destination, and confirm. Copy mode installs regular files rather than symbolic links. Keep your agent working in that folder so it can discover the skills.

Install across projects

Use global scope only if the tool lists global installation support for your agent. For example, Cursor supports:

npx skills add GoRenku/studio-skills --agent cursor --skill '*' --copy --global

Project-only agents, including PromptScript, must use project scope. Do not add --global for them.

Verify and update

Start a new agent conversation and check that the Renku skills are available. Begin with movie-director, using your agent’s skill interface.

To refresh the skills, rerun the same installation command with the same agent and scope. renku update skills refreshes the Claude/Codex plugins; it does not manage other agents’ skills.

Existing skill files are retained when you update Renku. If you previously installed both loose skills and a plugin for the same agent, review duplicates using that agent’s own controls.