New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Nexus Tool Schemas

by ProfSynapse in ProfSynapse/nexus

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.

MITAuto-check passed

Install Nexus Tool Schemas

skills CLI
$ npx skills add ProfSynapse/nexus --skill nexus-tool-schemas -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install ProfSynapse/nexus nexus-tool-schemas --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/ProfSynapse/nexus.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.skills/nexus-tool-schemas .claude/skills/nexus-tool-schemas && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
nexus-tool-schemas
GitHub stars
157
Token cost
~637 tokens
SKILL.md length
303 words
Files
10 (incl. scripts, references)
Skills in repo
12
Repo updated
First seen
Licence
MIT

At a glance

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.

  • Works in 4 steps: Decide which job this is. The answer is… → Run that protocol end to end. You MUST… → Validate what you produced with… → …
  • Someone asks for tool schemas
  • SKILL.md covers Workflow, Map and Siblings
  • Runs Python scripts from its folder; calls npm

What it does

Nexus Tool Schemas is an agent skill from ProfSynapse/nexus. 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.

Its SKILL.md is about 640 tokens, which your agent loads only when the skill is triggered. The skill folder holds 13 other files, including scripts and reference files (for example `agents/openai.yaml`, `protocols/export-subset.md` and `protocols/refresh-catalog.md`).

The licence is MIT.

When your agent uses it

  • Someone asks for tool schemas
  • The exact command/argument shape a caller sees
  • After changing a tools parameter schema
  • After touching ToolCliNormalizer

Example prompts

  • “/nexus-tool-schemas”

Requirements

  • Python 3
  • Node.js

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Decide which job this is. The answer is the output path, and choosing it by
  2. Run that protocol end to end. You MUST NOT hand-write or hand-patch either
  3. Validate what you produced with scripts/check_catalog.py before reporting
  4. At the end of a session that used this skill, run protocols/self-refine.md.

What it can do on your machine

Read from SKILL.md and the folder at commit eb20895. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 2 files in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Nexus Tool Schemas loads about 637 tokens when it runs, and up to ~2.3k if it reads all its reference files. Until then it costs about 107 tokens; SKILL.md has 303 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~107
When it runs · the whole SKILL.md, loaded when a task matches
~637
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from ProfSynapse/nexus at commit eb20895, republished under its MIT licence (© ProfSynapse). 303 words, ~637 tokens.

