Agent skill

Nexus LLM Adapters

by ProfSynapse in ProfSynapse/nexus

How to add or debug a Nexus LLM provider adapter — what every adapter must wire, how to verify it against a live provider, and the failure modes that produce a silently blank chat.

MITAuto-check passedDevelopment

Install Nexus LLM Adapters

skills CLI
$ npx skills add ProfSynapse/nexus --skill nexus-llm-adapters -a claude-code

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

GitHub CLI
$ gh skill install ProfSynapse/nexus nexus-llm-adapters --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-llm-adapters .claude/skills/nexus-llm-adapters && 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-llm-adapters
GitHub stars
157
Token cost
~704 tokens
SKILL.md length
308 words
Files
13 (incl. scripts, references)
Skills in repo
12
Repo updated
First seen
Licence
MIT

At a glance

How to add or debug a Nexus LLM provider adapter — what every adapter must wire, how to verify it against a live provider, and the failure modes that produce a silently blank chat.

  • Works in 4 steps: Adding or changing an adapter — follow… → Chat is blank, missing reasoning,… → Before calling any adapter change done —… → …
  • Changing a provider adapter
  • SKILL.md covers Workflow, Map, Siblings — do not duplicate… and Refine
  • Runs Python scripts from its folder

What it does

Nexus LLM Adapters is an agent skill from ProfSynapse/nexus. How to add or debug a Nexus LLM provider adapter — what every adapter must wire, how to verify it against a live provider, and the failure modes that produce a silently blank chat. Use when adding or changing a provider adapter, debugging streaming or reasoning display, working with local or CLI-backed models, or touching chat branch plumbing.

Its SKILL.md is about 700 tokens, which your agent loads only when the skill is triggered. The skill folder holds 15 other files, including scripts and reference files (for example `protocols/add-adapter.md`, `protocols/debug-adapter.md` and `protocols/self-refine.md`).

It sits in Development, covering Debugging. The licence is MIT.

When your agent uses it

  • Changing a provider adapter
  • Debugging streaming
  • Reasoning display
  • Working with local

Example prompts

  • “/nexus-llm-adapters”

Requirements

  • Python 3

Workflow steps

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

  1. Adding or changing an adapter — follow protocols/add-adapter.md. It is a
  2. Chat is blank, missing reasoning, looping, or doubling — follow
  3. Before calling any adapter change done — run protocols/verify-adapter.md.
  4. 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 1 file in scripts/ (Python), which the agent can run.

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

  • Network

    No URLs in SKILL.md.

    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 LLM Adapters loads about 704 tokens when it runs, and up to ~7.7k if it reads all its reference files. Until then it costs about 91 tokens; SKILL.md has 308 words of instructions outside code blocks.

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

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). 308 words, ~704 tokens.

