This release has been yanked by its maintainers, and will be ignored by installers, except when explicitly specified.
Consider using release 0.0.8 instead.
flyte-skills
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 for Flyte,
packaged for every agent harness — plus two MCP servers (flyte-docs, flyte-cluster)
for harnesses that read the bundled .mcp.json.
flyte-skillsandflyte-agent-pluginsare identical mirrors published from the same repo at the same version. Install whichever name you prefer — installing both just gives you two copies of the same skills.
Install
uvx flyte-skills install
Or pip install flyte-skills and then flyte-skills install.
The CLI auto-detects which harnesses are set up on the machine and copies the skills into each one's skills directory:
| Harness | User-level directory | Project-level (--project) |
|---|---|---|
| Claude Code | ~/.claude/skills/ |
.claude/skills/ |
| Codex CLI | ~/.agents/skills/ |
.agents/skills/ |
| opencode | ~/.config/opencode/skills/ |
.opencode/skills/ |
| pi | ~/.pi/agent/skills/ |
— |
flyte-skills install --target claude --target codex # pick harnesses explicitly
flyte-skills install --dir ./somewhere/skills # arbitrary directory
flyte-skills install --project # this repo only
flyte-skills install --dry-run # show what would change
flyte-skills uninstall # remove them again
flyte-skills list # list bundled skills
flyte-skills path # print the bundled plugin root
The MCP servers are not installed by the CLI — only the skills are. Harnesses
that consume the whole plugin (Claude Code, Codex) pick the servers up from
.mcp.json automatically.
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, Hermes, opencode, and pi instructions, the full skill list, and MCP server details.
License
Apache-2.0
Release files for flyte-skills 0.6.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 | |
|---|---|---|---|
| flyte_skills-0.6.0.tar.gz | 121.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| flyte_skills-0.6.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 266.5 kB
Release files / flyte_skills-0.6.0.tar.gz
| Download URL | flyte_skills-0.6.0.tar.gz |
|---|---|
| Size | 121.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e14fef8ed2ad82d93bef4819528f77eb664215315e0aa165f5410c486f42d8d6
|
|
BLAKE2b-256 checksum How to use checksums |
e864d873c49fe7ba346cd755fc5013d40486031f5292d73ba211cfb305c13d93
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 31, 2026.
Transparency logRelease files / flyte_skills-0.6.0-py3-none-any.whl
| Download URL | flyte_skills-0.6.0-py3-none-any.whl |
|---|---|
| Size | 145.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
92f4918a7695ff30b1986016789f00d70b18356dd332300afd1f4e5766a116e2
|
|
BLAKE2b-256 checksum How to use checksums |
fcccb79589626bf1fd2627f7560c7933b1b430c33c6f039a1e8511489154703f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 31, 2026.
Transparency log