Agent skill

AgentSys Cross-Platform Maintenance

by agent-sh in agent-sh/agentsys

Maintainer guide to where AgentSys keeps its marketplace, installer, transforms and adapters, and what to run when preparing a release or fixing a platform bug.

MITAuto-check passedAgent Workflows

Install AgentSys Cross-Platform Maintenance

skills CLI
$ npx skills add agent-sh/agentsys --skill maintain-cross-platform -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install agent-sh/agentsys maintain-cross-platform --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/agent-sh/agentsys.git skills-src && mkdir -p .claude/skills && cp -r skills-src/meta/skills/maintain-cross-platform .claude/skills/maintain-cross-platform && rm -rf skills-src

Use ~/.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/

Facts

Skill name
maintain-cross-platform
GitHub stars
994
Token cost
~1.2k tokens
SKILL.md length
489 words
Files
1
Skills in repo
1
Repo updated
First seen
Licence
MIT

At a glance

Maintainer guide to where AgentSys keeps its marketplace, installer, transforms and adapters, and what to run when preparing a release or fixing a platform bug.

  • Preparing an AgentSys release
  • SKILL.md covers Where things live, Platform differences behind…, Checks and Output
  • Calls npm, node and npx
  • Checking cross-platform compatibility of the installer or adapters

What it does

AgentSys installs the agent-sh plugins on Claude Code, OpenCode, Codex CLI, Cursor and Kiro, and this maintainer skill, for that repository only, works as a map. A table says where each concern lives: the marketplace file and its pinning script, the installer in `bin/cli.js` with one function per tool, transforms in `lib/adapter-transforms.js` (synced from agent-core, so changes belong there), platform adapters, dev installs, version bumps and generated documentation sections.

It also lists the differences behind most cross-platform bugs: the plugin root variable differs between Claude Code and the other hosts, Windows backslashes in `require()` paths must be normalized, and the state directory should come from `AI_STATE_DIR` instead of a hardcoded `.claude/`. For current facts it points to the compatibility checklist, `docs/CROSS_PLATFORM.md` and the release checklists rather than memory.

When your agent uses it

  • Preparing an AgentSys release
  • Checking cross-platform compatibility of the installer or adapters
  • Changing marketplace pins, transforms or adapter generation

Example prompts

  • “Re-pin the marketplace entries with a dry run first and show me what would change.”
  • “A Windows install fails with a path error in a require call; find where the path handling lives.”
  • “Walk me through what to run before cutting the next AgentSys release.”

Requirements

  • A checkout of the AgentSys repository
  • GitHub CLI `gh` and Node.js, for the marketplace pinning script

What it can do on your machine

Read from SKILL.md and the folder at commit 68eb4a7. 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:

    • npm
    • node
    • npx

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npm and npx, 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

AgentSys Cross-Platform Maintenance loads about 1.2k tokens when it runs. Until then it costs about 52 tokens; SKILL.md has 489 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~52
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k

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 agent-sh/agentsys at commit 68eb4a7, republished under its MIT licence (© agent-sh). 489 words, ~1,215 tokens.

