maintain-cross-platform
Use when preparing releases, validating cross-platform compatibility, or updating installation infrastructure. Meta-skill for maintaining AgentSys's 3-platform architecture.
Profile →npx skills add agent-sh/agentsys --skill maintain-cross-platform --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
The skill expresses a comprehensive, local framework for keeping AgentSys's cross-platform setup aligned across Claude Code, OpenCode, and Codex CLI. It defines rules to ensure three platforms work, validates before pushes with six validators, and enforces alignment of 11 version fields across package.json and 10 plugin.json files. It documents platform-specific configurations, component locations, install paths, and transformation rules used by the installer to maintain consistency across environments. It also prescribes updating the skill when misalignments or automation opportunities are found.
How it works
- Establishes critical rules: three platforms must work, pre-push validation with six validators, and version fields must be aligned across 11 files.
- Specifies a platform differences matrix for configuration formats, state directories, command prefixes, and project instruction files across Claude Code, OpenCode, and Codex CLI.
- Details component locations (commands, agents, skills, hooks) per platform and install/config locations for each platform in this repository.
- Lists validation scripts run by CI and pre-push (validate-plugins.js, validate-cross-platform.js, validate-repo-consistency.js, check-hardcoded-paths.js, validate-counts.js, validate-cross-platform-docs.js).
- Describes the transformation rules used by the installer (bin/cli.js) when adapting content for OpenCode and Codex, including how tools become permissions, model stripping, and path substitutions.
- Provides a release workflow section detailing how to bump versions, update CHANGELOG, and run validations and tests during RC and production releases.
When to use it
Use this skill when preparing releases, validating cross-platform compatibility, or updating installation infrastructure. It applies to maintaining AgentSys's 3-platform architecture and is scoped to this repository only.
What it can touch
- Files and paths referenced in the platform install and transformation steps (e.g., bin/cli.js, scripts/, adapters/, plugins/*/, mcp-server, and config files) as described in the transformation mappings and validation scripts. The skill enumerates commands, paths, and tooling names exactly as described in its instructions.
Caveats
- Requires alignment of 11 version fields across multiple files.
- Validation relies on CI and pre-push hooks; misalignment may block pushes or releases.
- Transformation rules assume three platforms; behavior may differ if a platform changes its toolset or file paths.
# Maintain Cross-Platform Architecture **Purpose:** Comprehensive knowledge of AgentSys's cross-platform infrastructure for release preparation, validation, and maintenance. **Scope:** LOCAL skill for this repository only. Contains specific file locations, transformation rules, and automation patterns for maintaining Claude Code + OpenCode + Codex CLI compatibility. ## Critical Rules 1. **3 platforms MUST work** - Claude Code, OpenCode, Codex CLI. No exceptions. 2. **Validation before every push** - Pre-push hook runs 6 validators automatically. 3. **All version fields must align** - 11 files total (package.json + 10 plugin.json files). 4. **Documentation must be accurate** - Counts, paths, and platform references validated by CI. 5. **Update this skill** - If you find misalignments or automation opportunities, update this file. --- ## Platform Differences (The Complete Matrix) ### Configuration | Aspect | Claude Code | OpenCode | Codex CLI | |--------|-------------|----------|-----------| | **Config format** | JSON | JSON/JSONC | TOML | | **Config location** | `~/.claude/settings.json` | `~/.config/opencode/opencode.json` | `~/.codex/config.toml` | | **State directory** | `.claude
- Critical Rules
- Platform Differences (The Complete Matrix)
- Configuration
- Component Locations
- Install Locations (This Repo)
- Frontmatter Differences
- File Locations (This Repository)
- Installation Infrastructure
- Validation Scripts (All in CI + Pre-Push)
- Transformation Mappings (bin/cli.js)
- Version Fields (11 Files Total)
- Release Process (RC and Production)
- RC Release (3.X.0-rc.N)
- Production Release (3.X.0)
grep -r '"version"' package.json plugins/*/.claude-plugin/plugin.json .claude-plugin/plugin.json
Bump to RC version in ALL 11 files
package.json
npm version $NEW_VERSION --no-git-tag-version
All plugin.json files (9 plugins + root)
find . -name "plugin.json" -path "*/.claude-plugin/*" -exec sed -i '' "s/\"version\": \".*\"/\"version\": \"$NEW_VERSION\"/" {} \;
mcp-server/index.js
sed -i '' "s/version: '.*'/version: '$NEW_VERSION'/" mcp-server/index.js
npm run validate # All 6 validators
npm test # All testsWhat does the maintain-cross-platform skill do?
Use when preparing releases, validating cross-platform compatibility, or updating installation infrastructure. Meta-skill for maintaining AgentSys's 3-platform architecture.
How do I install it?
Run `npx skills add agent-sh/agentsys --skill maintain-cross-platform --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From agent-sh/agentsys, a repository with 923 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.