Metadata-Version: 2.5
Name: union-skills
Version: 0.0.3
Summary: Deploy and operate Union.ai. Self-serve setup on AWS end to end: provision EKS, S3, ECR and IAM, connect your cluster, run tracked workflows locally, and debug data-plane health.
Project-URL: Homepage, https://github.com/unionai-oss/union-skills
Project-URL: Repository, https://github.com/unionai-oss/union-skills
Project-URL: Issues, https://github.com/unionai-oss/union-skills/issues
Author: unionai-oss
License-Expression: Apache-2.0
License-File: LICENSE
Keywords: agent-skills,aws,claude-code,claude-code-plugin,codex,eks,flyte,mcp,union,unionai,workflow-orchestration
Classifier: Development Status :: 4 - Beta
Classifier: Intended Audience :: Developers
Classifier: Programming Language :: Python :: 3
Classifier: Topic :: Software Development :: Code Generators
Classifier: Topic :: System :: Installation/Setup
Requires-Python: >=3.9
Description-Content-Type: text/markdown

# union-skills

Deploy and operate Union.ai. Self-serve setup on AWS end to end: provision EKS, S3, ECR and IAM, connect your cluster, run tracked workflows locally, and debug data-plane health.

5 [Agent Skills](https://agentskills.io) for [Union.ai](https://www.union.ai),
packaged for every agent harness — plus two MCP servers (`flyte-docs`, `flyte-cluster`) for
harnesses that read the bundled `.mcp.json`.

The skills walk an agent and a human through Union.ai
[self-serve setup](https://www.union.ai/docs/v2/union/deployment/self-serve/) together:
provisioning AWS, connecting a cluster, running workflows, and debugging a data plane that
will not come up. Every command that creates a cloud resource is an explicit approval gate,
and every value that has to cross between the terminal and the Union.ai UI is marked as a
hand-off.

## Install

```bash
uvx union-skills install
```

Or `pip install union-skills` and then `union-skills install`.

The CLI auto-detects which harnesses are set up on the machine and copies the skills into
each one's skills directory:

| `--target` | User-level directory | Project-level (`--project`) | Read by |
|---|---|---|---|
| `agents` | `~/.agents/skills/` | `.agents/skills/` | Codex, Hermes (project), any harness following the convention |
| `claude` | `~/.claude/skills/` | `.claude/skills/` | Claude Code |
| `hermes` | `~/.hermes/skills/` | `.hermes/skills/` | Hermes |
| `opencode` | `~/.config/opencode/skills/` | `.opencode/skills/` | opencode |
| `pi` | `~/.pi/agent/skills/` | — | pi |

```bash
union-skills install --target claude --target hermes  # pick harnesses explicitly
union-skills install --target agents                  # the cross-harness standard location
union-skills install --dir ./somewhere/skills         # arbitrary directory
union-skills install --project                        # this repo only
union-skills install --dry-run                        # show what would change
union-skills uninstall                                # remove them again
union-skills list                                     # list bundled skills
union-skills path                                     # print the bundled plugin root
```

## MCP servers

`union-skills install` writes skills only. `union-skills mcp install` adds the two bundled MCP
servers as well, by driving `claude mcp add-json` / `codex mcp add` rather than editing
config files — so it needs one of those CLIs on your PATH:

```bash
union-skills mcp list                     # what would be added
union-skills mcp install --dry-run        # print the commands, change nothing
union-skills mcp install                  # add them
union-skills mcp uninstall                # remove them again
```

These are tools the agent can call, not inert markdown: `flyte-docs` sends search queries to
a Union-operated endpoint, and `flyte-cluster` gets control-plane access to your Union.ai
organization (which also needs `uv` and a login). Union.ai uses the same `flyte` SDK and CLI
as open-source Flyte, which is why the servers carry those names.

Harnesses that consume the whole plugin (Claude Code, Codex) pick the servers up from
`.mcp.json` automatically and need none of this.

## Native install paths

If you'd rather install from git than from a registry, the repo is a plugin marketplace in
its own right:

```
/plugin marketplace add unionai-oss/union-skills
/plugin install union@union-skills
```

See [the repository README](https://github.com/unionai-oss/union-skills#readme) for Codex, Hermes, opencode and pi
instructions, the full skill list, and MCP server details.

## License

Apache-2.0
