Minimax DOCX
poco-ai/poco-claw
Professional DOCX document creation, editing, and formatting using OpenXML SDK (.NET).
Guides work that changes or reviews MCServerLauncher Future domain behavior.
GPL-3.0Auto-check passed
Install Mcsl Future
$ npx skills add MCSLTeam/MCServerLauncher-Future --skill mcsl-future -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install MCSLTeam/MCServerLauncher-Future mcsl-future --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/MCSLTeam/MCServerLauncher-Future.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/mcsl-future .claude/skills/mcsl-future && rm -rf skills-srcUse ~/.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/
Install the "mcsl-future" agent skill from https://github.com/MCSLTeam/MCServerLauncher-Future/tree/master/skills/mcsl-future into .claude/skills/mcsl-future/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcsl-future", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/MCSLTeam/MCServerLauncher-Future/tree/master/skills/mcsl-futureType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add MCSLTeam/MCServerLauncher-Future --skill mcsl-future -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install MCSLTeam/MCServerLauncher-Future mcsl-future --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MCSLTeam/MCServerLauncher-Future.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/mcsl-future .agents/skills/mcsl-future && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "mcsl-future" agent skill from https://github.com/MCSLTeam/MCServerLauncher-Future/tree/master/skills/mcsl-future into .agents/skills/mcsl-future/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcsl-future", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add MCSLTeam/MCServerLauncher-Future --skill mcsl-future -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install MCSLTeam/MCServerLauncher-Future mcsl-future --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MCSLTeam/MCServerLauncher-Future.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/mcsl-future .cursor/skills/mcsl-future && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "mcsl-future" agent skill from https://github.com/MCSLTeam/MCServerLauncher-Future/tree/master/skills/mcsl-future into .cursor/skills/mcsl-future/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcsl-future", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/MCSLTeam/MCServerLauncher-Future.git --path skills/mcsl-future--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add MCSLTeam/MCServerLauncher-Future --skill mcsl-future -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install MCSLTeam/MCServerLauncher-Future mcsl-future --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MCSLTeam/MCServerLauncher-Future.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/mcsl-future .gemini/skills/mcsl-future && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "mcsl-future" agent skill from https://github.com/MCSLTeam/MCServerLauncher-Future/tree/master/skills/mcsl-future into .gemini/skills/mcsl-future/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcsl-future", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install MCSLTeam/MCServerLauncher-Future mcsl-futureInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add MCSLTeam/MCServerLauncher-Future --skill mcsl-future -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/MCSLTeam/MCServerLauncher-Future.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/mcsl-future .github/skills/mcsl-future && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "mcsl-future" agent skill from https://github.com/MCSLTeam/MCServerLauncher-Future/tree/master/skills/mcsl-future into .github/skills/mcsl-future/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcsl-future", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add MCSLTeam/MCServerLauncher-Future --skill mcsl-future -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install MCSLTeam/MCServerLauncher-Future mcsl-future --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MCSLTeam/MCServerLauncher-Future.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/mcsl-future .opencode/skills/mcsl-future && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "mcsl-future" agent skill from https://github.com/MCSLTeam/MCServerLauncher-Future/tree/master/skills/mcsl-future into .opencode/skills/mcsl-future/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcsl-future", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
mcsl-future- GitHub stars
- 121
- Token cost
- ~1.2k tokens
- SKILL.md length
- 487 words
- Files
- 1
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- GPL-3.0
At a glance
Guides work that changes or reviews MCServerLauncher Future domain behavior.
- Works in 5 steps: Read PROJECT_PLAN.md. → Read RULES.md. → Declare touched areas. → …
- Daemon protocol
- SKILL.md covers Quick Start, Invariants, Task Recipes and Red Flags, plus 2 more sections
- Calls dotnet, pwsh and git
What it does
Mcsl Future is an agent skill from MCSLTeam/MCServerLauncher-Future. Guides work that changes or reviews MCServerLauncher Future domain behavior. Use for daemon protocol, instance lifecycle, file/path handling, installers, serialization, WPF instance submission, or event semantics, not ordinary docs-only edits.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It works with C# and .NET. The repository describes itself as: Future version of MCSL, a brand new server management tool. Redefined, Versatile, Easy to use. (WPF Launcher & Daemon). The licence is GPL-3.0.
When your agent uses it
- Daemon protocol
- Instance lifecycle
- File/path handling
- WPF instance submission
Example prompts
- “Use the mcsl-future skill to guide work that changes or reviews MCServerLauncher Future domain behavior”
- “/mcsl-future”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Read PROJECT_PLAN.md.
- Read RULES.md.
- Declare touched areas.
- Preserve the invariants below.
- Run the smallest relevant verification.
What it can do on your machine
Read from SKILL.md and the folder at commit 0057061. 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
Shell commands in SKILL.md call:
dotnetpwshgit
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
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
Mcsl Future loads about 1.2k tokens when it runs. Until then it costs about 64 tokens; SKILL.md has 487 words of instructions outside code blocks.
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); files beside SKILL.md are not scanned.
SKILL.md
The full file from MCSLTeam/MCServerLauncher-Future at commit 0057061, republished under its GPL-3.0 licence (© MCSLTeam). 487 words, ~1,195 tokens.
Download SKILL.mdSave it as
.claude/skills/mcsl-future/SKILL.md (or your agent's skills folder).- name
- mcsl-future
- description
- Guides work that changes or reviews MCServerLauncher Future domain behavior. Use for daemon protocol, instance lifecycle, file/path handling, installers, serialization, WPF instance submission, or event semantics, not ordinary docs-only edits.
MCServerLauncher Future
Quick Start
- Read
PROJECT_PLAN.md. - Read
RULES.md. - Declare touched areas.
- Preserve the invariants below.
- Run the smallest relevant verification.
Invariants
- Client-daemon communication uses JSON-RPC 2.0 plus versioned binary transfer frames over the sole
/api/v2WebSocket endpoint. - Shared serialized wire contracts live in
src/MCServerLauncher.Common; transport-neutral application/plugin contracts live insrc/MCServerLauncher.Daemon.API. - Daemon behavior has one application implementation; transport, console, event rules, WPF, and plugins delegate to it.
- Protocol and plugin serialization uses explicit source-generated
System.Text.Jsonmetadata with no reflection fallback. - Plugin-enabled publishing is untrimmed JIT single-file plus sidecars. Keep trim analysis, but do not claim Native AOT or trimmed plugin-host support.
- Plugins are trusted and startup-only. Plugin API 2.0 admits features via
mcsl-plugin.json(requires.features); first-milestone runtime implementsrpc.register,event.publish, andinstance.query, with Preview-1 expanding the vocabulary for operations/provisioning/auth/HTTP. - Instance catalog reads use deep immutable copy-on-write published state.
- Instance creation remains factory-driven through
IInstanceFactoryand[InstanceFactory]. - WPF user-facing text uses
Lang.Tr[...]. - Daemon path handling validates trust boundaries before file access.
Task Recipes
Protocol or serialization. Start with serialized DTOs in Common and typed definitions/application contracts in Daemon API, then update daemon, daemon client, WPF, generated docs, protocol tests, and benchmarks. Do not add V1 fallback or reflection metadata discovery.
Application core. Put behavior behind the four domain application services. Console, event rules, JSON-RPC bindings, and plugins must not duplicate manager/storage rules.
Published state. Keep snapshot values deeply immutable. Current/TryGet reads are lock-free and allocation-free; I/O, callbacks, logging, and await never occur under the writer lock.
Plugins. Validate mcsl-plugin.json, API version, features, references, namespace ownership, and catalog conflicts before commit. A failed plugin must leave no host-owned registration or lifetime residue and must not stop daemon startup.
Instance lifecycle. Public application methods use Task<Result<T, DaemonError>>; legacy manager Result<T, Error> paths stay implementation-only until the V2 deletion gate. Preserve cancellation and daemon-side authority for state changes.
Installer changes. Keep mirror behavior explicit, preserve Forge-family format differences, and validate cached/downloaded libraries when checksums exist.
WPF create-instance flows. Validate form values before submission, but keep daemon-side validation authoritative.
Events. Preserve missing/null/object meta/data semantics, typed canonical filtering, reconnect resubscription, connection-owned ordering, slow-consumer disconnect, and serialization-once fan-out.
Show full SKILL.md (133 more words)Show less
Red Flags
- Frontend-only validation becomes the only security or path-safety check.
- Reflection is added to protocol/plugin DTO serialization or runtime catalog discovery.
- Daemon internals, TouchSocket, MessagePipe, Serilog, root DI, mutable collections, or disposable handles leak into Daemon API.
- V1/V2 fallback, dual dispatch, legacy envelope detection, or compatibility wrappers are introduced.
- Plugin hooks, hot unload, factory/store/control/filesystem capabilities, or plugin dependencies are added before an approved plan and real consumer exist.
- A protocol field changes without protocol tests.
- Domain vocabulary changes without updating
PROJECT_PLAN.mdandRULES.md.
Verification
- Docs: inspect Markdown and run terminology searches.
- Daemon API:
dotnet build src/MCServerLauncher.Daemon.API/MCServerLauncher.Daemon.API.csproj /m:1 - WPF:
dotnet build src/MCServerLauncher.WPF/MCServerLauncher.WPF.csproj /m:1 - Daemon:
dotnet build src/MCServerLauncher.Daemon/MCServerLauncher.Daemon.csproj /m:1 - Protocol:
dotnet test tests/MCServerLauncher.ProtocolTests/MCServerLauncher.ProtocolTests.csproj /m:1 - Generated docs:
dotnet run --project tools/MCServerLauncher.ProtocolDocs/MCServerLauncher.ProtocolDocs.csproj -- --check - V1 deletion:
pwsh -File tools/VerifyNoV1Runtime.ps1 - Final:
git diff --check
Commits
Use type(scope): subject.
© MCSLTeam, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/mcsl-future of MCSLTeam/MCServerLauncher-Future.
Open the folder on GitHubat commit 0057061
Compare with similar skills
Mcsl Future 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Mcsl Future this skillMCSLTeam/MCServerLauncher-Future | 121 | — | ~1.2k | Automated safety check: Pass | GPL-3.0 | |
| Minimax DOCXpoco-ai/poco-claw | 1.4k | 7 repos | ~3.9k | Automated safety check: Pass | MIT | |
| Speckit ConstitutionWeihanLi/WeihanLi.Common | 242 | 11 repos | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| Analyzing .NET Performancedotnet/skills | 5.6k | 3 repos | ~3.1k | Automated safety check: Pass | MIT | |
| Add Analyzerdotnet/roslynator | 3.5k | — | ~1.3k | Automated safety check: Pass | Custom licence | |
| GitVersion .NET DevelopmentGitTools/GitVersion | 3.1k | — | ~1.7k | Automated safety check: Pass | MIT |
Similar skills
Speckit Constitution
WeihanLi/WeihanLi.Common
Create or update the project constitution from interactive or provided principle inputs, ensuring all dependent templates stay in sync.
- Official
Analyzing .NET Performance
dotnet/skills
Scans C# and .NET code for about 50 performance anti-patterns and reports prioritized findings with concrete fixes, at a scan depth you choose.
- Official
Add Analyzer
dotnet/roslynator
A skill your agent uses when adding a new RCS diagnostic in roslynator (RCS0 formatting, RCS1 general, RCS9 code-analysis), wiring roslynator EditorConfig options, or when docs say CHANGELOG.md…
GitVersion .NET Development
GitTools/GitVersion
Gives repository-specific .NET guidance for GitVersion: build and test commands, central package management, project layout and coding conventions.
- Official
Code Review
dotnet/macios
Review dotnet/macios PRs against established rules. An agent skill from dotnet/macios.
More from MCSLTeam/MCServerLauncher-Future
Init My Project
MCSLTeam/MCServerLauncher-Future
Bootstrap reusable project governance for a new or existing repo.
Related
Questions about Mcsl Future
What does Mcsl Future do?
Guides work that changes or reviews MCServerLauncher Future domain behavior. Mcsl Future is an agent skill from MCSLTeam/MCServerLauncher-Future. Guides work that changes or reviews MCServerLauncher Future domain behavior.
When should I use Mcsl Future?
Mcsl Future fits situations like: daemon protocol; instance lifecycle; file/path handling; WPF instance submission.
How do I install Mcsl Future in Claude Code?
Run `npx skills add MCSLTeam/MCServerLauncher-Future --skill mcsl-future -a claude-code`. Or copy the skill folder (skills/mcsl-future in MCSLTeam/MCServerLauncher-Future) into .claude/skills/mcsl-future in your project. Claude Code loads it when a task matches its description.
How do I install Mcsl Future in Codex?
Run `npx skills add MCSLTeam/MCServerLauncher-Future --skill mcsl-future -a codex`. Or copy the skill folder (skills/mcsl-future in MCSLTeam/MCServerLauncher-Future) into .agents/skills/mcsl-future in your project. Codex loads it when a task matches its description.
Can I use Mcsl Future 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 MCSLTeam/MCServerLauncher-Future --skill mcsl-future -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/mcsl-future, .gemini/skills/mcsl-future, .github/skills/mcsl-future and .opencode/skills/mcsl-future in your project.
What does Mcsl Future need to run?
Going by SKILL.md and its folder, Mcsl Future needs the command-line tools its instructions call (dotnet, pwsh and git).
Does Mcsl Future access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Mcsl Future 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. Review the folder before installing.
What licence does Mcsl Future use?
Mcsl Future is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Mcsl Future use?
About 1.2k tokens (SKILL.md is roughly 4.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Mcsl Future?
Skills that share tags, products or a category with Mcsl Future: Minimax DOCX (poco-ai/poco-claw, 1.4k stars), Speckit Constitution (WeihanLi/WeihanLi.Common, 242 stars), Analyzing .NET Performance (dotnet/skills, 5.6k stars) and Add Analyzer (dotnet/roslynator, 3.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Mcsl Future?
MCSLTeam (a GitHub organization) maintains it in MCSLTeam/MCServerLauncher-Future, which has 121 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on September 4, 2026.
Source: MCSLTeam/MCServerLauncher-Future on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.