Laviya Agent Skills

Name: Laviya Agent Skills
Author: kartegagithub

by kartegagithubversion 0.1.32i★ 0iRuns on your computer

Registry nameio.github.kartegagithub/laviya-agent-skills

Install

Overview

Description from the maker (original English)

Laviya AI Orchestration MCP runtime for IDE and agent integrations.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi2 of 2 passedChecked from public information; code not scanned yet
UsageiEarly↓ 352/wk · ★ 0

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Developer tools
You need to fill in: LAVIYA_API_KEY

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 2 of 2 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: LAVIYA_API_KEY, LAVIYA_BASE_URL, LAVIYA_AGENT_UID, LAVIYA_LOG_LEVEL, LAVIYA_GLOBAL_CONFIG_PATH

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "laviya-agent-skills": {
      "command": "npx",
      "args": [
        "-y",
        "laviya-mcp-server"
      ],
      "env": {
        "LAVIYA_API_KEY": "your-value",
        "LAVIYA_BASE_URL": "your-value",
        "LAVIYA_AGENT_UID": "your-value",
        "LAVIYA_LOG_LEVEL": "your-value",
        "LAVIYA_GLOBAL_CONFIG_PATH": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add laviya-agent-skills --env LAVIYA_API_KEY=your-value --env LAVIYA_BASE_URL=your-value --env LAVIYA_AGENT_UID=your-value --env LAVIYA_LOG_LEVEL=your-value --env LAVIYA_GLOBAL_CONFIG_PATH=your-value -- npx -y laviya-mcp-server

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "laviya-agent-skills": {
      "command": "npx",
      "args": [
        "-y",
        "laviya-mcp-server"
      ],
      "env": {
        "LAVIYA_API_KEY": "your-value",
        "LAVIYA_BASE_URL": "your-value",
        "LAVIYA_AGENT_UID": "your-value",
        "LAVIYA_LOG_LEVEL": "your-value",
        "LAVIYA_GLOBAL_CONFIG_PATH": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "laviya-agent-skills": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "laviya-mcp-server"
      ],
      "env": {
        "LAVIYA_API_KEY": "your-value",
        "LAVIYA_BASE_URL": "your-value",
        "LAVIYA_AGENT_UID": "your-value",
        "LAVIYA_LOG_LEVEL": "your-value",
        "LAVIYA_GLOBAL_CONFIG_PATH": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

LAVIYA_API_KEY secret required env
Laviya API key used for MCP runtime authentication.
LAVIYA_BASE_URL env
Optional base URL override for the Laviya API endpoint.
LAVIYA_AGENT_UID env
Optional agent UID override for execution orchestration.
LAVIYA_LOG_LEVEL env
Optional log level override (debug|info|warn|error).
LAVIYA_GLOBAL_CONFIG_PATH env
Optional path override for global runtime config (useful in sandboxed environments where home directory is not readable).

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 10, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account kartegagithub, which owns the repo
✓ Pass
Still maintained
Code last changed today
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Developer toolsi

More stars than 0% of the other 5719 servers in this category
Published to the registry more recently than 79% of the other 5719 servers in this category
Basic checks equal to or better than 100% of the other 5719 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Laviya Agent Skills safe?

It passed 2 of 2 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: LAVIYA_API_KEY

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed today, and the latest version (0.1.32) reached the registry 4 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: REA, Netdata, Front-End Checklist

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

REA

Reverse engineer anything from your terminal or agent with one CLI and MCP server.

by morlutoWidely used↓ 481.8K/wk★ 448.2KUpdated 16 days ago

Runs on your computer

Install

Netdata

Real-time infrastructure monitoring with metrics, logs, alerts, and ML-based anomaly detection.

by netdataWidely used★ 81.3KUpdated 6 days ago

Runs in the cloud

Install

Front-End Checklist

Review frontend code and live pages against 386 quality-gated web development rules.

by thedaviddiasWidely used★ 74.7KUpdated 36 days ago

Runs in the cloud

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Laviya 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 tooling
laviya-mcp-server: stdio MCP runtime published from mcp/

What Is Included

core/: shared orchestration prompt assets
mcp/: TypeScript MCP runtime scaffold (laviya-mcp-server)
cursor/: Cursor rule artifacts
claude/: Claude skill artifacts (SKILL.md for orchestration, laviya-delivery-cycle/SKILL.md for the user-driven delivery cycle, laviya-prd-intake/SKILL.md for 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 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`	`/.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`	`/.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`	`/.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 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.json or .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_help
laviya_feed_task
laviya_get_local_work_status
laviya_cancel_local_work
laviya_add_task_comment
laviya_list_projects
laviya_list_tasks
laviya_create_tasks
laviya_start_delivery_run
laviya_get_task
laviya_upload_task_file
laviya_update_task_description
laviya_assign_task
laviya_list_sprints
laviya_create_sprint
laviya_assign_tasks_to_sprint
laviya_list_task_links
laviya_add_task_link
laviya_remove_task_link
laviya_list_test_cases
laviya_create_test_cases
laviya_report_test_result
laviya_list_wikis
laviya_get_wiki
laviya_create_wiki
laviya_update_wiki
laviya_start_task_work
laviya_complete_task_work
laviya_get_my_work
laviya_start_execution
laviya_complete_execution
laviya_report_token_usage
laviya_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.

Laviya Agent Skills

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Developer toolsi

Common questions

Alternatives

REA

Netdata

Front-End Checklist

README from the maker

Laviya Agent Skills

Packages

What Is Included

Repository Structure

Quick Start

Install the Claude Code skills

Installable Asset Package

Documentation Index

Runtime Overview