메뉴
Export live CLI-first Nexus tool schemas as JSON. Use when the user wants every tool schema, a subset by selector, or an artifact that reflects the current runtime command/argument shape instead of source parsing.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Read, search, and edit the user's Obsidian vault (notes, folders, canvas, tasks, memory/workspaces, saved prompts) from the shell via the `nexus` CLI — no MCP connection needed. Use whenever the user refers to their vault, notes, daily notes, second brain, or Obsidian, or asks you to find/read/change something stored there.
Grade LLM models on Nexus tool-use (the two-tool getTools/useTools protocol) with the live eval harness in tests/eval/. Use when asked to grade, benchmark, or evaluate one or more OpenRouter (or other provider) models for how well they drive Nexus tools — e.g. "grade google/gemma-4-31b-it" or "benchmark these models on our harness".
Version bump and GitHub Actions release for the Nexus Obsidian plugin. Use when the user wants to cut a release, bump the version, or publish a new version after stable changes are ready.
Add, update, or verify Nexus LLM provider model definitions. Use when adding newly released models, changing OpenAI/OpenRouter/Codex/GitHub Copilot/Anthropic/Google model metadata, updating provider defaults, or live-testing whether a model ID works through the reusable provider smoke test.
Version bump and GitHub Actions release for the Nexus Obsidian plugin. Use when the user wants to cut a release, bump the version, or publish a new version after stable changes are ready.
Version bump and GitHub Actions release for the Nexus Obsidian plugin. Use when the user wants to cut a release, bump the version, or publish a new version after stable changes are ready.
| name | nexus-tool-schemas |
| description | Export live CLI-first Nexus tool schemas as JSON. Use when the user wants every tool schema, a subset by selector, or an artifact that reflects the current runtime command/argument shape instead of source parsing. |
Use this skill when the task is to generate or refresh JSON exports of the plugin's CLI-first tool schemas.
scripts/generate-tool-schemas.mjsToolCliNormalizer.buildCliSchema() runtime pathThis is the source of truth for the exported shape. Do not hand-assemble schema JSON unless the script is broken and you are fixing it.
Run:
npm run schemas:tools
This writes the default full export to:
docs/generated/cli-first-tool-schemas.json
Use --selector with the same selector grammar as getTools:
npm run schemas:tools -- --selector "storage"
npm run schemas:tools -- --selector "storage move, content read"
npm run schemas:tools -- --selector "prompt generate-image"
Use --output to control the destination:
npm run schemas:tools -- --selector "task" --output docs/generated/task-tool-schemas.json
npm run schemas:tools -- --selector "web-tools capture-to-markdown" --output -
--output - prints JSON to stdout instead of writing a file.
--selector and --output as needed.npm run sync:skills
getTools.