New: 97,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 Testing

by ProfSynapse in ProfSynapse/nexus

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.

MITAuto-check passedTesting & QA

Install Nexus Testing

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

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

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

At a glance

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.

  • Works in 5 steps: Pick the job and open its protocol. Work… → Derive every list from the tree, never… → Before calling a testing change done,… → …
  • A mock might be deciding the outcome
  • SKILL.md covers Workflow, Map, Siblings — do not duplicate… and Status of the in-app loop
  • Runs Python scripts from its folder; calls python3

What it does

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

Its SKILL.md is about 990 tokens, which your agent loads only when the skill is triggered. The skill folder holds 16 other files, including scripts and reference files (for example `protocols/fix-shipped-docs-drift.md`, `protocols/headless-obsidian.md` and `protocols/live-loop.md`).

It sits in Testing & QA, covering Unit testing and LLM evaluation. It works with Obsidian and Jest. The licence is MIT.

When your agent uses it

  • A mock might be deciding the outcome
  • A change has to be proven in the running plugin
  • The guidance gate fails

Example prompts

  • “/nexus-testing”

Requirements

  • Python 3

Workflow steps

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

  1. Pick the job and open its protocol. Work from the protocol, not from this
  2. Derive every list from the tree, never from a document. This skill states no
  3. Before calling a testing change done, run both checks from the repo root and
  4. NEVER claim a change is verified in the app on the strength of Jest alone.
  5. 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 6cb7bce. 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:

    • python3

    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 Testing loads about 994 tokens when it runs, and up to ~3.8k if it reads all its reference files. Until then it costs about 88 tokens; SKILL.md has 457 words of instructions outside code blocks.

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

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 6cb7bce, republished under its MIT licence (© ProfSynapse). 457 words, ~994 tokens.

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

Testing Nexus

Context: every Jest lane resolves obsidian to a hand-written mock — see moduleNameMapper in jest.config.js. A green suite therefore proves the code agrees with tests/mocks/obsidian/, not with Obsidian. Three ranking defects shipped past that suite. Everything below exists to close the gap between what Jest can prove and what the running plugin does.

Workflow

  1. Pick the job and open its protocol. Work from the protocol, not from this router — the router names procedures, it does not contain them.

    JobProtocol
    Add or change a testprotocols/write-a-test.md
    Prove a change works in the running pluginprotocols/live-loop.md
    No Obsidian here (container / cloud session)protocols/headless-obsidian.md
    Run a gated live-smoke lane or the eval harnessprotocols/run-gated-lanes.md
    shippedGuidanceCommands or ToolManagerCliSyntax is redprotocols/fix-shipped-docs-drift.md
    Merge a PR (what to run first, how to gate on CI)protocols/merge-a-pr.md
    A symptom you cannot placereferences/troubleshooting.md

  2. Derive every list from the tree, never from a document. This skill states no test counts, no lane inventory and no env-var table on purpose, and you MUST NOT add one — those rot silently and a rotted list is worse than none. references/lanes.md holds the discovery commands.

  3. Before calling a testing change done, run both checks from the repo root and fix anything they print:

    bash
    python3 .claude/skills/nexus-testing/scripts/check_live_lane_gates.py
python3 .claude/skills/nexus-testing/scripts/check_catalog_target.py

  4. NEVER claim a change is verified in the app on the strength of Jest alone. If the change touches load order, rendering, hydration or anything that only exists once the plugin is running, protocols/live-loop.md is the proof and nothing else is.

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

Show full SKILL.md (196 more words)Show less

Map

  • protocols/ the procedures: write-a-test, live-loop, headless-obsidian, run-gated-lanes, fix-shipped-docs-drift, self-refine.
  • references/ read on demand: lanes.md (where a test goes and how to find what exists), mock-honesty.md (the two habits that make a test able to fail), troubleshooting.md (symptom → cause).
  • scripts/ the mechanical checks named in step 3. Run them; do not reimplement them.
  • refinement-log.md what past sessions changed here and why.

Siblings — do not duplicate them here

  • nexus-eval-harness — configuring, extending and debugging the eval harness. This skill covers only running it and the two knobs that surprise people.
  • nexus-model-eval — grading specific models.
  • nexus-tool-schemas — regenerating the tool catalog (no running vault needed).
  • nexus-agents — the two-tool contract and the useTools payload shape a test has to build.
  • nexus-mobile-compat — the mobile failure class the in-app loop cannot see.
  • nexus-storage — resetting persisted state when a plugin reload is not enough.

Status of the in-app loop

