Skill Distribution Status

Reference doc for tracking skill submissions across all agent platforms. Last updated: 2026-03-07

Distribution Overview

All three skills use the Agent Skills standard (SKILL.md with name/description YAML frontmatter). This format is natively compatible with: GitHub Copilot, Claude Code, OpenAI Codex, OpenClaw, Gemini CLI, OpenHands, Goose, Amp, and more.

Master Status Table

Channel	Audience	`power-automate-mcp`	`power-automate-debug`	`power-automate-build`
awesome-copilot	GitHub Copilot	✅ PR #896 merged (as `flowstudio-power-automate-mcp`)	⏳ PR #899 + plugin — awaiting merge	⏳ PR #899 + plugin — awaiting merge
ClawHub (OpenClaw)	240k monthly visitors	✅ v1.1.0 published (metadata fix)	✅ v1.1.0 published (metadata fix)	✅ v1.1.0 published (metadata fix)
anthropics/skills	Claude Code (85.2k ⭐, 9k forks)	⏳ PR #555 awaiting review	⏳ PR #555 awaiting review	⏳ PR #555 awaiting review
openai/skills	Codex (11.2k ⭐, 622 forks)	⏳ PR #231 awaiting review	⏳ PR #231 awaiting review	⏳ PR #231 awaiting review
Smithery (skills)	125k+ skills, 4.8k+ MCPs	✅ Published (flowstudio/power-automate-mcp)	✅ Published (flowstudio/power-automate-debug)	✅ Published (flowstudio/power-automate-build)
Smithery (MCP server)	4.8k+ MCPs	⚠️ Created — scan blocked by Cloudflare	N/A (server)	N/A (server)
Official MCP Registry	All MCP clients	Not yet published	N/A (skill, not server)	N/A (skill, not server)

1. GitHub Copilot — awesome-copilot

Status: ✅ Merged

Fork: ninihen1/awesome-copilot → cloned to ~/GitHub/awesome-copilot
Branch: add-power-automate-mcp off staged
PR: #896 — merged by @aaronpowell on 2026-03-06
Skill folder: skills/flowstudio-power-automate-mcp/

What happened

Initial PR submitted as power-automate-mcp (commit 9c81ea6)
@aaronpowell (code owner) requested: "have FlowStudio as part of the name"
Copilot AI posted 8 review comments on response shapes, syntax, User-Agent, docs
All 8 comments verified against live FlowStudio MCP server using real API calls
Renamed to flowstudio-power-automate-mcp, applied all valid fixes (commit 0962c47)
Posted review reply comment with verdict table for each Copilot suggestion
Validation: npm run skill:validate ✅ (208 skills valid), npm run build ✅

Status: ⏳ PR #899 awaiting merge (all review comments addressed + plugin added)

Fork: ninihen1/awesome-copilot → cloned to ~/GitHub/awesome-copilot
Branch: add-power-automate-debug-build off staged
PR: #899 — submitted 2026-03-06
Skill folders: skills/flowstudio-power-automate-debug/, skills/flowstudio-power-automate-build/
Plugin: plugins/flowstudio-power-automate/ (bundles all 3 skills)
CI: All 4 checks passing (line-endings, materialized-files, codespell, validate-readme)
Review: @aaronpowell's CHANGES_REQUESTED was auto-dismissed after fixes
Branches cleaned: only add-power-automate-debug-build, main, staged remain

Key Details

PRs target the staged branch (not main)
Validate: npm run skill:validate then npm run build
Fork: ~/GitHub/awesome-copilot (origin = ninihen1, upstream = github)

2. OpenClaw — ClawHub

Status: ✅ All 3 skills published (v1.1.0)

ClawHub (clawhub.ai): 13,729 skills, 240k monthly visitors
awesome-openclaw-skills (VoltAgent/awesome-openclaw-skills): 28.5k stars curated list

What happened

v1.0.0 uploaded manually via web UI on 2026-03-06
Security scan flagged mcp and build as "Suspicious (medium confidence)" — missing credential declarations
Added metadata.openclaw to all 3 SKILL.md frontmatters declaring FLOWSTUDIO_MCP_TOKEN env var
Published v1.1.0 via clawhub CLI on 2026-03-07
debug skill already passed as "Benign (high confidence)"

CLI Setup

npx clawhub login --token "<token>" --no-browser
npx clawhub publish skills/power-automate-mcp --version 1.1.0
npx clawhub publish skills/power-automate-debug --version 1.1.0
npx clawhub publish skills/power-automate-build --version 1.1.0

Installation by Users

npx clawhub@latest install power-automate-mcp

