Agent skills and tools

Skills teach an agent how and when to perform a task. Tools provide actions it can execute. A skill can explain a tool, but cannot grant permission to use it.

Create a skills project

glxdev new --kind skills --package-id com.example.review-guide --name "Review Guide" --publisher example --output ./review-guide
glxdev check --project ./review-guide

Open the generated project and edit its instruction files. Explain the trigger, required inputs, steps, and expected result. Use a small, repeatable example that demonstrates success and a case in which the agent should stop or ask for missing information.

Test the instructions

Use a disposable workspace with known input files. Confirm the agent follows the intended workflow, handles missing inputs, and reports what it actually checked. Keep credentials and personal data out of examples.

Packaging status

The npm CLI 0.2.0 scaffolds and checks a skills project, but packaging that scaffold currently fails with component_not_built. The Rust provider tutorial is the supported end-to-end packaging example.

Tools and MCP

Executable tools need a host-supported implementation and permission checks. An instruction file alone does not register executable code or start a server. Configure supported MCP integrations through Glixo Code's integration settings; do not assume a catalog description installs or starts a process.