Lyquor Skills

Public Lyquor skills for agents that help developers install, run, inspect, build, and deploy against the public Lyquor LDK workflow.

This repository is the single source of truth for Lyquor-maintained skills. Private Lyquor applications consume the published package; they do not keep a second copy of these skill files.

Package

The npm package name is:

lyquor-skills

Install it in an agent host or application that knows how to read Lyquor skill catalogs:

npm install lyquor-skills

Agent hosts should resolve lyquor-skills/package.json, then read skills from:

<package-root>/skills

Local development may point directly at this repository with an explicit override, but the default production path should use the package.

Included Skills

• ldk-devnet-setup
• ldk-devnet-start
• ldk-devnet-status
• ldk-devnet-stop
• ldk-devnet-uninstall
• ldk-evm-interact
• ldk-lyquid-create
• ldk-lyquid-implement
• ldk-lyquid-build
• ldk-lyquid-abi
• ldk-lyquid-deploy
• ldk-lyquid-status

Skill Structure

Each skill lives in:

skills/<skill-name>/
  SKILL.md
  lyquor.skill.json

Some skills may also include scoped helper files:

skills/<skill-name>/scripts/
skills/<skill-name>/references/
skills/<skill-name>/assets/

SKILL.md is the human-authored source. lyquor.skill.json is the runtime manifest used by agent hosts. When a skill changes, update SKILL.md first, then update the manifest to match the public runtime contract.

Public Scope

These skills cover public LDK workflows:

• install or remove the public LDK footprint
• start, stop, and inspect local managed devnet nodes
• query the EVM-compatible local devnet surface
• create Lyquid projects from public templates or examples
• implement one Lyquid boundary from clear requirements
• build, inspect, and deploy Lyquid projects
• query visible or hosted Lyquids from a running local devnet

They do not include internal Lyquor-only workflows, private deployment procedures, or product-specific console UI behavior.

Runtime State

This repository must not commit local runtime state, caches, build output, or developer scratch data. Examples that must stay out of git and npm packages:

• lyquor_data/
• lyquid_tools_target/
• .local-kb/
• evals/
• .DS_Store
• log files and local database files

If stable example data is needed, add a small, reviewed fixture under an explicit fixtures/ directory instead of committing runtime output.

Package Preview

Preview the package contents before publishing:

npm run pack:dry-run

The preview should include only public docs, package metadata, and files under skills/.

Publishing

Publish the public package with:

npm run publish:public

Private consumers should update their dependency version after the package is published. They should not copy files from this repository.