Download SKILL.mdSave it as .claude/skills/maintain-cross-platform/SKILL.md (or your agent's skills folder).
name
maintain-cross-platform
description
Use when preparing an AgentSys release, checking cross-platform compatibility, or changing the installer, transforms, adapters or marketplace pins. Maintainer skill for this repo only.
metadata.short-description
Maintain AgentSys across its five platforms
metadata.scope
local
metadata.audience
repo-maintainers

Maintain cross-platform AgentSys

AgentSys installs the agent-sh plugins on Claude Code, OpenCode, Codex CLI, Cursor and Kiro. The plugins live in their own repos; this repo owns the marketplace, the installer, the transforms and the docs. Use this skill to find where a cross-platform concern lives and what to run.

Platform details (config formats, frontmatter, env vars, label limits) are in checklists/cross-platform-compatibility.md and docs/CROSS_PLATFORM.md; release steps are in checklists/release.md and agent-docs/release.md. Read them for the current facts instead of relying on memory.

Where things live

ConcernLocation
Marketplace, one entry per plugin pinned by tag and commit.claude-plugin/marketplace.json; re-pin with node scripts/pin-marketplace.js [--dry-run] (needs gh)
Installerbin/cli.js: installForClaude, installForOpenCode, installForCodex, installForCursor, installForKiro. Claude Code installs from the marketplace; the others fetch plugin sources into ~/.agentsys/plugins/<name> and transform them.
Transforms (frontmatter, tools to permissions, plugin-root paths, namespaces)lib/adapter-transforms.js. lib/ is synced from agent-sh/agent-core, so make the change there; an edit here is overwritten by the next sync.
Platform adaptersadapters/opencode-plugin/ (native OpenCode plugin), adapters/opencode/, adapters/codex/; scripts/gen-adapters.js keeps generated files fresh
Dev installsnode bin/dev-cli.js dev-install [tool] (scripts/dev-install.js)
Versionspackage.json is the source; npx agentsys-dev bump X.Y.Z stamps package-lock.json, .claude-plugin/plugin.json, marketplace.json and site/content.json. Plugin repos version independently.
Generated doc sections<!-- GEN:START:... --> blocks, rewritten by npx agentsys-dev gen-docs

Platform differences behind most bugs

  • Plugin root: ${CLAUDE_PLUGIN_ROOT} in Claude Code, ${PLUGIN_ROOT} in OpenCode and Codex; Cursor and Kiro get the install path inlined. Normalize backslashes in require() paths (.replace(/\\/g, '/')), because a Windows path such as C:\Users\... turns into escape sequences.
  • State directory: use AI_STATE_DIR (.opencode, .codex, .cursor, .kiro; unset means .claude) instead of a hardcoded .claude/. validate paths catches hardcoded ones.
  • OpenCode: model fields are stripped by default (--no-strip keeps them), tools become permission: entries, and AskUserQuestion labels longer than 30 characters fail.
  • Codex has no commands or agents: commands become skills invoked as $name, so every skill description needs trigger phrases ("Use when ...").
  • Kiro: commands become prompts in ~/.kiro/prompts/, agents become JSON in ~/.kiro/agents/, and two combined reviewer agents fit its 4-subagent limit. Each skill directory is copied whole to ~/.kiro/skills/<name>/, away from its plugin, so the installer and the Kiro transforms point plugin-root wording ("two directories up from this skill"), relative links that leave the skill directory, and versioned-cache globs (**/<plugin>/*/) at ~/.agentsys/plugins/<plugin>.
Show full SKILL.md (119 more words)Show less

Checks

CommandCovers
npm run validateplugins, cross-platform, consistency, paths, counts, platform-docs, agent-skill-compliance
npm testJest suite
npm run gen-docs:check, node scripts/expand-templates.js --check, node scripts/gen-adapters.js --checkGenerated content is fresh (CI runs all three)
npx agentsys-dev preflight [--all|--release]Change-aware checklist checks. The pre-push hook runs it, asks for the /enhance confirmation, and runs --release when a v* tag is pushed.
node bin/dev-cli.js validate opencode-installA real OpenCode install (not part of validate)
npm pack --dry-runThe package builds

Before a release, smoke-test the installer: npm pack, npm install -g ./agentsys-*.tgz, run agentsys, and check each platform's install directory as checklists/release.md lists.

If this skill or a checklist no longer matches the code, fix it in the same change.

Output

markdown
## Cross-Platform Compatibility Check

### Validations run
- [OK|ERROR] <validator>: <one line>

### Issues
- <file:line>: <problem> - <fix>

### Docs out of date
- <file>: <what no longer matches>

### Actions taken
- <files changed>

### Next steps
- <remaining work, or "none">

© agent-sh, MIT. 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 meta/skills/maintain-cross-platform of agent-sh/agentsys.

Open the folder on GitHubat commit 68eb4a7

Compare with similar skills

AgentSys Cross-Platform Maintenance 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.

AgentSys Cross-Platform Maintenance compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
AgentSys Cross-Platform Maintenance this skillagent-sh/agentsys994—~1.2kAutomated safety check: PassMIT
Publish Plugins Version Bumpvinta/hal-90001381 repos~1kAutomated safety check: PassMIT
Watchmen Setupfirstbatchxyz/watchmen296—~1.1kAutomated safety check: NotesMIT
Mistral Vibe CLI Referencemistralai/mistral-vibe5.1k—~14kAutomated safety check: NotesApache-2.0
OmniRoute Plugins, Skills and Memory CLIdiegosouzapw/OmniRoute74k—~1kAutomated safety check: PassMIT
Superset Plugins and Toolssuperset-sh/superset15k—~1.3kAutomated safety check: PassCustom licence

Similar skills

  • Finds which plugins in the repository changed, bumps only the ones not already bumped since origin/main, and checks that each plugin's two manifests stay in sync.

    138 GitHub starsUsed in 1 repo~1k tokens
    Agent WorkflowsAuto-check passed
  • Watchmen Setup

    firstbatchxyz/watchmen

    Walks through installing watchmen, running its init wizard, wiring the plugin into Codex or Claude Code and checking the result with doctor.

    296 GitHub stars~1.1k tokensUpdated 1 mo ago
    Agent WorkflowsAuto-check: notes
  • Mistral Vibe CLI Reference

    mistralai/mistral-vibe

    Official

    Reference for Mistral Vibe, the CLI agent it runs inside: config files, env vars, agents, skills, tools, hooks and MCP servers, so the agent can explain and troubleshoot its own setup.

    5.1k GitHub stars~14k tokensUpdated yesterday
    Agent WorkflowsAuto-check: notes
  • Command reference for the omniroute CLI's memory, plugin, marketplace and skills commands: search and manage stored memory, install and scaffold plugins, and find skill packages.

    74k GitHub stars~1k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Superset Plugins and Tools

    superset-sh/superset

    Installs Superset plugins, connects the accounts they need and calls their MCP tools through the credential proxy, without writing tokens to your machine.

    15k GitHub stars~1.3k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Skill Porting

    Prism-Shadow/penguin-harness

    Install skills from external ecosystems into this agent's agentstate/skills/ — resolve Claude Code plugin marketplaces, the Codex plugin repo, skills.sh registry names, GitHub repos, or local…

    2.5k GitHub stars~4.2k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed

Questions about AgentSys Cross-Platform Maintenance

What does AgentSys Cross-Platform Maintenance do?

Maintainer guide to where AgentSys keeps its marketplace, installer, transforms and adapters, and what to run when preparing a release or fixing a platform bug. AgentSys installs the agent-sh plugins on Claude Code, OpenCode, Codex CLI, Cursor and Kiro, and this maintainer skill, for that repository only, works as a map.js` (synced from agent-core, so changes belong there), platform adapters, dev installs, version bumps and generated documentation sections.

When should I use AgentSys Cross-Platform Maintenance?

AgentSys Cross-Platform Maintenance fits situations like: preparing an AgentSys release; checking cross-platform compatibility of the installer or adapters; changing marketplace pins, transforms or adapter generation.

How do I install AgentSys Cross-Platform Maintenance in Claude Code?

Run `npx skills add agent-sh/agentsys --skill maintain-cross-platform -a claude-code`. Or copy the skill folder (meta/skills/maintain-cross-platform in agent-sh/agentsys) into .claude/skills/maintain-cross-platform in your project. Claude Code loads it when a task matches its description.

How do I install AgentSys Cross-Platform Maintenance in Codex?

Run `npx skills add agent-sh/agentsys --skill maintain-cross-platform -a codex`. Or copy the skill folder (meta/skills/maintain-cross-platform in agent-sh/agentsys) into .agents/skills/maintain-cross-platform in your project. Codex loads it when a task matches its description.

Can I use AgentSys Cross-Platform Maintenance 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 agent-sh/agentsys --skill maintain-cross-platform -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/maintain-cross-platform, .gemini/skills/maintain-cross-platform, .github/skills/maintain-cross-platform and .opencode/skills/maintain-cross-platform in your project.

What does AgentSys Cross-Platform Maintenance need to run?

Going by SKILL.md and its folder, AgentSys Cross-Platform Maintenance needs the command-line tools its instructions call (npm, node and npx). Our summary lists: A checkout of the AgentSys repository; GitHub CLI `gh` and Node.js, for the marketplace pinning script.

Does AgentSys Cross-Platform Maintenance access the network?

SKILL.md contains no URLs. Its commands use npm and npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is AgentSys Cross-Platform Maintenance 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 AgentSys Cross-Platform Maintenance use?

AgentSys Cross-Platform Maintenance is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does AgentSys Cross-Platform Maintenance use?

About 1.2k tokens (SKILL.md is roughly 4.9k 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 AgentSys Cross-Platform Maintenance?

Skills that share tags, products or a category with AgentSys Cross-Platform Maintenance: Publish Plugins Version Bump (vinta/hal-9000, 138 stars), Watchmen Setup (firstbatchxyz/watchmen, 296 stars), Mistral Vibe CLI Reference (mistralai/mistral-vibe, 5.1k stars) and OmniRoute Plugins, Skills and Memory CLI (diegosouzapw/OmniRoute, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains AgentSys Cross-Platform Maintenance?

agent-sh (a GitHub organization) maintains it in agent-sh/agentsys, which has 994 GitHub stars. The repository was last updated on October 6, 2026.

Source: agent-sh/agentsys on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.