setup
/setup
Verify that the Dometrain MCP tools are available to the Dometrain grounding skills, without reading or exposing any API key. Use when: 'set up Dometrain', 'configure Dometrain', 'Dometrain setup', the Dometrain MCP server is unavailable, or a Dometrain tool reports an authentication error. Actions: check (read-only verification, default and only action). This plugin has no options and ships no server: the tools come from a user-scope dometrain server, so there is nothing an apply could write.
- Author
- melodic-software ↗
- Repository
- claude-code-plugins ↗
- Licence
- MIT
- Last repository change
- 26.10.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 10
No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Verify that the Dometrain MCP tools are available to the Dometrain grounding skills, without reading or exposing any API key. Use when: 'set up Dometrain', 'configure Dometrain', 'Dometrain setup', the Dometrain MCP server is unavailable, or a Dometrain tool reports an authentication error. Actions: check (read-only verification, default and only action). This plugin has no options and ships no server: the tools come from a user-scope dometrain server, so there is nothing an apply could write.
Triggers from the description
Arguments
/setup [check]
Original author description
Verify that the Dometrain MCP tools are available to the Dometrain grounding skills, without reading or exposing any API key. Use when: 'set up Dometrain', 'configure Dometrain', 'Dometrain setup', the Dometrain MCP server is unavailable, or a Dometrain tool reports an authentication error. Actions: check (read-only verification, default and only action). This plugin has no options and ships no server: the tools come from a user-scope dometrain server, so there is nothing an apply could write.
How it works
- Purpose
- Task
- Headless installation
- Output
- Namespace-collision note
- Boundaries
SKILL.md preview
---
description: "Verify that the Dometrain MCP tools are available to the Dometrain grounding skills, without reading or exposing any API key. Use when: 'set up Dometrain', 'configure Dometrain', 'Dometrain setup', the Dometrain MCP server is unavailable, or a Dometrain tool reports an authentication error. Actions: check (read-only verification, default and only action). This plugin has no options and ships no server: the tools come from a user-scope dometrain server, so there is nothing an apply could write."
argument-hint: "[check]"
user-invocable: true
disable-model-invocation: true
---
## Purpose
Report whether a Dometrain MCP server is reachable from this session, without reading, printing,
or writing any API key. This plugin ships skills only. The tools come from a user-scope
`dometrain` MCP server the user registered, per the README's
[Getting the MCP server](../../README.md#getting-the-mcp-server).
That server exposes its tools under a `dometrain` server segment. This skill matches on the
server segment and tool name in the runtime inventory and never on a fixed prefix, because Claude
Code owns the prefix format and can change it.
Check-only per the uniform setup contract's carve-out for a plugin with no options: `check`
(default and only action) verifies and reports. The server keeps its credential outside this
skill, so it never manages it.
**Mechanism note (why this skill does not read `/mcp`):** `/mcp` is a human-run interactive
command. No tool exposes its output to a model turn. The one model-visible signal for a failed
remote server is the connection error Claude Code itself reports to Claude, which this skill reads
when it is present and never assumes when it is absent. This skill is built around that
constraint, not around reading `/mcp` connection status directly.
- **Pointer**: when deciding what a missing Dometrain tool can tell this skill, fetch
[How Claude learns that a server failed](https://code.claude.com/docs/en/mcp#how-claude-learns-that-a-server-failed)
live.
- **As of**: 2026-10-11
- **Recheck trigger**: that section changes which configurations report a failed server to
Claude, or where the error appears.
Official contracts:
- <https://code.claude.com/docs/en/plugins/manifest-reference#defaultenabled>
- <https://code.claude.com/docs/en/mcp#how-claude-learns-that-a-server-failed> (as of
2026-10-11; recheck when that section changes which configurations report a failed server to
Claude)
## Task
1. Check whether a Dometrain tool (e.g. `list_courses`, `search_dometrain`) is present in the
current tool inventory, matched by the `dometrain` server segment and the tool name. Do not inspect
settings files, environment variables, process arguments, debug logs, credential stores, or
any key.
2. When a Dometrain tool resolves (via direct tool-list presence or a successful `ToolSearch`
match), report **connected**. Do not claim the credential has valid API access beyond that. A connection-layer 401/403/429 rejection
(per Dometrain's own README Troubleshooting section) would prevent the tool from resolving at
all, so resolution itself is the strongest signal this skill can observe.
3. When no Dometrain tool resolves and `ToolSearch` returned no connection
error for a `dometrain` server, report **disabled**: no server is present. Point to the
README's [Getting the MCP server](../../README.md#getting-the-mcp-server) for registering a
user-scope server. Do not run the command for the user. For a non-interactive install (CI, a
fleet bootstrap, a scripted machine setup), point to the headless path below.
4. When a user-scope server is registered but no tool resolves, report **failed or unverified**:
- If `ToolSearch` returned a connection error for the `dometrain` server, quote it verbatim.
- Otherwise do not assert why. Whether a failed connection reaches this turn depends on
configuration this skill cannot inspect (see the mechanism note's pointer in
[Purpose](#purpose); as of 2026-10-11; recheck when that pointer moves out of
Purpose, is dropped, or its as-of date changes).
Direct the user to run `/mcp` themselves rather than claim knowledge it does not have.
- Do not send the user to `/plugin configure`: point them to `claude mcp list` for a
missing-variable warning on the `dometrain` entry and to the README's
[Getting the MCP server](../../README.md#getting-the-mcp-server); a variable set after Claude
Code started needs a new session, since Claude Code expands it from its own environment at
connect time.
## Headless installation
For a non-interactive install such as CI, a fleet bootstrap, or a scripted machine setup, install
and enable the skills, then register the user-scope server per the README's
[Getting the MCP server](../../README.md#getting-the-mcp-server). Every step is required. At
`user` scope, on a CLI that supports `--marketplace` on `install`, add the marketplace and install
in one step:
```shell
claude plugin install dometrain --marketplace <source> -s user
claude plugin enable dometrain -s user
```
At `project` or `local` scope, or on an older CLI, keep the two-step form, so the marketplace is
registered in the same scope as the install:
```shell
claude plugin marketplace add <source> --scope <scope>
claude plugin install dometrain@<marketplace> -s <scope>
claude plugin enable dometrain -s <scope>
```
- **Pointer**: when choosing between the two forms, fetch
[Plugin commands reference: plugin install](https://code.claude.com/docs/en/plugins/cli-reference#plugin-install)
(the `--marketplace` row and its minimum version) and
[Add a marketplace and install in one command](https://code.claude.com/docs/en/plugins/install#add-a-marketplace-and-install-in-one-command)
(which scope the added marketplace lands in) live.
- **As of**: 2026-10-10
- **Recheck trigger**: the `--marketplace` row of `plugin install` changes, or that install section
changes where the one-step form registers the marketplace.
`<marketplace>` is the name the catalog registers under when it is added, and `<scope>` is the
scope the bootstrap chooses: `user`, `project`, or `local`. Pass the scope explicitly on every
command and carry the same `<scope>` through all of them.
- **Pointer**: when a command's scope default or flag spelling matters, fetch
[plugin marketplace add](https://code.claude.com/docs/en/plugins/cli-reference#plugin-marketplace-add),
[plugin install](https://code.claude.com/docs/en/plugins/cli-reference#plugin-install) and
[plugin enable](https://code.claude.com/docs/en/plugins/cli-reference#plugin-enable) live.
- **As of**: 2026-10-11
- **Recheck trigger**: any of those three rows changes its scope default or its flag spelling.
Registering at `user` while installing at `project`
leaves the marketplace declaration out of the project's checked-in settings, so a fresh clone or CI
agent carries the enabled plugin with no registered marketplace to resolve it from.
**The enable step is not optional.** The plugin ships `defaultEnabled: false`, so it installs
DISABLED and its skills stay unavailable until it is enabled ([Default
enablement](https://code.claude.com/docs/en/plugins/manifest-reference#defaultenabled)).
Pass `-s` to [`claude plugin enable`](https://code.claude.com/docs/en/plugins/cli-reference#plugin-enable)
explicitly, so the sequence stays deterministic in CI. A bootstrap that stops after `install` looks successful and delivers
no skills.
## Output
Report exactly one state: `disabled`, `connected`, or `failed or unverified`. Include the exact
next action when the state is not `connected`.
## Namespace-collision note
Dometrain ships its own official Claude Code plugin (`github.com/Dometrain/mcp`) whose
`plugin.json` `name` is also `"dometrain"`. If the user has that plugin enabled too, do not attempt
to detect the collision by comparing MCP tool-name prefixes. A true collision produces an
*identical*, not divergent, prefix, so no prefix comparison can distinguish "one plugin enabled" from
"two colliding plugins enabled." Point the user to this plugin's README collision warning instead.
## Boundaries
- Do not read, echo, log, copy, or persist any API key.
- Do not write the plugin cache, Claude Code user settings, or `pluginConfigs`, per the uniform
setup contract (`docs/plugin-philosophy.md` "Setup is explicit and repeatable" in the
marketplace repository).
- Do not call a Dometrain tool during setup. Resolution via tool inventory / `ToolSearch` is
sufficient and spends no quota.
- Do not claim to have read `/mcp` connection status. No tool exposes it to a model turn.
Files in this package (2)
- SKILL.md 8 KB
- evals/evals.json 2 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · melodic-software/claude-code-plugins | 84 | MIT |
| HwangSlater/harness-fit | 100 | MIT |
| nesquikm/dev-process-toolkit | 100 | MIT |
| userKael/rastro | 100 | MIT |
| als-apg/osprey | 100 | BSD-3-Clause |
| dedujeong/gemba | 100 | Apache-2.0 |
| eigenwise/eigenwise-toolshed | 100 | MIT |
| awrshift/agent-memory-kit | 100 | MIT |
| lifecycle-innovations-limited/claude-ops | 100 | MIT |
Database snapshot: 13.11.2026 · package version e93efe162b84 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 84grounding
Ground an approach in how a Dometrain course teaches it, via the Dometrain MCP server, and cite lessons with timestamped deep links. Use when: 'implementing', 'designing', 'reviewing', or 'debugging' anything covered by a Dometrain course: C#/.NET, ASP.NET Core, EF Core,… - 90dometrain-grounding
Use when implementing, designing, reviewing, or debugging anything a Dometrain course covers (C#/.NET, ASP.NET Core, EF Core, testing, design patterns, architecture, messaging, databases, cloud/DevOps, TypeScript, AI development) — ground the approach in how the course teaches… - 84sync
Maintainer-only drift check for the grounding skill's vendored upstream content. Never model-invocable: only a human explicitly running /dometrain:sync. Use when: 'check dometrain sync drift', 'has the dometrain-grounding skill changed upstream', before a version bump, or at a… - 100setup-api-key
Guides users through setting up an ElevenLabs API key for ElevenLabs MCP tools. Use when the user needs to configure an ElevenLabs API key, when ElevenLabs tools fail due to missing API key, or when the user mentions needing access to ElevenLabs. First checks whether… - 100setup-api-key
Guides users through setting up an ElevenLabs API key for ElevenLabs MCP tools. Use when the user needs to configure an ElevenLabs API key, when ElevenLabs tools fail due to missing API key, or when the user mentions needing access to ElevenLabs. First checks whether…