About laviya-agent-skills
Laviya Agent Skills is a repository of reusable orchestration prompts, rules, skills, and a TypeScript MCP runtime for IDE and agent integrations. It includes client-specific assets for Cursor and Claude, plus runtime tools for task and delivery workflows.
Key features
- 01Reusable orchestration prompts and rules
- 02Cursor rules and Claude skills
- 03TypeScript stdio MCP runtime
- 04Project-local configuration
- 05Task and delivery workflow tools
Use cases
- 01Add orchestration guidance to Claude Code
- 02Use shared rules in Cursor
- 03Run task and delivery workflows through MCP
MCP support
Includes laviya-mcp-server, a stdio MCP runtime that exposes orchestration and task-management tools. The runtime uses a global installation with project-level configuration.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
npx -y laviya-mcp-serverLAVIYA_API_KEYSecretLaviya API key used for MCP runtime authentication.LAVIYA_BASE_URLOptional base URL override for the Laviya API endpoint.LAVIYA_AGENT_UIDOptional agent UID override for execution orchestration.LAVIYA_LOG_LEVELOptional log level override (debug|info|warn|error).LAVIYA_GLOBAL_CONFIG_PATHOptional path override for global runtime config (useful in sandboxed environments where home directory is not readable).Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
10Saved tool list · updated 4d ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| payload | object | Yes | |
| payload.taskID | integer | Yes |
Details
From the project READMELaviya Agent Skills
Laviya Agent Skills is a repository of reusable orchestration assets for IDE and agent integrations. It provides a production-oriented MCP runtime, shared orchestration prompt assets, and client-specific artifacts for tools such as Cursor and Claude.
Packages
laviya-agent-skills: reusable prompt, rule, and skill asset bundle for Node-based toolinglaviya-mcp-server: stdio MCP runtime published frommcp/
What Is Included
core/: shared orchestration prompt assetsmcp/: TypeScript MCP runtime scaffold (laviya-mcp-server)cursor/: Cursor rule artifactsclaude/: Claude skill artifacts (SKILL.mdfor orchestration,laviya-delivery-cycle/SKILL.mdfor the user-driven delivery cycle)docs/: setup, npm publishing, and end-user onboarding guides
Repository Structure
laviya-agent-skills/
core/
mcp/
src/
examples/
README.md
cursor/
claude/
docs/
Setup.md
MCPServerPublish.md
InstallationAndUsage.md
Quick Start
cd mcp
npm install
npm run typecheck
npm run build
npm run dev
Required environment variable:
LAVIYA_API_KEY
Install the Claude Code skills
Claude Code loads a skill only from a skills folder, one folder per skill named after the skill, with the file named SKILL.md:
| Skill | Source file in this repository | Install to (personal, all projects) | Or (one project only) |
|---|---|---|---|
laviya-orchestrator (orchestration runs) | mcp/examples/claude/SKILL.md | ~/.claude/skills/laviya-orchestrator/SKILL.md | <project>/.claude/skills/laviya-orchestrator/SKILL.md |
laviya-delivery-cycle (verify a work list, create tasks, report Ready for deploy) | claude/laviya-delivery-cycle/SKILL.md | ~/.claude/skills/laviya-delivery-cycle/SKILL.md | <project>/.claude/skills/laviya-delivery-cycle/SKILL.md |
The paths in the second column are where the files live in this repository, not where Claude Code looks for them. A file in ~/.claude/laviya-delivery-cycle/ (without skills) or directly in ~/.claude/ is ignored.
Windows (PowerShell, from the repository root):
New-Item -ItemType Directory -Force "$HOME\.claude\skills\laviya-orchestrator", "$HOME\.claude\skills\laviya-delivery-cycle" | Out-Null
Copy-Item mcp\examples\claude\SKILL.md "$HOME\.claude\skills\laviya-orchestrator\SKILL.md"
Copy-Item claude\laviya-delivery-cycle\SKILL.md "$HOME\.claude\skills\laviya-delivery-cycle\SKILL.md"
macOS / Linux (from the repository root):
mkdir -p ~/.claude/skills/laviya-orchestrator ~/.claude/skills/laviya-delivery-cycle
cp mcp/examples/claude/SKILL.md ~/.claude/skills/laviya-orchestrator/SKILL.md
cp claude/laviya-delivery-cycle/SKILL.md ~/.claude/skills/laviya-delivery-cycle/SKILL.md
Check: start a new Claude Code session and run /skills; laviya-orchestrator and laviya-delivery-cycle must be listed. Copy the files again after updating this repository. The Laviya MCP tools also work without the skills; the skills add the step-by-step rules.
Installable Asset Package
Install the reusable asset bundle:
npm install laviya-agent-skills
Example usage:
import { assets, resolveAssetPath } from "laviya-agent-skills";
import { readFileSync } from "node:fs";
const cursorRule = readFileSync(assets.cursorRule, "utf8");
const orchestratorPrompt = readFileSync(resolveAssetPath("orchestratorSystemPrompt"), "utf8");
Documentation Index
- Runtime architecture and implementation:
mcp/README.md - Developer setup guide:
docs/Setup.md - NPM publishing guide:
docs/MCPServerPublish.md - End-user installation and usage:
docs/InstallationAndUsage.md - Client-specific MCP setup (Codex, VS Code, Antigravity, Claude):
docs/InstallationAndUsage.md
Runtime Overview
The MCP runtime follows a global-runtime plus project-local-config model:
- machine-level runtime installation
- repository-level project configuration (
.laviya/project.jsonor.laviya.json) - runtime-enforced lifecycle mechanics (validation, retries, idempotency, and structured logging)
Current MCP tool set includes both orchestration and local-direct task feed flows:
laviya_helplaviya_feed_tasklaviya_get_local_work_statuslaviya_cancel_local_worklaviya_add_task_commentlaviya_list_projectslaviya_create_taskslaviya_start_delivery_runlaviya_get_tasklaviya_upload_task_filelaviya_update_task_descriptionlaviya_assign_tasklaviya_start_task_worklaviya_complete_task_worklaviya_get_my_worklaviya_start_executionlaviya_complete_executionlaviya_report_token_usagelaviya_diagnostics
All tools return API envelope JSON text in the shape: { HasFailed, Messages, Data }.
Work items may include a backend-defined ExecutionPolicy. Analysis and review
policies are read-only: agents must not implement changes, and enforced policies
require a truthful completion executionEvidence.
For full architecture details and file-level scaffolding, refer to mcp/README.md.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.