dspace-groupdspace-group/SystemDeskMCP/.github/skills/smoke-test/SKILL.md

smoke-test

Skill3 starsChanged 15 days agoApache-2.0View on GitHub

End-to-end smoke test for the SystemDesk MCP server.

21 other projects use a version of this.

Adopted by

Most recently taken up by

AJschoons/robowrighttheir own version, first seen Nov 8, 2026
blamechris/chroxytheir own version, first seen Nov 8, 2026
crbnos/carbontheir own version, first seen Nov 7, 2026
danielvm-git/bigpowerstheir own version, first seen Nov 6, 2026
Draganoider/claude-code-telegramtheir own version, first seen Oct 20, 2026
garrytan/gbraintheir own version, first seen Oct 17, 2026

Used with

Projects with it also use debugging-difficult-bugs, pr-explainer and 1 more.

Other files people use alongside this one.

dzevsSkill
debugging-difficult-bugs
Use early when debugging a medium or hard bug, especially when tests alone may not reveal the real runtime failure. Trigger this before extended TDD iteration when a bug involves runtime state, PTY/terminal ordering, persistence, streaming, async/concurrency, the TUI/manual reproduction, the IPC socket layer, or when a red or newly passing test may not model the real issue. Skip only when the root cause is already directly proven by a stack trace or deterministic test that exercises the real runtime path.
Also in 3 projects that use this
Mathews-TomSkill
pr-explainer
Use when a developer asks to explain a pushed PR, walk through a PR stack, understand one stack member, or explain what an AI agent just pushed so they can connect code changes to end-to-end functionality and update domain knowledge. Not for defect review, merge approval, PR-body authoring, or full-repository onboarding.
Also in 3 projects that use this
dzevsSkill
pr-splitter
Use when breaking a large, complex, messy, or hard-to-review pull request into multiple smaller PRs; planning stacked PRs; extracting independent changes from a branch; splitting mixed refactor and behavior changes; managing drift after review feedback (operator gate, Codex/swarm second opinion); rebasing follow-up PRs as earlier PRs change; or preserving original branch intent while shipping incrementally.
Also in 3 projects that use this

Other versions21 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 21
garrytan/gbrain★ 32ksame name
mastra-ai/mastra★ 29ksame name
JoshuaC215/agent-service-toolkit★ 4.6ksame name
crbnos/carbon★ 2.8ksame name
peteonrails/voxtype★ 1.8ksame name
nginx/nginx-s3-gateway★ 761same name
danielvm-git/bigpowers★ 288same name
andrew-yangy/gru-ai★ 153same name
stacklok/toolhive-registry-server★ 29same name
sohei56/maul-team★ 17same name
11 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repositoryOne other file it gives its agents.
- AGENTS.mdAGENTS.md

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 7 are distinctive, and 1 is very specific to this project.

0
Common
Most of the 18 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Distinctive:
Use the SystemDesk MCP Server to perform an end-to-end smoke test, ensuring that the core functionalities are working as expected.
line 8
Distinctive:
Do NOT inspect the files in this workspace, only rely on the information provided in this prompt and by the MCP server.
line 13
Distinctive:
Do NOT read the repository memory or state from previous sessions.
line 14
Distinctive:
Do NOT write to the repository memory.
line 15
Distinctive:
Always clean up any created directories or files after the test execution, regardless of the test results.
line 19
Very specific:
Import tests\smoke-test.arxml and create a composition at /SWA/Compositions/SmokeComposition containing /SWA/A and /SWA/B.
line 21
Distinctive:
Use the tools provided by the SystemDesk MCP server to validate the project.
line 22
Distinctive:
After validation, use the tools provided by the SystemDesk MCP server to get the status of SystemDesk and whether a project is opened.
line 30

“Common” is measured: kept by at least 6 in 10 of the 18 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

Goal

Use the SystemDesk MCP Server to perform an end-to-end smoke test, ensuring that the core functionalities are working as expected.

Rules

Work in %TEMP% for any file or directory creation. Do not create files or directories outside of this location.
Do NOT inspect the files in this workspace, only rely on the information provided in this prompt and by the MCP server.
Do NOT read the repository memory or state from previous sessions. Fail the run, if it happens.
Do NOT write to the repository memory. Fail the run and delete the created memory, if it happens.

Instructions

Always clean up any created directories or files after the test execution, regardless of the test results.
SystemDesk.exe should not be running before the test starts.
Import tests\smoke-test.arxml and create a composition at /SWA/Compositions/SmokeComposition containing /SWA/A and /SWA/B.
Use the tools provided by the SystemDesk MCP server to validate the project. The following results are expected from the validation:
- 1 Error
  - /SWA/B/InternalBehavior/DataReceivedEvent is missing the "DataIref".
- 4 Warnings
  - /SWA/A/InternalBehavior/Runnable is not triggered by any event.
  - /SWA/RootComposition/AssemblySwConnector_022a6a18ca20b376e84badaf962bf0ac is an incompatible connection.
  - /SWA/Compositions/SmokeComposition has two warnings for unconnected receiver elements B.RPort.E1 and B.RPort.E2.
After validation, use the tools provided by the SystemDesk MCP server to get the status of SystemDesk and whether a project is opened. The expected results are:
- SystemDesk is running.
- A project is opened.
- The project is modified.
Close SystemDesk.
SystemDesk.exe should not be running after the test finishes. Allow a grace period for it to close properly.

Fail the test if any of the expected results are not met, or if SystemDesk.exe is running at the wrong times.

Output

Provide a summary of the results. Be pedantic if something seems wrong. Be concise.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free