Agent skills

Download and use the three Templiqx repository skills so Codex and Claude Code operate, author, and test packages smartly over MCP or the CLI.

Templiqx ships three repository-local skills — self-contained instruction bundles that teach an agent to drive Templiqx through its MCP tools or CLI, using the same canonical service a human would. They exist so an agent makes smart, grounded use of the capability catalog instead of guessing command syntax or inventing a second code path.

MCP first, CLI fallback

Every skill follows one rule: prefer the templiqx MCP server when its tools are connected; otherwise run the CLI (cargo run -q -p templiqx-cli -- …). MCP tool names match CLI commands and the application method one-to-one (validate_contract, compile_contract, run_eval, …), so the same operation is traceable across all three surfaces. See the capability map for the full 1:1 table and agent-native guide for connecting an agent over MCP.

Where the skills live

Canonical copies live under .agents/skills/, which Codex scans from the working directory up to the repository root. Each skill’s optional agents/openai.yaml supplies Codex app-UI metadata (see the official Codex skills docs). .claude/skills/ holds relative symlinks to the same files, so Claude Code and Codex read identical instructions with no drifting copies.

Each skill is a directory:

.agents/skills/<name>/
  SKILL.md              # the instructions the agent loads
  references/*.md       # concrete syntax, checklists, reporting formats
  agents/openai.yaml    # Codex app metadata

Download the skills

The skills are plain files in the repo. To use them outside a full clone, sparse-checkout just the skills directory:

git clone --no-checkout --depth 1 https://github.com/RyanLisse/templiqx.git
cd templiqx
git sparse-checkout set .agents/skills
git checkout
# skills are now in .agents/skills/ — copy them into your agent's skills path

Or fetch a single skill’s instructions directly:

curl -sSL https://raw.githubusercontent.com/RyanLisse/templiqx/main/.agents/skills/use-templiqx/SKILL.md

Invoke a skill

Reference the skill by name; the agent loads its SKILL.md and follows it.

Codex:        $use-templiqx discover packages and inspect the greeting contract
Claude Code:  /author-templiqx-contracts create a typed contract for this interaction
Claude Code:  /test-templiqx-packages validate the demo package and run all eval fixtures

Because both surfaces resolve to the same TempliqxService, you get identical envelopes, diagnostics, and fingerprints whether the skill used MCP or the CLI.