Download SKILL.mdSave it as .claude/skills/nexus-llm-adapters/SKILL.md (or your agent's skills folder). This skill also uses 12 other files; get the full folder from GitHub.
name
nexus-llm-adapters
description
How to add or debug a Nexus LLM provider adapter — what every adapter must wire, how to verify it against a live provider, and the failure modes that produce a silently blank chat. Use when adding or changing a provider adapter, debugging streaming or reasoning display, working with local or CLI-backed models, or touching chat branch plumbing.

Nexus LLM adapters

Adapters live in src/services/llm/adapters/{provider}/ and extend BaseAdapter, which talks direct HTTP through ProviderHttpClient. There are no vendor LLM SDKs in this repo; adding one is a decision to raise, not to make.

This router points at the procedure. The detail loads when you take the path.

Workflow

  1. Adding or changing an adapter — follow protocols/add-adapter.md. It is a wiring checklist; work it in order rather than pattern-matching an existing adapter, because the pieces that get forgotten are the ones no compiler checks.
  2. Chat is blank, missing reasoning, looping, or doubling — follow protocols/debug-adapter.md. Start from the symptom, not the adapter source: these failures have known causes and reading code first wastes the trip.
  3. Before calling any adapter change done — run protocols/verify-adapter.md. You MUST exercise the non-streaming path, the streaming path, and the streaming error path separately; they fail independently and unit tests prove none of them. You MUST also run scripts/check_stream_error_wiring.py on the adapter you touched and get a zero exit.
  4. End of a session that used this skill — run protocols/self-refine.md.

Map

  • protocols/ the procedures: add-adapter, debug-adapter, verify-adapter, self-refine.
  • references/ mechanism and rationale, read on demand: symptoms.md (the symptom→cause lookup the debug protocol enters through), streaming-contract.md, reasoning-rendering.md, local-providers.md, cli-providers.md, chat-plumbing.md.
  • scripts/check_stream_error_wiring.py — checks that an adapter parsing an SSE stream wires extractError. Run it, do not re-derive it by reading source.

Siblings — do not duplicate them here

  • nexus-model-updates owns model metadata: ids, pricing, context windows, capability flags, provider defaults, and the live provider smoke test.
  • nexus-model-eval and nexus-eval-harness own grading models on tool use.
  • nexus-testing owns test lanes, what a mock can prove, and the in-app loop.
  • nexus-mobile-compat owns Node imports, dependency vetting, and desktop-only gating — which every adapter that shells out or touches the filesystem needs.

Refine

At the end of a session that used this skill, run protocols/self-refine.md and append to refinement-log.md.

© 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 12 other files (scripts, references) in .skills/nexus-llm-adapters of ProfSynapse/nexus.

  • SKILL.md
  • protocols/add-adapter.md
  • protocols/debug-adapter.md
  • protocols/self-refine.md
  • protocols/verify-adapter.md
  • references/chat-plumbing.md
  • references/cli-providers.md
  • references/local-providers.md
  • references/reasoning-rendering.md
  • references/streaming-contract.md
  • references/symptoms.md
  • refinement-log.md
  • scripts/check_stream_error_wiring.py

Open the folder on GitHubat commit eb20895

Compare with similar skills

Nexus LLM Adapters 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 LLM Adapters compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Nexus LLM Adapters this skillProfSynapse/nexus157—~704Automated safety check: PassMIT
Trellis Session Insightmindfold-ai/Trellis15k4 repos~1.7kAutomated safety check: PassAGPL-3.0
Native Data FetchingCherryHQ/cherry-studio-app4k6 repos~2.9kAutomated safety check: NotesMIT
Debugging Executionsn8n-io/n8n207k—~2.6kAutomated safety check: PassCustom licence
Aoti Debugpytorch/pytorch104k1 repos~1.7kAutomated safety check: PassCustom licence
Herdr Throwaway Reproductionherdrdev/herdr43k—~2.4kAutomated safety check: PassApache-2.0

Similar skills

  • Trellis Session Insight

    mindfold-ai/Trellis

    Reach into past AI conversation history through the trellis mem CLI.

    15k GitHub starsUsed in 4 repos~1.7k tokens
    DevelopmentAuto-check passed
  • Native Data Fetching

    CherryHQ/cherry-studio-app

    A skill your agent uses when implementing or debugging ANY network request, API call, or data fetching.

    4k GitHub starsUsed in 6 repos~2.9k tokens
    DevelopmentAuto-check: notes
  • Official

    Debug failed or wrong-output workflow executions using executions tools.

    207k GitHub stars~2.6k tokensUpdated today
    DevelopmentAuto-check passed
  • Aoti Debug

    pytorch/pytorch

    Debug AOTInductor (AOTI) errors and crashes. An agent skill from pytorch/pytorch.

    104k GitHub starsUsed in 1 repo~1.7k tokens
    DevelopmentAuto-check passed
  • Runs a disposable, uniquely named Herdr session inside an existing one so runtime, pane, terminal or API bugs can be reproduced without touching the main session.

    43k GitHub stars~2.4k tokensUpdated today
    DevelopmentAuto-check passed
  • Systematic Debugging

    ultralisp/ultralisp

    A skill your agent uses when encountering any bug, test failure, or unexpected behavior, before proposing fixes

    258 GitHub starsUsed in 51 repos~2.4k tokens
    DevelopmentAuto-check passed

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 today
    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 today
    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 today
    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 today
    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 today
    Auto-check passed
  • Nexus Storage

    ProfSynapse/nexus

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

    157 GitHub stars~749 tokensUpdated today
    Auto-check passed

Categories

Questions about Nexus LLM Adapters

What does Nexus LLM Adapters do?

How to add or debug a Nexus LLM provider adapter — what every adapter must wire, how to verify it against a live provider, and the failure modes that produce a silently blank chat. Nexus LLM Adapters is an agent skill from ProfSynapse/nexus. How to add or debug a Nexus LLM provider adapter — what every adapter must wire, how to verify it against a live provider, and the failure modes that produce a silently blank chat.

When should I use Nexus LLM Adapters?

Nexus LLM Adapters fits situations like: changing a provider adapter; debugging streaming; reasoning display; working with local.

How do I install Nexus LLM Adapters in Claude Code?

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

How do I install Nexus LLM Adapters in Codex?

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

Can I use Nexus LLM Adapters 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-llm-adapters -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-llm-adapters, .gemini/skills/nexus-llm-adapters, .github/skills/nexus-llm-adapters and .opencode/skills/nexus-llm-adapters in your project.

What does Nexus LLM Adapters need to run?

Going by SKILL.md and its folder, Nexus LLM Adapters needs Python for the scripts in its folder. Our summary lists: Python 3.

Does Nexus LLM Adapters access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Nexus LLM Adapters 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 LLM Adapters use?

Nexus LLM Adapters 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 LLM Adapters use?

About 704 tokens (SKILL.md is roughly 2.8k 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 7k tokens, read only when the agent opens those files.

What are the alternatives to Nexus LLM Adapters?

Skills that share tags, products or a category with Nexus LLM Adapters: Trellis Session Insight (mindfold-ai/Trellis, 15k stars), Native Data Fetching (CherryHQ/cherry-studio-app, 4k stars), Debugging Executions (n8n-io/n8n, 207k stars) and Aoti Debug (pytorch/pytorch, 104k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Nexus LLM Adapters?

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.