Brainstorming
xpinjection/test-driven-spring-boot
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior.
Write and edit CCSDS MO service XML specification files following the established conventions of the mo-services-java project (ServiceSchema-v003).
$ npx skills add esa/nanosat-mo-framework --skill mo-xml -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install esa/nanosat-mo-framework mo-xml --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/esa/nanosat-mo-framework.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/mo-xml .claude/skills/mo-xml && 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 "mo-xml" agent skill from https://github.com/esa/nanosat-mo-framework/tree/master/.claude/skills/mo-xml into .claude/skills/mo-xml/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mo-xml", 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/esa/nanosat-mo-framework/tree/master/.claude/skills/mo-xmlType 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 esa/nanosat-mo-framework --skill mo-xml -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install esa/nanosat-mo-framework mo-xml --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/esa/nanosat-mo-framework.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/mo-xml .agents/skills/mo-xml && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "mo-xml" agent skill from https://github.com/esa/nanosat-mo-framework/tree/master/.claude/skills/mo-xml into .agents/skills/mo-xml/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mo-xml", 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 esa/nanosat-mo-framework --skill mo-xml -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install esa/nanosat-mo-framework mo-xml --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/esa/nanosat-mo-framework.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/mo-xml .cursor/skills/mo-xml && 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 "mo-xml" agent skill from https://github.com/esa/nanosat-mo-framework/tree/master/.claude/skills/mo-xml into .cursor/skills/mo-xml/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mo-xml", 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/esa/nanosat-mo-framework.git --path .claude/skills/mo-xml--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 esa/nanosat-mo-framework --skill mo-xml -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install esa/nanosat-mo-framework mo-xml --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/esa/nanosat-mo-framework.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/mo-xml .gemini/skills/mo-xml && 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 "mo-xml" agent skill from https://github.com/esa/nanosat-mo-framework/tree/master/.claude/skills/mo-xml into .gemini/skills/mo-xml/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mo-xml", 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 esa/nanosat-mo-framework mo-xmlInstalls 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 esa/nanosat-mo-framework --skill mo-xml -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/esa/nanosat-mo-framework.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/mo-xml .github/skills/mo-xml && 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 "mo-xml" agent skill from https://github.com/esa/nanosat-mo-framework/tree/master/.claude/skills/mo-xml into .github/skills/mo-xml/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mo-xml", 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 esa/nanosat-mo-framework --skill mo-xml -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install esa/nanosat-mo-framework mo-xml --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/esa/nanosat-mo-framework.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/mo-xml .opencode/skills/mo-xml && 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 "mo-xml" agent skill from https://github.com/esa/nanosat-mo-framework/tree/master/.claude/skills/mo-xml into .opencode/skills/mo-xml/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mo-xml", 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.
mo-xmlWrite and edit CCSDS MO service XML specification files following the established conventions of the mo-services-java project (ServiceSchema-v003).
Mo XML is an agent skill from esa/nanosat-mo-framework. Write and edit CCSDS MO service XML specification files following the established conventions of the mo-services-java project (ServiceSchema-v003). Use whenever creating or modifying files under core/mo-services-xml/.
Its SKILL.md is about 6k 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 Java. The repository describes itself as: A software framework for small satellites based on CCSDS MO services.
12 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 126d437. It shows what the files ask for, not the result of running them.
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.
No scripts in the folder and no shell commands in SKILL.md (its code samples are xml).
From the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
ccsds.orgw3.orggithub.comFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Mo XML loads about 6k tokens when it runs. Until then it costs about 56 tokens; SKILL.md has 2,126 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.
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.
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 2,126 words (~6,045 tokens).
Just SKILL.md in .claude/skills/mo-xml of esa/nanosat-mo-framework.
Open the folder on GitHubat commit 126d437
Mo XML 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 |
|---|---|---|---|---|---|---|
| Mo XML this skillesa/nanosat-mo-framework | 125 | — | ~6k | Automated safety check: Pass | Custom licence | |
| Brainstormingxpinjection/test-driven-spring-boot | 112 | 54 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Android API Diffgkd-kit/gkd | 43k | — | ~796 | Automated safety check: Pass | GPL-3.0 | |
| Video Cover Imageitwanger/toBeBetterJavaer | 18k | — | ~3.3k | Automated safety check: Pass | None | |
| Lancedb Update Lance Dependencylancedb/lancedb | 12k | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Java SDK E2E Test with Replay Snapshotgithub/copilot-sdk | 11k | — | ~1.8k | Automated safety check: Pass | MIT |
xpinjection/test-driven-spring-boot
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior.
gkd-kit/gkd
Looks up Android framework Java and AIDL APIs across versions with the android-api-diff CLI: signatures, availability, source files and hidden-API access code.
itwanger/toBeBetterJavaer
Generate matched 3:4, 16:9, and 4:3 short-video cover images from toBeBetterJavaer video scripts or AI/Java technical topics.
lancedb/lancedb
Update LanceDB to a specific Lance release or tag. An agent skill from lancedb/lancedb.
github/copilot-sdk
Creates a Java SDK end-to-end test for the Copilot SDK that runs against a recorded YAML snapshot through a replay proxy, so CI needs no real authentication.
apache/fory
Prepare an Apache Fory release candidate from a clean release branch, including the version bump, RC tag, JVM staging, ASF source artifacts, SVN upload, and vote email.
Works with
Write and edit CCSDS MO service XML specification files following the established conventions of the mo-services-java project (ServiceSchema-v003). Mo XML is an agent skill from esa/nanosat-mo-framework. Write and edit CCSDS MO service XML specification files following the established conventions of the mo-services-java project (ServiceSchema-v003).
Mo XML fits situations like: modifying files under core/mo-services-xml/.
Run `npx skills add esa/nanosat-mo-framework --skill mo-xml -a claude-code`. Or copy the skill folder (.claude/skills/mo-xml in esa/nanosat-mo-framework) into .claude/skills/mo-xml in your project. Claude Code loads it when a task matches its description.
Run `npx skills add esa/nanosat-mo-framework --skill mo-xml -a codex`. Or copy the skill folder (.claude/skills/mo-xml in esa/nanosat-mo-framework) into .agents/skills/mo-xml in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add esa/nanosat-mo-framework --skill mo-xml -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/mo-xml, .gemini/skills/mo-xml, .github/skills/mo-xml and .opencode/skills/mo-xml in your project.
SKILL.md names no scripts, command-line tools or credentials: Mo XML is instructions for the agent only.
SKILL.md names 3 domains. In commands or code: ccsds.org, w3.org and github.com; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.
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.
Mo XML has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
About 6k tokens (SKILL.md is roughly 24k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Mo XML: Brainstorming (xpinjection/test-driven-spring-boot, 112 stars), Android API Diff (gkd-kit/gkd, 43k stars), Video Cover Image (itwanger/toBeBetterJavaer, 18k stars) and Lancedb Update Lance Dependency (lancedb/lancedb, 12k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
esa (a GitHub organization) maintains it in esa/nanosat-mo-framework, which has 125 GitHub stars. The repository was last updated on October 6, 2026.
Source: esa/nanosat-mo-framework on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.