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.
23 Agent Skills for Flyte,
packaged for every agent harness — plus two MCP servers (flyte-docs, flyte-cluster)
for harnesses that read the bundled .mcp.json.
flyte-agent-pluginsandflyte-skillsare published from the same repo at the same version and carry the same 23 skills. They differ in one thing: onlyflyte-agent-pluginsships themcpsubcommand for the bundled MCP servers. Installing both just gives you two copies of the same skills.
Install
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 |
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:
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
For Google Antigravity, install the whole plugin — skills and both servers — straight from this package:
agy plugin install "$(flyte-agent-plugins path)"
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, Antigravity) pick the servers up from the
bundled config 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 for Codex, Antigravity, Hermes, opencode, and pi instructions, the full skill list, and MCP server details.
License
Apache-2.0
Metadata
Release files for flyte-agent-plugins 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| flyte_agent_plugins-0.1.0.tar.gz | 155.5 kB | With provenance | Details for flyte_agent_plugins-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| flyte_agent_plugins-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for flyte_agent_plugins-0.1.0-py3-none-any.whl |
Total release size: 341.1 kB
Release files / flyte_agent_plugins-0.1.0.tar.gz
| Download URL | flyte_agent_plugins-0.1.0.tar.gz |
|---|---|
| Size | 155.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
91e29890e48b82287d8c69e9d39fcd5353af6ee70aff49513e541e319f0dbf7e
|
|
BLAKE2b-256 checksum How to use checksums |
c5afcdd5c4e0b5298cfedd06aa38c7b14eba7a22f7adb7b364192c7722afcc0b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 26, 2026.
Transparency logRelease files / flyte_agent_plugins-0.1.0-py3-none-any.whl
| Download URL | flyte_agent_plugins-0.1.0-py3-none-any.whl |
|---|---|
| Size | 185.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
862c99f1814d9dbef9003d313864f5bd63f42e31ff27eb593b582700ca41c3a4
|
|
BLAKE2b-256 checksum How to use checksums |
108598ca0720ebdc2ac7013553b556d573a7da21b8bbebab2d653e6839bc99fe
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 26, 2026.
Transparency logSecurity for flyte-agent-plugins 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for flyte_agent_plugins-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 26, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.