[github-actions]

Summary

• add mobile-use in plugins/external.json
• regenerate marketplace outputs for the approved external plugin submission
• source repository: microsoft/mobile-use
• approved from [External Plugin]: mobile-use #6278

Validation

• npm run build

[Copilot]

🔵 Needs a closer look

Because the plugin controls real Android devices and its paired-wireless ADB behavior remains unverified, maintainer review of the pinned source and operational safety is still needed.

No open issues 🎉

What changed in this PR

Adds the approved microsoft/mobile-use external plugin to the Awesome Copilot marketplace, with generated marketplace metadata pinned to an immutable source commit.

Changes:

• Registers mobile-use in plugins/external.json with repository, metadata, licensing, keywords, and source SHA.
• Regenerates .github/plugin/marketplace.json with the corresponding marketplace entry.
• Preserves synchronization between the catalog and generated marketplace output.

A nit remains for plugins/external.json: the pinned source README still states that the marketplace listing is unavailable. The upstream README should be updated and the listing repinned to a newer immutable commit.

File	Description
plugins/​external.json	Adds the pinned mobile-use external plugin registration. A stale README notice remains in the pinned source revision (nit).
.github/​plugin/​marketplace.json	Adds the generated marketplace entry for mobile-use.

_{Review effort: Lite (auto)}

[github-actions]

🚦 Submission status: ⏳ Awaiting automation

Risk tier: merge-risk:high — Privileged execution, automation, or review-policy change
Required to merge: passing submission-gate checks plus 1 approval from reviewers with write access, including a maintainer with admin or maintain permission.

Why this tier

• plugins/external.json is a high-risk path (automation, scripts, MCP config, hooks, or review policy)

Automated checks

Check	Status	Details
Line endings	🔧 Infrastructure failure	Waiting for a maintainer to approve workflow runs for this PR · logs
Spelling	🔧 Infrastructure failure	Waiting for a maintainer to approve workflow runs for this PR · logs
Generated README consistency	🔧 Infrastructure failure	Waiting for a maintainer to approve workflow runs for this PR · logs
Plugin and extension validation	🔧 Infrastructure failure	Waiting for a maintainer to approve workflow runs for this PR · logs
Plugin structure	🔧 Infrastructure failure	Waiting for a maintainer to approve workflow runs for this PR · logs
Risk scan	🔧 Infrastructure failure	Waiting for a maintainer to approve workflow runs for this PR · logs
Contributor reputation	🔧 Infrastructure failure	Waiting for a maintainer to approve workflow runs for this PR · logs
Duplicate resource scan	⚠️ Failed (advisory, non-blocking)	Waiting for a maintainer to approve workflow runs for this PR · logs
PR quality signal	⚠️ Failed (advisory, non-blocking)	Waiting for a maintainer to approve workflow runs for this PR · logs
Canvas/plugin smoke test	⏭️ Skipped	Not reported for this commit

Action needed

• 🔧 Line endings, Spelling, Generated README consistency, Plugin and extension validation, Plugin structure, Risk scan, Contributor reputation hit an automation problem that is not caused by your contribution. Comment /rerun-checks to retry; maintainers are notified if it keeps failing.
• ⚠️ Advisory checks did not complete (Duplicate resource scan, PR quality signal). This does not block the PR.

Review

• Approvals: 1/1 (aaronpowell)
• Assigned reviewer: not assigned yet — comment /request-review to ask for one
• Review target date: not set
• The core-maintainers pool is not staffed yet; an approver with admin or maintain permission is required instead.

Commands

Command	Who	What it does
/rerun-checks	PR author, maintainers	Re-runs failed or incomplete checks and re-evaluates this gate
/request-review	PR author, maintainers	Asks the review rotation to assign a reviewer (adds needs-reviewer)

_{Updated for 22ed9ee · gate run · This comment is maintained automatically — see submission gate docs.}

[aaronpowell]

Thanks for contributing this plugin. The pinned package targets explicitly selected real Android devices on Windows rather than emulators, and its skill spells out consent boundaries for device control, sensitive screen content, ADB startup, and app installation or removal. This is distinct from the existing mobile-canvas simulator/emulator workflow.