nexus-tool-schemas

Export the live CLI-first Nexus tool catalog as JSON — the whole registry or a selector-picked subset — and refresh the committed catalog that the repo's guidance and drift tests read. Use when someone asks for tool schemas or the exact command/argument shape a caller sees, after changing a tool's parameter schema, slug or description, after touching ToolCliNormalizer, or when a catalog-backed test fails.

Ir para a instalação

Repositório: ProfSynapse/nexus
Última atividade na origem: 19 de agosto de 2026 às 16:33
Idioma detectado do SKILL.md: inglês
Estrelas: 154
Forks: 19

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.

npx skills add https://github.com/ProfSynapse/nexus --skill nexus-tool-schemas

O comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.

Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

Explorador de arquivos

10 arquivos

SKILL.md

Instruções da origem · Visualização somente leitura

Voltar à pesquisa Voltar à instalação

nexus-release

Cut a Nexus release — bump the version with the repo's own machinery, get the docs and generated sources right, push a tag the GitHub Actions workflow will actually pick up, and recover when it does not. Use when asked to release, publish, ship, cut a release, bump the version, or tag a version, and when a release workflow did not fire, failed its version guard, or produced the wrong assets.

2026-09-02

nexus-model-updates

Add, change or verify a Nexus LLM model definition — the registry entry, the provider default, and proof the model id actually works against the live endpoint. Use when adding a newly released model, editing model metadata such as pricing, context window or capability flags, promoting a provider default, standing up a model registry for a new provider, or checking whether a model id resolves through the live provider smoke lane.

2026-09-02

nexus-testing

Verify a Nexus change — pick a Jest lane, write a test that can actually fail, run the in-app Obsidian CLI loop, drive the eval harness, or fix a shipped-docs drift failure. Use when adding or changing tests, when a mock might be deciding the outcome, when a change has to be proven in the running plugin, or when the guidance gate fails.

2026-08-27

Ver todas deste repositório

Nexus Tool Schemas

Context: the exporter boots the agent registry headlessly and asks the live ToolCliNormalizer for each tool's CLI schema, so the JSON is the caller's-eye view of the tools rather than a parse of the TypeScript. It runs with no Obsidian, no vault and no build — but it does need npm install, and it writes to two different files for two different jobs.

Workflow

Decide which job this is. The answer is the output path, and choosing it by default is the standard failure here — the default path is a scratch file nothing reads.

Reading, answering a question, inspecting a subset → protocols/export-subset.md
Refreshing the catalog the repo ships and tests against → protocols/refresh-catalog.md

Run that protocol end to end. You MUST NOT hand-write or hand-patch either JSON file: both are generated, and an edited catalog makes the drift test the only thing standing between a wrong doc and a caller.

Validate what you produced with scripts/check_catalog.py before reporting it, and treat a non-zero exit as a stop.

At the end of a session that used this skill, run protocols/self-refine.md.

Map

protocols/ the two export jobs, plus self-refine.

references/ consumers.md (which file each reader expects, and what breaks when it is stale) and exporter-internals.md (how the headless boot works, what it needs, and its failure modes).

scripts/check_catalog.py validates an exported catalog; scripts/check_exporter_coverage.py catches an agent the exporter cannot see. Run them, do not reimplement.

refinement-log.md what past sessions changed here and why.

Siblings

Adding or renaming an agent or tool, or a command that does not resolve: nexus-agents. It owns the slug-to-CLI-name transform (cli_name.py) and the checker for commands written in docs (check_documented_commands.py).

Jest lanes, the shipped-docs gate and how to make a failing test fail for the right reason: nexus-testing.

Shipping the refreshed catalog in a version: nexus-release.