awesome-openclaw-skills Listing (Deferred)

PR to VoltAgent/awesome-openclaw-skills once skills get community traction on ClawHub
Category: DevOps & Cloud (408 skills)
⚠️ Requires proven adoption — don't submit until download metrics warrant it

3. Claude Code — anthropics/skills

Status: ⏳ PR #555 submitted — awaiting review

Repo: anthropics/skills (85.2k ⭐, 9k forks, 267 open PRs)
Fork: ninihen1/skills → cloned to ~/GitHub/skills
Branch: add-flowstudio-power-automate-skills
PR: #555 — submitted 2026-03-07
Skill folders (with flowstudio- prefix per convention):
- skills/flowstudio-power-automate-mcp/
- skills/flowstudio-power-automate-debug/
- skills/flowstudio-power-automate-build/
15 files total (3 SKILL.md + 12 reference files)

How to Submit

Fork anthropics/skills
Add skill folders under skills/:
- skills/power-automate-mcp/SKILL.md + references/
- skills/power-automate-debug/SKILL.md + references/
- skills/power-automate-build/SKILL.md + references/
PR to main

# Fork & clone
gh repo fork anthropics/skills --clone
cd skills

# Copy all 3 skills
for skill in power-automate-mcp power-automate-debug power-automate-build; do
  mkdir -p "skills/$skill/references"
  cp ~/GitHub/"FlowStudio MCP"/skills/$skill/SKILL.md "skills/$skill/"
  cp ~/GitHub/"FlowStudio MCP"/skills/$skill/references/* "skills/$skill/references/" 2>/dev/null
done

# Commit & PR
git checkout -b add-flowstudio-skills
git add skills/power-automate-*
git commit -m "feat: add FlowStudio Power Automate skills (mcp, debug, build)"
git push origin add-flowstudio-skills
gh pr create --base main --title "feat: add FlowStudio Power Automate skills" \
  --body "Three skills for Power Automate cloud flow management via FlowStudio MCP server.
- **power-automate-mcp**: Core connection & CRUD operations
- **power-automate-debug**: Debug workflow for failed flow runs
- **power-automate-build**: Build & deploy flows from natural language

Requires FlowStudio MCP subscription: https://flowstudio.app"

Users Connect FlowStudio MCP in Claude Code

claude mcp add --transport http flowstudio https://mcp.flowstudio.app/mcp \
  --header "x-api-key: <JWT>"

Notes

267 open PRs suggest review backlog — submit early, expect wait
All 3 skills can go in one PR since anthropics/skills has no tier system

4. OpenAI Codex — openai/skills

Status: ⏳ PR #231 submitted — awaiting review

Repo: openai/skills (11.2k ⭐, 622 forks, 87 open PRs)
Fork: ninihen1/openai-skills (renamed to avoid collision with anthropics fork)
Branch: add-flowstudio-power-automate-skills
PR: #231 — submitted 2026-03-07
Skill folders under skills/.experimental/ (with flowstudio- prefix):
- skills/.experimental/flowstudio-power-automate-mcp/
- skills/.experimental/flowstudio-power-automate-debug/
- skills/.experimental/flowstudio-power-automate-build/
Skills organized by tiers: .system (built-in), .curated (vetted), .experimental (community)

How to Submit

Fork openai/skills
Add skill folders under skills/.experimental/:
- skills/.experimental/power-automate-mcp/SKILL.md + references/
- skills/.experimental/power-automate-debug/SKILL.md + references/
- skills/.experimental/power-automate-build/SKILL.md + references/
PR to main

# Fork & clone
gh repo fork openai/skills --clone
cd skills

# Copy all 3 skills into .experimental
for skill in power-automate-mcp power-automate-debug power-automate-build; do
  mkdir -p "skills/.experimental/$skill/references"
  cp ~/GitHub/"FlowStudio MCP"/skills/$skill/SKILL.md "skills/.experimental/$skill/"
  cp ~/GitHub/"FlowStudio MCP"/skills/$skill/references/* "skills/.experimental/$skill/references/" 2>/dev/null
done

# Commit & PR
git checkout -b add-flowstudio-skills
git add skills/.experimental/power-automate-*
git commit -m "feat: add FlowStudio Power Automate skills"
git push origin add-flowstudio-skills
gh pr create --base main --title "feat: add FlowStudio Power Automate skills (.experimental)" \
  --body "Three experimental skills for Power Automate cloud flow management via FlowStudio MCP.
- **power-automate-mcp**: Core connection & CRUD operations
- **power-automate-debug**: Debug workflow for failed flow runs
- **power-automate-build**: Build & deploy flows from natural language

Requires FlowStudio MCP subscription: https://flowstudio.app"

Users Connect FlowStudio MCP in Codex

In ~/.codex/config.toml:

[mcp_servers.flowstudio]
url = "https://mcp.flowstudio.app/mcp"

[mcp_servers.flowstudio.http_headers]
x-api-key = "<JWT>"

Users Install Skills

$skill-installer install the power-automate-mcp skill from the .experimental folder

5. Smithery

Status: ✅ All 3 skills published

smithery.ai — 4,824+ MCP servers, 125,300+ skills
Namespace: flowstudio (created 2026-03-07)
Skills published via REST API: PUT https://api.smithery.ai/skills/{namespace}/{slug}
All skills link to GitHub repo subdirs and auto-sync from SKILL.md

Published Skills

Skill	Smithery URL
`power-automate-mcp`	flowstudio/power-automate-mcp
`power-automate-debug`	flowstudio/power-automate-debug
`power-automate-build`	flowstudio/power-automate-build

CLI Publishing Commands (for reference)

# Authenticate
export SMITHERY_API_KEY="<api-key>"

# Publish/update a skill (idempotent PUT)
curl -X PUT "https://api.smithery.ai/skills/flowstudio/power-automate-mcp" \
  -H "Authorization: Bearer $SMITHERY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"gitUrl": "https://github.com/ninihen1/power-automate-mcp-skills/tree/master/skills/power-automate-mcp"}'

Installation by Users

npx smithery skill add flowstudio/power-automate-mcp

MCP Server Publishing — ⚠️ Created but scan blocked by Cloudflare

Server created: flowstudio/flowstudio-mcp
Proxy URL: https://flowstudio-mcp--flowstudio.run.tools
Config schema: smithery-config-schema.json (declares x-api-key via x-from: header:x-api-key)
Description: ✅ Updated via PATCH API
Scan failed: Cloudflare Bot Fight Mode blocks SmitheryBot/1.0 User-Agent, returning HTML instead of JSON
Server page shows "No capabilities found" / "No deployments found"

To fix (requires FlowStudio server-side change — pick one):

Whitelist SmitheryBot UA in Cloudflare WAF: Security > WAF > Tools > IP Access Rules, or create skip rule for (http.user_agent contains "SmitheryBot")

Serve /.well-known/mcp/server-card.json endpoint to bypass scanning entirely:

{
  "serverInfo": { "name": "FlowStudio MCP", "version": "1.0.0" },
  "authentication": { "required": true, "schemes": ["apiKey"] },
  "tools": [
    { "name": "list_live_flows", "description": "List flows in an environment", "inputSchema": { "type": "object" } },
    { "name": "get_live_flow", "description": "Fetch complete flow definition", "inputSchema": { "type": "object" } }
  ]
}

Disable Bot Fight Mode in Cloudflare (Security > Bots)

After Cloudflare fix, re-publish:

SMITHERY_API_KEY="<key>" npx smithery mcp publish "https://mcp.flowstudio.app/mcp" \
  -n flowstudio/flowstudio-mcp --config-schema smithery-config-schema.json

6. Official MCP Registry

Status: Requires investigation — may not be compatible yet

registry.modelcontextprotocol.io — canonical MCP server directory (currently in preview)
Publishes the FlowStudio MCP server itself, not individual skills
Uses mcp-publisher CLI tool + server.json metadata file

Compatibility Considerations

Registry expects either an npm package (stdio transport) or a remote server (Streamable HTTP/SSE)
FlowStudio MCP uses JSON-RPC over HTTP with x-api-key auth — this maps to the remotes approach
The headers property in server.json supports custom headers like X-API-Key
Server name: io.github.ninihen1/flowstudio-mcp (GitHub auth prefix)
Question: Does FlowStudio MCP support Streamable HTTP transport, or only JSON-RPC POST? The registry expects MCP protocol compliance.

How to Publish (if compatible)

# Install mcp-publisher
curl -L "https://github.com/modelcontextprotocol/registry/releases/latest/download/mcp-publisher_$(uname -s | tr '[:upper:]' '[:lower:]')_$(uname -m | sed 's/x86_64/amd64/;s/aarch64/arm64/').tar.gz" | tar xz mcp-publisher
sudo mv mcp-publisher /usr/local/bin/

# Authenticate
mcp-publisher login github

# Create server.json
cat > server.json << 'EOF'
{
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "name": "io.github.ninihen1/flowstudio-mcp",
  "title": "FlowStudio MCP",
  "description": "Read, modify, deploy, debug, and monitor Power Automate cloud flows via MCP",
  "version": "1.0.0",
  "repository": {
    "url": "https://github.com/ninihen1/FlowStudio-MCP",
    "source": "github"
  },
  "remotes": [
    {
      "type": "streamable-http",
      "url": "https://mcp.flowstudio.app/mcp",
      "headers": [
        {
          "name": "x-api-key",
          "description": "FlowStudio workspace JWT (get from https://flowstudio.app)",
          "isRequired": true,
          "isSecret": true
        }
      ]
    }
  ]
}
EOF

# Publish
mcp-publisher publish

Priority & Execution Order

Priority	Action	Effort	Status
1	✅ awesome-copilot PR #896	Done	✅ Merged
1b	awesome-copilot: debug + build + plugin	Done	⏳ PR #899 awaiting merge
2	✅ Publish 3 skills to ClawHub	Done	✅ v1.1.0 (metadata fix)
3	✅ PR to anthropics/skills (all 3 skills)	Done	⏳ PR #555 awaiting review
4	✅ PR to openai/skills (all 3 skills)	Done	⏳ PR #231 awaiting review
5	✅ Publish 3 skills to Smithery	Done	✅ Published (namespace: flowstudio)
6	⚠️ Publish MCP server to Smithery	Done	⚠️ Created — scan blocked by Cloudflare Bot Fight Mode
7	Publish to MCP Registry	Medium — needs server.json, verify transport	Investigate
8	PR to awesome-openclaw-skills	Low — needs traction first	Deferred

Key Details to Remember

All skills use Agent Skills standard format (SKILL.md with name/description frontmatter)
In awesome-copilot, the skill is named flowstudio-power-automate-mcp (renamed per reviewer)
In all other platforms, skills keep original names: power-automate-mcp, -debug, -build
Auth in all skills uses x-api-key header, never Bearer
User-Agent FlowStudio-MCP/1.0 required in all HTTP examples (Cloudflare blocks empty UA)
PowerShell examples must include -UseBasicParsing
awesome-copilot PRs target the staged branch; anthropics/skills and openai/skills target main
The skills/*/examples/ directory in FlowStudio MCP is gitignored (tenant-specific data)

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Skill Distribution Status