Download SKILL.mdSave it as .claude/skills/nexus-tool-schemas/SKILL.md (or your agent's skills folder). This skill also uses 9 other files; get the full folder from GitHub.
name
nexus-tool-schemas
description
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.

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

  1. 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
  2. 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.
  3. Validate what you produced with scripts/check_catalog.py before reporting it, and treat a non-zero exit as a stop.
  4. 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.

© ProfSynapse, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 9 other files (scripts, references) in .skills/nexus-tool-schemas of ProfSynapse/nexus.

  • SKILL.md
  • agents/openai.yaml
  • protocols/export-subset.md
  • protocols/refresh-catalog.md
  • protocols/self-refine.md
  • references/consumers.md
  • references/exporter-internals.md
  • refinement-log.md
  • scripts/check_catalog.py
  • scripts/check_exporter_coverage.py

Open the folder on GitHubat commit eb20895

Compare with similar skills

Nexus Tool Schemas next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Nexus Tool Schemas compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Nexus Tool Schemas this skillProfSynapse/nexus157—~637Automated safety check: PassMIT
Schema Markupalirezarezvani/claude-skills28k1 repos~2.9kAutomated safety check: PassMIT
Database Schema Designeralirezarezvani/claude-skills28k1 repos~1.9kAutomated safety check: PassMIT
Export0xsline/OpenChatCut2.2k—~2.2kAutomated safety check: WarnAGPL-3.0
GEO Schema Auditorzubair-trabzada/geo-seo-claude11k2 repos~3.7kAutomated safety check: NotesMIT
Export Download Debuggingnexu-io/open-design100k—~725Automated safety check: PassApache-2.0

Similar skills

  • Schema Markup

    alirezarezvani/claude-skills

    When the user wants to implement, audit, or validate structured data (schema markup) on their website.

    28k GitHub starsUsed in 1 repo~2.9k tokens
    Marketing & SEOAuto-check passed

  • Database Schema Designer

    alirezarezvani/claude-skills

    A skill your agent uses when the user asks to create ERD diagrams, normalize database schemas, design table relationships, or plan schema migrations.

    28k GitHub starsUsed in 1 repo~1.9k tokens
    DatabasesAuto-check passed

  • Export

    0xsline/OpenChatCut

    A skill your agent uses when a OpenChatCut video editing or creation workflow needs export, render, download, share, final delivery, subtitle-file export, render choice, local-only asset handling…

    2.2k GitHub stars~2.2k tokensUpdated 2 days ago
    Media & CreativeAuto-check: warnings

  • GEO Schema Auditor

    zubair-trabzada/geo-seo-claude

    Audits a page's Schema.org structured data for AI discoverability, validates it, generates JSON-LD to fill gaps and writes a GEO-SCHEMA-REPORT.md.

    11k GitHub starsUsed in 2 repos~3.7k tokens
    Marketing & SEOAuto-check: notes

  • Export Download Debugging

    nexu-io/open-design

    Diagnose and fix browser, preview, or Electron export/download failures, especially image export issues involving Save As, Blob/Data URLs, the File System Access API, createWritable failures, and 0…

    100k GitHub stars~725 tokensUpdated today
    DevelopmentAuto-check passed

  • Cost Export

    ruvnet/ruflo

    Export cost-tracking telemetry in Prometheus textfile or webhook JSON formats — for external observability (Grafana, Datadog, custom dashboards)

    74k GitHub stars~687 tokensUpdated today
    DevOps & CloudAuto-check: notes

More from ProfSynapse/nexus

All 12 skills in this repo

  • Nexus Agents

    ProfSynapse/nexus

    How to add, change and verify a Nexus agent or tool, and the contract every tool must satisfy.

    157 GitHub stars~843 tokensUpdated yesterday
    Auto-check passed

  • Nexus Eval Harness

    ProfSynapse/nexus

    Work on the Nexus LLM eval harness in tests/eval/ — author or fix a scenario fixture, write an eval config, change the executors, assertions or reports, or explain a run that produced nothing…

    157 GitHub stars~1k tokensUpdated yesterday
    Auto-check passed

  • Nexus Model Eval

    ProfSynapse/nexus

    Grade how well a model drives the Nexus two-tool protocol (getTools/useTools) and decide whether a low score is the model's fault or the harness's.

    157 GitHub stars~1k tokensUpdated yesterday
    Auto-check passed

  • Nexus Model Updates

    ProfSynapse/nexus

    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.

    157 GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

  • Nexus Release

    ProfSynapse/nexus

    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…

    157 GitHub stars~944 tokensUpdated yesterday
    Auto-check passed

  • Nexus Storage

    ProfSynapse/nexus

    How to change, persist, migrate and recover Nexus data without losing it.

    157 GitHub stars~749 tokensUpdated yesterday
    Auto-check passed

Questions about Nexus Tool Schemas

What does Nexus Tool Schemas do?

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. Nexus Tool Schemas is an agent skill from ProfSynapse/nexus. 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.

When should I use Nexus Tool Schemas?

Nexus Tool Schemas fits situations like: someone asks for tool schemas; the exact command/argument shape a caller sees; after changing a tools parameter schema; after touching ToolCliNormalizer.

How do I install Nexus Tool Schemas in Claude Code?

Run `npx skills add ProfSynapse/nexus --skill nexus-tool-schemas -a claude-code`. Or copy the skill folder (.skills/nexus-tool-schemas in ProfSynapse/nexus) into .claude/skills/nexus-tool-schemas in your project. Claude Code loads it when a task matches its description.

How do I install Nexus Tool Schemas in Codex?

Run `npx skills add ProfSynapse/nexus --skill nexus-tool-schemas -a codex`. Or copy the skill folder (.skills/nexus-tool-schemas in ProfSynapse/nexus) into .agents/skills/nexus-tool-schemas in your project. Codex loads it when a task matches its description.

Can I use Nexus Tool Schemas in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ProfSynapse/nexus --skill nexus-tool-schemas -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/nexus-tool-schemas, .gemini/skills/nexus-tool-schemas, .github/skills/nexus-tool-schemas and .opencode/skills/nexus-tool-schemas in your project.

What does Nexus Tool Schemas need to run?

Going by SKILL.md and its folder, Nexus Tool Schemas needs Python for the scripts in its folder and the command-line tools its instructions call (npm). Our summary lists: Python 3; Node.js.

Does Nexus Tool Schemas access the network?

SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Nexus Tool Schemas safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Nexus Tool Schemas use?

Nexus Tool Schemas is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Nexus Tool Schemas use?

About 637 tokens (SKILL.md is roughly 2.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.7k tokens, read only when the agent opens those files.

What are the alternatives to Nexus Tool Schemas?

Skills that share tags, products or a category with Nexus Tool Schemas: Schema Markup (alirezarezvani/claude-skills, 28k stars), Database Schema Designer (alirezarezvani/claude-skills, 28k stars), Export (0xsline/OpenChatCut, 2.2k stars) and GEO Schema Auditor (zubair-trabzada/geo-seo-claude, 11k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Nexus Tool Schemas?

ProfSynapse (a GitHub user) maintains it in ProfSynapse/nexus, which has 157 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on October 8, 2026.

Source: ProfSynapse/nexus on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.