Metadata-Version: 2.5
Name: flyte-agent-plugins
Version: 0.0.8
Summary: Work with Flyte 2. Deploy Flyte on AWS or kind, author and run workflows, apps, agents, data, and ML workloads with the SDK, and operate your cluster through bundled MCP servers.
Project-URL: Homepage, https://github.com/flyteorg/flyte-agent-plugins
Project-URL: Repository, https://github.com/flyteorg/flyte-agent-plugins
Project-URL: Issues, https://github.com/flyteorg/flyte-agent-plugins/issues
Author: flyteorg
License-Expression: Apache-2.0
License-File: LICENSE
Keywords: agent-skills,claude-code,claude-code-plugin,codex,flyte,mcp,workflow-orchestration
Classifier: Development Status :: 4 - Beta
Classifier: Intended Audience :: Developers
Classifier: Programming Language :: Python :: 3
Classifier: Topic :: Software Development :: Code Generators
Requires-Python: >=3.9
Description-Content-Type: text/markdown

# flyte-agent-plugins

Work with Flyte 2. Deploy Flyte on AWS or kind, author and run workflows, apps, agents, data, and ML workloads with the SDK, and operate your cluster through bundled MCP servers.

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

> `flyte-agent-plugins` and `flyte-skills` are published from [the same repo](https://github.com/flyteorg/flyte-agent-plugins)
> at the same version and carry the same 21 skills. They differ in one
> thing: only `flyte-agent-plugins` ships the `mcp` subcommand for the bundled MCP
> servers. Installing both just gives you two copies of the same skills.

## Install

```bash
uvx flyte-agent-plugins install
```

Or `pip install flyte-agent-plugins` and then `flyte-agent-plugins 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
flyte-agent-plugins install --target claude --target hermes  # pick harnesses explicitly
flyte-agent-plugins install --target agents                  # the cross-harness standard location
flyte-agent-plugins install --dir ./somewhere/skills         # arbitrary directory
flyte-agent-plugins install --project                        # this repo only
flyte-agent-plugins install --dry-run                        # show what would change
flyte-agent-plugins uninstall                                # remove them again
flyte-agent-plugins list                                     # list bundled skills
flyte-agent-plugins path                                     # print the bundled plugin root
```

`flyte-agent-plugins install` writes skills only. `flyte-agent-plugins 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
flyte-agent-plugins mcp list                     # what would be added
flyte-agent-plugins mcp install --dry-run        # print the commands, change nothing
flyte-agent-plugins mcp install                  # add them
flyte-agent-plugins 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 cluster (which also needs `uv` and a Flyte login). 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 flyteorg/flyte-agent-plugins
/plugin install flyte@flyte-agent-plugins
```

See [the repository README](https://github.com/flyteorg/flyte-agent-plugins#readme) for Codex, Hermes, opencode, and
pi instructions, the full skill list, and MCP server details.

## License

Apache-2.0
