About Laviya
Laviya Agent Skills is a repository of reusable orchestration assets and an MCP runtime for IDE and agent integrations. It combines shared prompts and client-specific rules or skills with task, sprint, wiki and test-case operations.
Key features
- 01Reusable prompts, rules and skills
- 02TypeScript MCP runtime
- 03Cursor and Claude artifacts
- 04Task and sprint operations
- 05Wiki and test-case management
- 06Runtime validation and retries
Use cases
- 01Turn a PRD into project work
- 02Run a guided delivery cycle
- 03Manage tasks from an IDE agent
- 04Record test cases and results
MCP support
Includes a stdio MCP runtime and a remote OAuth endpoint. Its tools expose Laviya project operations, including tasks, sprints, wikis, test cases and execution workflows.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://api.laviya.app/api/mcpclaude mcp add --transport http kartegagithub-laviya https://api.laviya.app/api/mcp{"mcpServers":{"kartegagithub-laviya":{"type":"http","url":"https://api.laviya.app/api/mcp"}}}Open in Cursor{"servers":{"kartegagithub-laviya":{"type":"http","url":"https://api.laviya.app/api/mcp"}}}Open in VS Code{"mcpServers":{"kartegagithub-laviya":{"type":"http","url":"https://api.laviya.app/api/mcp"}}}{"mcpServers":{"kartegagithub-laviya":{"serverUrl":"https://api.laviya.app/api/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
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/- Remote MCP endpoint
https://api.laviya.app/api/mcp(OAuth), registered frommcp-remote/server.json
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,laviya-prd-intake/SKILL.mdfor turning a PRD into Laviya work)docs/: setup, npm publishing, and end-user onboarding guides (docs/examples/: an example PRD)
Repository Structure
laviya-agent-skills/
core/
mcp/
src/
examples/
README.md
mcp-remote/
server.json
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 |
laviya-prd-intake (turn a PRD into epics, stories, tasks, sprints and test cases; example PRD: docs/examples/prd-order-export.md) | claude/laviya-prd-intake/SKILL.md | ~/.claude/skills/laviya-prd-intake/SKILL.md | <project>/.claude/skills/laviya-prd-intake/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", "$HOME\.claude\skills\laviya-prd-intake" | 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"
Copy-Item claude\laviya-prd-intake\SKILL.md "$HOME\.claude\skills\laviya-prd-intake\SKILL.md"
macOS / Linux (from the repository root):
mkdir -p ~/.claude/skills/laviya-orchestrator ~/.claude/skills/laviya-delivery-cycle ~/.claude/skills/laviya-prd-intake
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
cp claude/laviya-prd-intake/SKILL.md ~/.claude/skills/laviya-prd-intake/SKILL.md
Check: start a new Claude Code session and run /skills; laviya-orchestrator, laviya-delivery-cycle and laviya-prd-intake 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 + MCP Registry publishing guide (stdio and remote entries, GitHub Copilot listing):
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_list_taskslaviya_create_taskslaviya_start_delivery_runlaviya_get_tasklaviya_upload_task_filelaviya_update_task_descriptionlaviya_assign_tasklaviya_list_sprintslaviya_create_sprintlaviya_assign_tasks_to_sprintlaviya_list_task_linkslaviya_add_task_linklaviya_remove_task_linklaviya_list_test_caseslaviya_create_test_caseslaviya_report_test_resultlaviya_list_wikislaviya_get_wikilaviya_create_wikilaviya_update_wikilaviya_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.