Taruvi Agents Plugin

Source of truth for Taruvi agent support across Claude, Codex, Cursor, and Kiro.

The repository root is also a portable Agent Plugins v1 package:

plugin.json is the standards-compliant root manifest.
skills/ is the fixed Agent Plugins skill discovery location, generated from src/skills/.
mcp.json is intentionally empty for now because Agent Plugins v1 does not define portable secret or tenant configuration for Taruvi's remote MCP endpoint. Vendor-specific MCP templates remain under payload/.

Install into a Taruvi template

From a cloned Taruvi hacks template:

npx @taruvi/agents-plugin install

The installer writes safe agent support files into the current project:

.agents/skills/
.agents/hooks/
.claude/
.codex/
.cursor/
.kiro/

It does not ask for credentials, does not create .env, and does not write local MCP secrets. After install, open your preferred agent and say:

setup taruvi

That later setup flow writes app and MCP configuration from the Taruvi Connect block that the user pastes.

Develop

Shared product skills live once under src/skills/. Shared hook scripts live under src/hooks/ and are installed into .agents/hooks/, with vendor folders symlinking to them when needed. Common setup behavior lives in src/shared/setup-core.md. Vendor setup skills are generated from that shared core plus vendor-specific guidance.

Build the installer payload:

npm run build:vendor-files

Run a local install test:

node bin/taruvi-agents-plugin.js install --target /tmp/taruvi-agents-plugin-test --force --allow-non-template