feat(run-workflow): add run-workflow and run-featured-workflow skills - #268
Open
thagarwal-sjc wants to merge 1 commit into
Open
feat(run-workflow): add run-workflow and run-featured-workflow skills#268thagarwal-sjc wants to merge 1 commit into
thagarwal-sjc wants to merge 1 commit into
Conversation
trieloff
approved these changes
Jul 22, 2026
trieloff
left a comment
Contributor
There was a problem hiding this comment.
The skill.md seems long, this will likely get flagged by Tessl
Ports the run-workflow and run-featured-workflow skills from the run-workflow MCP server repo into a new creative-cloud/run-workflow plugin, adapted to this repo's frontmatter/scaffolding conventions (license field, .claude-plugin/plugin.json, .mcp.json, .tessl-plugin/plugin.json, CODEOWNERS). run-workflow/SKILL.md is split into a slim always-loaded core plus references/ (featured-and-templates, compose, diagnostics, asset-input, alert-rca) to stay under Tessl's recommended SKILL.md token budget. Eval scenarios cover the bare-ID inspect rule, list_actions discovery, and featured workflow routing.
thagarwal-sjc
force-pushed
the
run-workflow-mcp-skills
branch
from
July 23, 2026 16:58
351ed33 to
68217c9
Compare
10 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Ports the
run-workflowandrun-featured-workflowskills from the run-workflow MCP server repo into a newplugins/creative-cloud/run-workflowplugin, adapted to this repo's conventions:origin: internalwithlicense: Apache-2.0+metadata.version/visibility(required by thelicense-fieldCI check)..claude-plugin/plugin.json,.mcp.json(hosted endpointhttps://run-workflow.adobe.io/mcp), and.tessl-plugin/plugin.jsonso the plugin is discoverable and eligible for Tessl evals..github/CODEOWNERSentry for the new path.docs/mcp-server/featured-workflows.md,firefly-api-specs).evals/<scenario>/{task.md,criteria.json}) covering the bare-ID inspect-only rule,list_actions-first discovery, and featured-workflow routing.No existing plugin files were modified beyond the CODEOWNERS addition.
Related Issue
No existing GitHub issue for this — happy to open one first if that's required before merge.
Motivation and Context
Brings the run-workflow MCP skills (Adobe Firefly workflow discovery/compose/run/publish, plus predefined featured workflows) into the shared Adobe skills repo so other agents/users can install them the same way as the other creative-cloud skills.
How Has This Been Tested?
npm run validate(skills-ref spec check) — both skills valid.license-fieldandcodeowners-coverageCI jobs — both pass.tessl review run(quality/security review): run-workflow scored 89%, run-featured-workflow scored 99% (both well above the 50% CONTRIBUTING threshold).tessl eval run(real agent eval, baseline vs. with-skill): average score baseline 39% → with-skill 82%. Two scenarios (bare-ID inspect, discovery-before-answering) show baseline 0-20% vs. skill 100% — the skill fixes clear failure modes. The third scenario (featured-workflow-routing) shows the skill scoring lower than baseline (47% vs 97%) — investigated and this is a known eval-sandbox limitation (no live IMS credential available to authenticate against the real hosted MCP server, so the with-skill run correctly attempted real tool calls and hit 403s, while the unguided baseline "solved" it by writing a self-contained mock implementation instead of calling any real tool). Documented inline inevals/featured-workflow-routing/task.mdunder "Known limitation".Types of changes
Checklist: