Review an exported Adobe Workfront Planning + Fusion scenario blueprint (.json) for performance, speed, resource use, and API call volume, and produce a prioritized optimization self-review.
Install the "wf-planning-fusion-optimizer" agent skill from https://github.com/adobe/skills/tree/main/plugins/workfront/skills/wf-planning-fusion-optimizer into .claude/skills/wf-planning-fusion-optimizer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wf-planning-fusion-optimizer", then confirm the skill loads.
Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
skills CLI
$ npx skills add adobe/skills --skill wf-planning-fusion-optimizer -a codex
Project install goes to .agents/skills/; add -g for ~/.codex/skills/.
Install the "wf-planning-fusion-optimizer" agent skill from https://github.com/adobe/skills/tree/main/plugins/workfront/skills/wf-planning-fusion-optimizer into .agents/skills/wf-planning-fusion-optimizer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wf-planning-fusion-optimizer", then confirm the skill loads.
Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add adobe/skills --skill wf-planning-fusion-optimizer -a cursor
Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.
Install the "wf-planning-fusion-optimizer" agent skill from https://github.com/adobe/skills/tree/main/plugins/workfront/skills/wf-planning-fusion-optimizer into .cursor/skills/wf-planning-fusion-optimizer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wf-planning-fusion-optimizer", then confirm the skill loads.
Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
skills CLI
$ npx skills add adobe/skills --skill wf-planning-fusion-optimizer -a gemini-cli
Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.
Install the "wf-planning-fusion-optimizer" agent skill from https://github.com/adobe/skills/tree/main/plugins/workfront/skills/wf-planning-fusion-optimizer into .gemini/skills/wf-planning-fusion-optimizer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wf-planning-fusion-optimizer", then confirm the skill loads.
Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
skills CLI
$ npx skills add adobe/skills --skill wf-planning-fusion-optimizer -a github-copilot
Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.
Install the "wf-planning-fusion-optimizer" agent skill from https://github.com/adobe/skills/tree/main/plugins/workfront/skills/wf-planning-fusion-optimizer into .github/skills/wf-planning-fusion-optimizer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wf-planning-fusion-optimizer", then confirm the skill loads.
GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add adobe/skills --skill wf-planning-fusion-optimizer -a opencode
OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
Install the "wf-planning-fusion-optimizer" agent skill from https://github.com/adobe/skills/tree/main/plugins/workfront/skills/wf-planning-fusion-optimizer into .opencode/skills/wf-planning-fusion-optimizer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wf-planning-fusion-optimizer", then confirm the skill loads.
OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
Skill name
wf-planning-fusion-optimizer
GitHub stars
197
Token cost
~1.6k tokens
SKILL.md length
784 words
Files
6 (incl. scripts, references)
Skills in repo
66
Repo updated
First seen
Licence
Apache-2.0
At a glance
Review an exported Adobe Workfront Planning + Fusion scenario blueprint (.json) for performance, speed, resource use, and API call volume, and produce a prioritized optimization self-review.
Works in 3 steps: Get the exported blueprint file(s)… → Run → Present the Markdown report as the…
Phrases like make my Fusion scenario faster
SKILL.md covers What this does, Scope: Workfront Planning only, When to use it and How to run it, plus 3 more sections
Runs Python scripts from its folder; calls python
What it does
Wf Planning Fusion Optimizer is an agent skill from adobe/skills. Review an exported Adobe Workfront Planning + Fusion scenario blueprint (.json) for performance, speed, resource use, and API call volume, and produce a prioritized optimization self-review. Use this whenever someone shares a Fusion scenario that uses Workfront Planning (Maestro) and wants it faster, cheaper, or more reliable: slow runs, long execution time, scenario timeouts, high operations consumption, too many API calls, or rate-limit / 429 errors, especially when it works in test but breaks under load or at…
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including scripts and reference files (for example `README.md`, `evals/evals.json` and `references/findings.md`).
It sits in Mobile, covering Rate limiting, Mobile testing and debugging and Database administration. The repository describes itself as: Adobe Skills for Agents. The licence is Apache-2.0.
When your agent uses it
Phrases like make my Fusion scenario faster
Why is this Planning scenario so slow
Reduce operations
Our replication
Example prompts
“make my Fusion scenario faster”
“why is this Planning scenario so slow”
“reduce operations or API calls”
“/wf-planning-fusion-optimizer”
Requirements
Python 3
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
1Get the exported blueprint file(s) (Fusion scenario blueprint export, .json).
2Run
3Present the Markdown report as the deliverable, findings in the order returned
What it can do on your machine
Read from SKILL.md and the folder at commit c8f44ec. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
python
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Wf Planning Fusion Optimizer loads about 1.6k tokens when it runs, and up to ~4.1k if it reads all its reference files. Until then it costs about 232 tokens; SKILL.md has 784 words of instructions outside code blocks.
Always· name and description, kept in context so the agent knows when to use it
~232
When it runs· the whole SKILL.md, loaded when a task matches
~1.6k
With references· SKILL.md plus every file in references/, read only if the agent opens them
~4.1k
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
Download SKILL.mdSave it as .claude/skills/wf-planning-fusion-optimizer/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
name
wf-planning-fusion-optimizer
description
Review an exported Adobe Workfront Planning + Fusion scenario blueprint (.json) for performance, speed, resource use, and API call volume, and produce a prioritized optimization self-review. Use this whenever someone shares a Fusion scenario that uses Workfront Planning (Maestro) and wants it faster, cheaper, or more reliable: slow runs, long execution time, scenario timeouts, high operations consumption, too many API calls, or rate-limit / 429 errors, especially when it works in test but breaks under load or at scale. Trigger for phrases like "make my Fusion scenario faster", "why is this Planning scenario so slow", "reduce operations or API calls", "our replication or sync scenario times out", or "review this blueprint". It is specific to the Workfront Planning connector: if a scenario does not use Planning, it says so and does not apply. Read-only; it does not modify the blueprint.
metadata.category
solution-architecture
license
Apache-2.0
Workfront Planning + Fusion scenario optimizer
What this does
Takes one or more exported Fusion scenario blueprints (.json) that use the Workfront
Planning (Maestro) connector and produces a prioritized, read-only review of what is
hurting the scenario's performance: run time, operations consumed, and API call volume
(which is what drives rate-limit 429s). It reports; it never modifies the blueprint,
and it does not need live workspace access.
The goal is broader than rate limits. Every module execution in Fusion is an
operation, operations cost run time and quota, and loop nesting multiplies them. So the
same structural fixes usually improve speed, cost, and rate-limit headroom at once.
Rate-limit 429s are one symptom of the same underlying inefficiency.
Scope: Workfront Planning only
This reviewer understands the Workfront Planning connector (workfront-maestro
modules). It is not a general Fusion optimizer. If a blueprint has no Planning modules
(for example a Salesforce-to-Slack scenario), the analyzer detects that and returns a
clear "not applicable" result listing the connectors it did find, rather than pretending
to review it. Do not force it onto non-Planning scenarios; tell the user it is
Planning-specific and, if they want, offer general Fusion advice separately without
this skill.
When to use it
Use it whenever a Workfront Planning Fusion scenario is the subject and the concern is
speed, run time, timeouts, operations/quota, cost, reliability, or API limits, even if
the person does not say "optimize" or "429". Replication, sync, and migration
scenarios benefit most because they walk hierarchies and fan out calls, but it applies
to any Planning scenario.
How to run it
Get the exported blueprint file(s) (Fusion scenario blueprint export, .json).
Multiple can be reviewed together.
Present the Markdown report as the deliverable, findings in the order returned
(highest impact first). Do not invent numbers the script did not produce.
How to explain the findings
Anchor everything in one model: call volume and operations are module count times how
often each module runs, and iteration depth is the multiplier. A GET is cheap at the
top of a scenario and expensive several loops deep. Frame each finding in terms of what
it improves: calls, operations, run time, reliability, or throughput. The report labels
each finding with its "Improves:" dimension for this reason.
State one thing early: there is no bulk-read endpoint. Search and single GET are the
only ways to read; bulk exists for writes only. So raising a limit or batching writes
does not fix a read-heavy scenario, only reading fewer and wider does. Lead with the
read findings (F1, F2, F3) for that reason.
Finding codes, their rationale, and recommended fixes are in references/findings.md.
Read it when you need the full explanation for a code; each finding already carries a
one-line recommendation in the report.
Show full SKILL.md (298 more words)Show less
Optional: enrich with a connected Workfront Planning MCP
The static analyzer is the base and needs no connection. But if a Workfront Planning MCP
is connected in the session (most customers running Planning have one), use it to make
the recommendations instance-specific instead of generic. It turns opaque ids in the
blueprint (Rt69e105..., F6a2010...) into real record-type and field names, and, more
importantly, confirms on the live schema that each read-collapse finding is actually
feasible: that the child record type has a filterable reference to its parent, and that
the fields a per-record GET fetches are already carried as lookups the search returns.
That is the check that otherwise needs a pasted sample.
Run python scripts/analyze_blueprint.py <blueprint.json> --ids to list the record-type
and field ids the blueprint references, then resolve them through the Planning MCP. The
full workflow, and one important caveat (the MCP verifies the schema and feasibility, not
the Fusion connector's output nesting), are in references/mcp-enrichment.md. Read it
when a Planning MCP is available. This step is strictly read-only, and if no MCP is
connected, skip it: the static report stands on its own.
What to be careful about
This is a heuristic structural review of the export, not a live measurement. Say so.
Reference and record-type ids differ per workspace instance; concrete fixes must be
resolved against the customer's live schema.
Recommend measuring a representative run before and after, and validating in a sandbox
before promoting.
Do not promise a percentage improvement. Point to where the cost is and let a real
before/after measurement produce the number.
Sleep-based throttling (P1) must be removed in sequence, after the read path is cut,
or bursts can get worse. Explain the ordering rather than just saying "remove it".
With --callmix, shares are usually sampled: treat them as proportions.
Wf Planning Fusion Optimizer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
Wf Planning Fusion Optimizer compared with similar skills
Skill
Stars
Used in
Tokens
Auto-check
Licence
Repo updated
Wf Planning Fusion Optimizer this skilladobe/skills
A skill your agent uses to run instrumented Android tests on Gradle Managed Devices (GMD) — emulators that Gradle provisions, boots, runs tests on, and tears down, so CI and every developer get the…
Design and harden Roblox client/server networking with RemoteEvent, RemoteFunction, and UnreliableRemoteEvent; server authority, argument and Instance validation, rate limits, proximity/ownership…
Control the user's phone — an iPhone through the Mac's iPhone Mirroring window, an Android over adb, or a rented cloud Android: open apps, tap, type, swipe, read the screen.
Scaffolds, implements, deploys and debugs Adobe Runtime actions in App Builder projects, with templates for webhooks, events, database CRUD, sequences and Asset Compute workers.
Launches Chrome with an unpacked extension over CDP, opens its sidepanel, popup or options page, and hands over to cdp-connect for clicks, typing and screenshots.
Detect all languages used on a webpage — both declared (html@lang, hreflang alternate links, nested lang= attributes, meta content-language) and actually present in the body text (Google CLD3 via…
Review an exported Adobe Workfront Planning + Fusion scenario blueprint (.json) for performance, speed, resource use, and API call volume, and produce a prioritized optimization self-review. Wf Planning Fusion Optimizer is an agent skill from adobe/skills.json) for performance, speed, resource use, and API call volume, and produce a prioritized optimization self-review.
When should I use Wf Planning Fusion Optimizer?
Wf Planning Fusion Optimizer fits situations like: phrases like make my Fusion scenario faster; why is this Planning scenario so slow; reduce operations; our replication.
How do I install Wf Planning Fusion Optimizer in Claude Code?
Run `npx skills add adobe/skills --skill wf-planning-fusion-optimizer -a claude-code`. Or copy the skill folder (plugins/workfront/skills/wf-planning-fusion-optimizer in adobe/skills) into .claude/skills/wf-planning-fusion-optimizer in your project. Claude Code loads it when a task matches its description.
How do I install Wf Planning Fusion Optimizer in Codex?
Run `npx skills add adobe/skills --skill wf-planning-fusion-optimizer -a codex`. Or copy the skill folder (plugins/workfront/skills/wf-planning-fusion-optimizer in adobe/skills) into .agents/skills/wf-planning-fusion-optimizer in your project. Codex loads it when a task matches its description.
Can I use Wf Planning Fusion Optimizer in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add adobe/skills --skill wf-planning-fusion-optimizer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/wf-planning-fusion-optimizer, .gemini/skills/wf-planning-fusion-optimizer, .github/skills/wf-planning-fusion-optimizer and .opencode/skills/wf-planning-fusion-optimizer in your project.
What does Wf Planning Fusion Optimizer need to run?
Going by SKILL.md and its folder, Wf Planning Fusion Optimizer needs Python for the scripts in its folder and the command-line tools its instructions call (python). Our summary lists: Python 3.
Does Wf Planning Fusion Optimizer access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Wf Planning Fusion Optimizer safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Wf Planning Fusion Optimizer use?
Wf Planning Fusion Optimizer is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Wf Planning Fusion Optimizer use?
About 1.6k tokens (SKILL.md is roughly 6.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.5k tokens, read only when the agent opens those files.
What are the alternatives to Wf Planning Fusion Optimizer?
Skills that share tags, products or a category with Wf Planning Fusion Optimizer: Running Tests On Gradle Managed Devices (skydoves/android-testing-skills, 334 stars), Upstash Redis (github/awesome-copilot, 40k stars), Discord Bot Architect (davila7/claude-code-templates, 33k stars) and Roblox Networking (gamedev-skills/awesome-gamedev-agent-skills, 1.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Wf Planning Fusion Optimizer?
adobe (a GitHub organization) maintains it in adobe/skills, which has 197 GitHub stars. The repository holds 66 skills in this directory. The repository was last updated on October 10, 2026.
Source: adobe/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.