This document explains how the repo-local Quantex CLI skill is installed, validated, updated, and shared today.
The Quantex CLI skill is a repo-native skill for Codex and similar agents that should operate Quantex through its lifecycle CLI surface instead of calling downstream agent binaries ad hoc.
This document is about the user-facing skills/quantex-cli/ skill. The separate skills/quantex-agent-runtime/ directory is contributor-facing repository workflow runtime for agents developing this repo; it is not part of the normal external user installation path.
This document covers:
- where the skill lives in this repository
- how to point an agent runtime at it
- how to validate changes safely
- what "distribution" means today
This document does not define a marketplace or packaged publishing flow because that does not exist yet.
The canonical user-facing skill files live under skills/quantex-cli/:
SKILL.md: the main operating instructions for agentsagents/openai.yaml: agent-specific metadatareferences/: supporting command, automation, output, and troubleshooting referencesassets/: icons and visual assetsscripts/smoke-check.sh: lightweight validation for the Quantex command surface
When the Quantex CLI behavior changes, update the relevant canonical project-memory artifact first:
- behavior contract:
openspec/ - durable decision:
docs/adr/ - troubleshooting or recovery knowledge:
docs/runbooks/
Then update the skill files so they reflect the same contract.
If a skill reference keeps a maintained supported-agent snapshot, verify it against bun run dev -- list --json and the current src/agents/catalog/*.json set in the same branch.
The contributor-facing runtime lives separately under skills/quantex-agent-runtime/. Use it when working inside this repository with Superpowers, OpenSpec intake, validation, and delivery closure rules. Do not document it as the default skill for users who only want to operate Quantex.
Today the Quantex CLI skill is installed from the repository itself. There is no separate npm package, marketplace release, or standalone bundle.
Use one of these patterns:
-
Install from GitHub with the
skillsCLI:npx skills add Drswith/quantex-cli --skill quantex-cli
-
Work directly from this repository when the agent runtime can read repo-local skills.
-
Copy or sync
skills/quantex-cli/into the target skill directory if the runtime expects installed skills outside the repository.
The important requirement is that the runtime sees the whole skills/quantex-cli/ directory, not only SKILL.md, because the references, metadata, assets, and smoke-check script are part of the maintained artifact.
To inspect the available skills before installing, run:
npx skills add Drswith/quantex-cli --listWhen maintaining the CLI surface or the skill itself, run:
skills/quantex-cli/scripts/smoke-check.shThe script resolves quantex in this order:
QUANTEX_BINif explicitly providedbun run src/cli.tsfrom this repository whenbunis available- a globally available
quantexbinary inPATH
Useful examples:
# Use the repo checkout with Bun
skills/quantex-cli/scripts/smoke-check.sh
# Validate against a specific built binary
QUANTEX_BIN=./dist/bin/quantex skills/quantex-cli/scripts/smoke-check.sh
# Change the smoke agent when needed
QUANTEX_SMOKE_AGENT=claude skills/quantex-cli/scripts/smoke-check.shThe smoke check currently verifies:
capabilities --jsoncommands --jsonschema --jsonschema inspect --jsoninspect <agent> --jsonresolve <agent> --jsonwhen that agent is already installed
Run this after updating:
- command names or flags
- JSON envelope or schema behavior
- lifecycle command expectations in the skill
- skill references that describe structured usage
- skill references that enumerate supported agent names
Use this update order:
- Change the Quantex CLI behavior or project-memory artifact first.
- Update
skills/quantex-cli/so the skill matches the current contract. - Run
skills/quantex-cli/scripts/smoke-check.sh. - If the change affects durable docs, update the linked runbook, ADR, or OpenSpec artifact in the same branch.
Treat skills/quantex-cli/ as a consumer-facing integration layer, not the source of truth for product behavior. Treat skills/quantex-agent-runtime/ as repository workflow runtime for contributors.
Supported today:
- sharing the repository itself
- pinning to a repository revision or branch
- installing from GitHub through
npx skills add Drswith/quantex-cli --skill quantex-cli - copying the repo-local skill directory into another compatible skill location
Not supported today:
- a dedicated skill package
- a public skill marketplace flow
- an automated release pipeline that publishes the skill independently from this repository
So in practice, the user-facing Quantex CLI skill is currently distributed as part of the repository, alongside the CLI and its project-memory artifacts.
skills/quantex-cli/SKILL.mdskills/quantex-agent-runtime/SKILL.mdskills/quantex-cli/scripts/smoke-check.shskills/quantex-cli/references/command-recipes.mdskills/quantex-cli/references/output-contracts.mddocs/runbooks/quantex-troubleshooting.md