Distribution Overview

Master Status Table

1. GitHub Copilot — awesome-copilot

Status: ✅ Merged

What happened

Status: ⏳ PR #899 awaiting merge (all review comments addressed + plugin added)

Key Details

2. OpenClaw — ClawHub

Status: ✅ All 3 skills published (v1.1.0)

What happened

CLI Setup

Installation by Users

awesome-openclaw-skills Listing (Deferred)

3. Claude Code — anthropics/skills

Status: ⏳ PR #555 submitted — awaiting review

How to Submit

Users Connect FlowStudio MCP in Claude Code

Notes

4. OpenAI Codex — openai/skills

Status: ⏳ PR #231 submitted — awaiting review

How to Submit

Users Connect FlowStudio MCP in Codex

Users Install Skills

5. Smithery

Status: ✅ All 3 skills published

Published Skills

CLI Publishing Commands (for reference)

Installation by Users

MCP Server Publishing — ⚠️ Created but scan blocked by Cloudflare

6. Official MCP Registry

Status: Requires investigation — may not be compatible yet

Compatibility Considerations

How to Publish (if compatible)

Priority & Execution Order

Key Details to Remember

FilesExpand file tree

SUBMISSION-STATUS.md

Latest commit

History

SUBMISSION-STATUS.md

File metadata and controls

Skill Distribution Status

Distribution Overview

Master Status Table

1. GitHub Copilot — awesome-copilot

Status: ✅ Merged

What happened

Status: ⏳ PR #899 awaiting merge (all review comments addressed + plugin added)

Key Details

2. OpenClaw — ClawHub

Status: ✅ All 3 skills published (v1.1.0)

What happened

CLI Setup

Installation by Users

awesome-openclaw-skills Listing (Deferred)

3. Claude Code — anthropics/skills

Status: ⏳ PR #555 submitted — awaiting review

How to Submit

Users Connect FlowStudio MCP in Claude Code

Notes

4. OpenAI Codex — openai/skills

Status: ⏳ PR #231 submitted — awaiting review

How to Submit

Users Connect FlowStudio MCP in Codex

Users Install Skills

5. Smithery

Status: ✅ All 3 skills published

Published Skills

CLI Publishing Commands (for reference)

Installation by Users

MCP Server Publishing — ⚠️ Created but scan blocked by Cloudflare

6. Official MCP Registry

Status: Requires investigation — may not be compatible yet

Compatibility Considerations

How to Publish (if compatible)

Priority & Execution Order

Key Details to Remember