Exercised 2026-08-14 against Obsidian 1.13.7 in a headless Linux container and 2026-08-21 against Obsidian 1.12.7 on macOS. Setup, vault-targeted plugin:reload, dev:errors, dev:console, dev:screenshot, dev:debug, and synchronous eval are confirmed working. The first run found a startup-ordering bug that every Jest lane was blind to; the macOS run confirmed explicit vault=<name> targeting and clean repeated reloads.

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

  • SKILL.md
  • protocols/fix-shipped-docs-drift.md
  • protocols/headless-obsidian.md
  • protocols/live-loop.md
  • protocols/merge-a-pr.md
  • protocols/run-gated-lanes.md
  • protocols/self-refine.md
  • protocols/write-a-test.md
  • references/lanes.md
  • references/mock-honesty.md
  • references/troubleshooting.md
  • refinement-log.md
  • scripts/check_catalog_target.py
  • scripts/check_live_lane_gates.py

Open the folder on GitHubat commit 6cb7bce

Compare with similar skills

Nexus Testing 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 Testing compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Nexus Testing this skillProfSynapse/nexus154—~994Automated safety check: PassMIT
TDDRafaelGB/Obsidian-ZettelFlow174—~724Automated safety check: PassMIT
Jest Testing PatternsChrisWiles/claude-code-showcase6.1k7 repos~1.5kAutomated safety check: PassNone
Test GuardamElnagdy/guard-skills1.3k2 repos~2.1kAutomated safety check: PassMIT
Vitestpixel-point/animate-text1492 repos~1.3kAutomated safety check: PassNone
Test Guidelinesgetsentry/sentry-react-native1.8k—~1.3kAutomated safety check: PassMIT

Similar skills

  • TDD

    RafaelGB/Obsidian-ZettelFlow

    The test-driven development workflow for ZettelFlow — write a failing test first, run jest, use the Obsidian mock and the bare-specifier alias mappings, and know which code is unit-testable.

    174 GitHub stars~724 tokensUpdated today
    Testing & QAAuto-check passed

  • Jest Testing Patterns

    ChrisWiles/claude-code-showcase

    Jest patterns for React Native style tests: TDD discipline, mock factory functions, module and GraphQL hook mocking, custom render helpers and anti-patterns to avoid.

    6.1k GitHub starsUsed in 7 repos~1.5k tokens
    Testing & QAAuto-check passed

  • Test Guard

    amElnagdy/guard-skills

    Reviews newly written or edited tests against nine rules that cut test bloat, such as mock-heavy checks and near-duplicate cases, before they are committed.

    1.3k GitHub starsUsed in 2 repos~2.1k tokens
    Testing & QAAuto-check passed

  • Vitest

    pixel-point/animate-text

    Vitest testing framework patterns for test setup, async testing, mocking with vi., snapshots, and test performance (formerly test-vitest).

    149 GitHub starsUsed in 2 repos~1.3k tokens
    Testing & QAAuto-check passed

  • Test Guidelines

    getsentry/sentry-react-native

    Official

    Enforce Sentry React Native SDK test conventions for naming, structure, mocking, and fixtures with Jest.

    1.8k GitHub stars~1.3k tokensUpdated today
    Testing & QAAuto-check passed

  • Designing Tests

    CloudAI-X/claude-workflow-v2

    Designs and implements testing strategies for any codebase. An agent skill from CloudAI-X/claude-workflow-v2.

    1.4k GitHub starsUsed in 1 repo~1.5k tokens
    Testing & QAAuto-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.

    154 GitHub stars~843 tokensUpdated 5 days ago
    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…

    154 GitHub stars~1k tokensUpdated 5 days ago
    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.

    154 GitHub stars~1k tokensUpdated 5 days ago
    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.

    154 GitHub stars~1.1k tokensUpdated 5 days ago
    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…

    154 GitHub stars~944 tokensUpdated 5 days ago
    Auto-check passed

  • Nexus Storage

    ProfSynapse/nexus

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

    154 GitHub stars~749 tokensUpdated 5 days ago
    Auto-check passed

Works with

Categories

Questions about Nexus Testing

What does Nexus Testing do?

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

When should I use Nexus Testing?

Nexus Testing fits situations like: A mock might be deciding the outcome; A change has to be proven in the running plugin; the guidance gate fails.

How do I install Nexus Testing in Claude Code?

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

How do I install Nexus Testing in Codex?

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

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

What does Nexus Testing need to run?

Going by SKILL.md and its folder, Nexus Testing needs Python for the scripts in its folder and the command-line tools its instructions call (python3). Our summary lists: Python 3.

Does Nexus Testing 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 Testing 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 Testing use?

Nexus Testing 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 Testing use?

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

What are the alternatives to Nexus Testing?

Skills that share tags, products or a category with Nexus Testing: TDD (RafaelGB/Obsidian-ZettelFlow, 174 stars), Jest Testing Patterns (ChrisWiles/claude-code-showcase, 6.1k stars), Test Guard (amElnagdy/guard-skills, 1.3k stars) and Vitest (pixel-point/animate-text, 149 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Nexus Testing?

ProfSynapse (a GitHub user) maintains it in ProfSynapse/nexus, which has 154 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on October 2, 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.