ClawHub

MCSManager Controller

v1.0.1

Control and troubleshoot MCSManager-managed Minecraft servers through the MCSManager API and clearly provided host-side context. Use when asked to start, sto...

⭐ 0· 115·0 current·0 all-time
by@szabee13
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name/description (MCSManager control) align with the instructions and included reference notes. The skill requires no unrelated environment variables or binaries and only asks for a local config pattern appropriate for a panel API client.
ℹ
Instruction Scope
Instructions are scoped and explicitly instruct the agent to use only user-provided config or an intentionally created local config.json and to avoid rummaging through unrelated files. They allow host-side process/port/log checks but only when the user explicitly supplies host-side troubleshooting context—this is reasonable but requires the user to avoid pasting sensitive credentials into chat.
✓
Install Mechanism
Instruction-only skill with no install spec and no code files to execute. Nothing will be downloaded or written by an installer; the only file-write behavior described is creating a local config.json from the provided example when the user explicitly requests reusable local config.
✓
Credentials
The skill declares no required environment variables, no primary credential, and no config paths. The config.example.json shows the expected fields (baseUrl, apiKey, instanceUuid) and these are proportional to the stated purpose (API access to MCSManager).
✓
Persistence & Privilege
Skill is not always-enabled and is user-invocable. Autonomous invocation (model calling the skill) is allowed by default (platform normal). The skill does not request permanent system-wide privileges or modify other skills' configs.
Assessment
This skill appears coherent and narrowly scoped to controlling MCSManager instances. Before using it: 1) Do not paste production API keys or host credentials into chat — instead store them in a local config.json you create and keep untracked. 2) Confirm the skill only acts on instances you explicitly name and always confirm destructive actions (stop/kill). 3) Test on a non-production server first. 4) Note the skill's source/homepage is not provided (owner ID only); if you require provenance, ask the publisher or prefer a skill with a known repository. Otherwise the included files and instructions look appropriate for the stated purpose.

Like a lobster shell, security has layers — review code before you run it.

latestvk97aaxa37qk77re0d5zs2x3yp98387c0

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments