flyte-sdk-optimize

A Flyte 2 performance-tuning skill for data and machine-learning workflows. It reviews workflow structure, caching, computing resources, and data movement to suggest improvements.

In plain words
What is it for?
Use it to tune task size, parallel work, cached results, CPU or memory requests, and data formats.
Why use it?
It helps explain why workflows are slow, costly, or unreliable and identifies changes that may improve them.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/flyteorg/flyte-agent-plugins/flyte-sdk-optimize
Any agent
npx skills add flyteorg/flyte-agent-plugins --skill flyte-sdk-optimize
Clone the repo
git clone --depth 1 https://github.com/flyteorg/flyte-agent-plugins

Made for: Claude Code, Codex.

Per session 102 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,340 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00102 $0.02340
Opus 5 $0.00051 $0.01170
Sonnet 5 $0.00020 $0.00468
Haiku 4.5 $0.00010 $0.00234

Measured 2d ago against content hash 236f5664a34e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

flyte-sdk-optimize scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/flyte/skills/flyte-sdk-optimize/SKILL.md · 306 lines

How it starts

The opening of the file, as written. The whole thing — 306 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Flyte 2 SDK Optimize Skill

Optimize Flyte 2 workflows for performance, cost, and reliability.

Grounding References

Resource URL
Official docs https://www.union.ai/docs/v2/flyte
Docs index (LLMs) https://www.union.ai/docs/v2/flyte/llms.txt
SDK API reference https://www.union.ai/docs/v2/union/api-reference/flyte-sdk/
CLI API reference https://www.union.ai/docs/v2/union/api-reference/flyte-cli/
flyte-sdk source https://github.com/flyteorg/flyte-sdk
Example code https://github.com/unionai/unionai-examples
Flyte MCP tools Available via the flyte-cluster and flyte-docs MCP servers

Optimization Strategy Overview

Performance optimization in Flyte follows a hierarchy:

  1. Reduce container overhead — use traces for lightweight ops
  2. Parallelize work — use flyte.map for fan-out
  3. Cache results — use cache="auto" for idempotent tasks
  4. Tune resources — set appropriate CPU/memory/GPU
  5. Optimize data transfer — choose efficient formats, reduce inline I/O
  6. Use reusable containers — shared environments reduce image pull time

Caching

Enable automatic caching

@env.task(cache="auto")  # versioned by function body + inputs
async def preprocess(data: list[str]) -> flyte.io.File:
    ...

Cache key strategies

@env.task(cache="auto")  # default: function body + inputs
async def task_a(data: str) -> flyte.io.File:
    ...

@env.task(cache="override", salt="v2")  # add salt for cache key variation
async def task_b(data: str) -> flyte.io.File:
    ...

@env.task(cache="disable")  # always re-run
async def task_c(data: str) -> flyte.io.File:
    ...

Content-based caching for DataFrames

@env.task(cache="auto")
async def transform(df: flyte.io.DataFrame) -> flyte.io.DataFrame:
    """Cache key includes DataFrame content hash."""
    ...

Ignoring specific inputs in cache key

@env.task(cache="auto", cache_ignore_inputs=["api_key"])
async def fetch_data(api_key: str, url: str) -> flyte.io.File:
    """Don't include api_key in cache key."""
    ...

Read the full file on GitHub · 306 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 306 lines · 102 tokens per session scan A 236f5664a34e

Subscribe to this mod's changes

flyte-sdk-optimize is a skill published in the GitHub repository flyteorg/flyte-agent-plugins (2 stars, last pushed 5d ago), licensed Apache-2.0. It adds 102 tokens to every session and 2,340 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens