Skip to content

Adapt Power Platform skills for Codex#91

Open
geekjapan wants to merge 8 commits intomicrosoft:mainfrom
geekjapan:codex-skill-migration
Open

Adapt Power Platform skills for Codex#91
geekjapan wants to merge 8 commits intomicrosoft:mainfrom
geekjapan:codex-skill-migration

Conversation

@geekjapan
Copy link
Copy Markdown

Summary

  • adapt repository and plugin guidance so Codex can consume plugin skills as standalone skill folders
  • simplify all SKILL.md frontmatter to Codex-friendly metadata with only name and description
  • rewrite canvas-apps workflows to run in a single Codex agent instead of relying on Claude task orchestration
  • update key skill references in code-apps to use relative paths that Codex can follow directly

Validation

  • ran git diff --check
  • verified all SKILL.md frontmatters contain only name and description

@geekjapan geekjapan requested a review from a team as a code owner April 16, 2026 04:35
@microsoft-github-policy-service
Copy link
Copy Markdown

@geekjapan please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.

@microsoft-github-policy-service agree [company="{your company}"]

Options:

  • (default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.
@microsoft-github-policy-service agree
  • (when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.
@microsoft-github-policy-service agree company="Microsoft"
Contributor License Agreement

Contribution License Agreement

This Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
and conveys certain license rights to Microsoft Corporation and its affiliates (“Microsoft”) for Your
contributions to Microsoft open source projects. This Agreement is effective as of the latest signature
date below.

  1. Definitions.
    “Code” means the computer software code, whether in human-readable or machine-executable form,
    that is delivered by You to Microsoft under this Agreement.
    “Project” means any of the projects owned or managed by Microsoft and offered under a license
    approved by the Open Source Initiative (www.opensource.org).
    “Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to any
    Project, including but not limited to communication on electronic mailing lists, source code control
    systems, and issue tracking systems that are managed by, or on behalf of, the Project for the purpose of
    discussing and improving that Project, but excluding communication that is conspicuously marked or
    otherwise designated in writing by You as “Not a Submission.”
    “Submission” means the Code and any other copyrightable material Submitted by You, including any
    associated comments and documentation.
  2. Your Submission. You must agree to the terms of this Agreement before making a Submission to any
    Project. This Agreement covers any and all Submissions that You, now or in the future (except as
    described in Section 4 below), Submit to any Project.
  3. Originality of Work. You represent that each of Your Submissions is entirely Your original work.
    Should You wish to Submit materials that are not Your original work, You may Submit them separately
    to the Project if You (a) retain all copyright and license information that was in the materials as You
    received them, (b) in the description accompanying Your Submission, include the phrase “Submission
    containing materials of a third party:” followed by the names of the third party and any licenses or other
    restrictions of which You are aware, and (c) follow any other instructions in the Project’s written
    guidelines concerning Submissions.
  4. Your Employer. References to “employer” in this Agreement include Your employer or anyone else
    for whom You are acting in making Your Submission, e.g. as a contractor, vendor, or agent. If Your
    Submission is made in the course of Your work for an employer or Your employer has intellectual
    property rights in Your Submission by contract or applicable law, You must secure permission from Your
    employer to make the Submission before signing this Agreement. In that case, the term “You” in this
    Agreement will refer to You and the employer collectively. If You change employers in the future and
    desire to Submit additional Submissions for the new employer, then You agree to sign a new Agreement
    and secure permission from the new employer before Submitting those Submissions.
  5. Licenses.
  • Copyright License. You grant Microsoft, and those who receive the Submission directly or
    indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license in the
    Submission to reproduce, prepare derivative works of, publicly display, publicly perform, and distribute
    the Submission and such derivative works, and to sublicense any or all of the foregoing rights to third
    parties.
  • Patent License. You grant Microsoft, and those who receive the Submission directly or
    indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license under
    Your patent claims that are necessarily infringed by the Submission or the combination of the
    Submission with the Project to which it was Submitted to make, have made, use, offer to sell, sell and
    import or otherwise dispose of the Submission alone or with the Project.
  • Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement.
    No additional licenses or rights whatsoever (including, without limitation, any implied licenses) are
    granted by implication, exhaustion, estoppel or otherwise.
  1. Representations and Warranties. You represent that You are legally entitled to grant the above
    licenses. You represent that each of Your Submissions is entirely Your original work (except as You may
    have disclosed under Section 3). You represent that You have secured permission from Your employer to
    make the Submission in cases where Your Submission is made in the course of Your work for Your
    employer or Your employer has intellectual property rights in Your Submission by contract or applicable
    law. If You are signing this Agreement on behalf of Your employer, You represent and warrant that You
    have the necessary authority to bind the listed employer to the obligations contained in this Agreement.
    You are not expected to provide support for Your Submission, unless You choose to do so. UNLESS
    REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING, AND EXCEPT FOR THE WARRANTIES
    EXPRESSLY STATED IN SECTIONS 3, 4, AND 6, THE SUBMISSION PROVIDED UNDER THIS AGREEMENT IS
    PROVIDED WITHOUT WARRANTY OF ANY KIND, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY OF
    NONINFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.
  2. Notice to Microsoft. You agree to notify Microsoft in writing of any facts or circumstances of which
    You later become aware that would make Your representations in this Agreement inaccurate in any
    respect.
  3. Information about Submissions. You agree that contributions to Projects and information about
    contributions may be maintained indefinitely and disclosed publicly, including Your name and other
    information that You submit with Your Submission.
  4. Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, and
    the parties consent to exclusive jurisdiction and venue in the federal courts sitting in King County,
    Washington, unless no federal subject matter jurisdiction exists, in which case the parties consent to
    exclusive jurisdiction and venue in the Superior Court of King County, Washington. The parties waive all
    defenses of lack of personal jurisdiction and forum non-conveniens.
  5. Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and
    supersedes any and all prior agreements, understandings or communications, written or oral, between
    the parties relating to the subject matter hereof. This Agreement may be assigned by Microsoft.

Power Pages の主要スキル群に残っていた ClaudeCode 前提の
オーケストレーション記述を、Codex の通常会話フローと
update_plan 前提の実行モデルに合わせて整理した。
AskUserQuestion / TaskCreate / TaskUpdate / TaskList 依存を外し、
Codex Notes と plugin check の統一も含めて、skill 単位で
そのまま Codex で運用できる状態に揃えた。

Constraint: 既存の skill 本文構造はできるだけ維持し、差分を小さく保つ必要があった
Constraint: plugin-level AGENTS.md の運用方針に合わせて Codex Notes を各 skill に明示する必要があった
Rejected: 全 skill を全面書き換え | 差分が大きくレビューしづらい
Rejected: power-pages だけ共通 reference に逃がす | 各 SKILL.md 単体で読める利点を損なう
Confidence: high
Scope-risk: moderate
Reversibility: clean
Directive: 今後新しい power-pages skill を追加する場合も Claude 専用 orchestration 語を直接書かず Codex 会話 + update_plan で記述すること
Tested: rg による legacy orchestration 語の除去確認 (power-pages), git diff --check
Not-tested: 個々の skill 手順の実運用テスト
code-apps の skill 群に Codex Notes を追加し、sibling skill の
扱いと通常チャットでの確認フローを明示した。
すでに一部進めていた Codex 変換と整合するよう、plugin 全体で
案内の粒度と表現を揃えた。

Constraint: connector ごとの手順本文は維持し、運用メタ情報だけを最小差分で追加する必要があった
Constraint: 既存の add-* skill 相互参照は残しつつ Codex 利用者に意味が通る必要があった
Rejected: すべての code-app skill を大きく再構成 | 実質的な挙動差分が増える
Rejected: Codex Notes を追加せず一部だけ手動補正 | plugin 内で一貫性が出ない
Confidence: high
Scope-risk: narrow
Reversibility: clean
Directive: code-apps 配下の新規 skill には最低限 Codex Notes を付け、/add-* 参照は sibling workflow として説明すること
Tested: git diff --check, 全 code-apps skill の Codex Notes 存在確認
Not-tested: 個々の connector skill の対話フロー実地確認
model-apps と canvas-apps の skill 群を Codex で自然に読めるよう
補強した。genpage には既存変換の仕上げを行い、canvas-apps には
Codex Notes を追加して、単一エージェント実行と update_plan の
使いどころを明示した。configure-canvas-mcp はマルチツール対応を
維持しつつ、Codex 優先の読み方を補足した。

Constraint: configure-canvas-mcp は Claude/Copilot 向け分岐も正当な機能として保持する必要があった
Constraint: Canvas App 系 skill は Studio 操作を含むため、Codex 単独で完結しない部分を明確にする必要があった
Rejected: Claude/Copilot 分岐の削除 | マルチツール用途を壊す
Rejected: canvas skill をすべて Codex 専用に書き換え | 既存用途を狭める
Confidence: high
Scope-risk: narrow
Reversibility: clean
Directive: マルチツール対応 skill では Codex 優先の注記を追加しつつ他ツール分岐は機能要件として残すこと
Tested: git diff --check, model-apps/canvas-apps の Codex Notes 存在確認
Not-tested: MCP 設定手順そのものの実行確認
README を Codex 中心に再構成し、旧 Claude Code 起点からの
変更点、利用方法、互換層、インストール手順、移行時の読み替え規則を
詳しく追記した。あわせて .omx/ を gitignore に追加し、
ローカル runtime state がレビュー対象に混ざらないよう整理した。

Constraint: README は Codex 利用者向けの新しい入口でありつつ、Claude/Copilot の互換情報も残す必要があった
Constraint: .omx/ はローカル運用で継続的に生成されるため、VCS 対象から外す必要があった
Rejected: README を Codex 専用にして legacy 情報を削除 | 既存利用者の移行導線を失う
Rejected: .omx 配下の個別ファイルだけ ignore | state の増減に追従しづらい
Confidence: high
Scope-risk: narrow
Reversibility: clean
Directive: 今後 README を更新する際も Codex の使い方を主軸にしつつ互換層の説明を維持すること
Tested: git diff --check -- README.md, git status で .omx が追跡対象から外れる前提を確認
Not-tested: 他環境での ignore 挙動
The repo already excludes other agent-local runtime directories, but `.codex`
was still showing up as an untracked local artifact. Add it to `.gitignore`
so local Codex workspace state does not distract from reviewable source changes.

Constraint: `.codex` is a local execution artifact, not a shared project input
Rejected: Track `.codex` in the repo | machine-local state should not be versioned
Confidence: high
Scope-risk: narrow
Reversibility: clean
Directive: Keep local agent/runtime directories ignored unless they become explicit shared project config
Tested: `git check-ignore -v .codex`, `git diff --check -- .gitignore`
Not-tested: Ignore behavior on other developer machines
README を日英併記で再構成し、Codex 向けの使い方、
Claude Code からの移行差分、互換レイヤーの扱い、
導入手順と開発手順を両言語で追えるようにした。
Codex 利用者を主軸にしつつ、legacy plugin packaging の
背景と残存理由も分かるように整理した。

Constraint: README は Codex 利用者向けの新しい入口でありつつ、Claude/Copilot 利用者の互換情報も残す必要があった
Constraint: 既存の技術内容を落とさず、日英で対応関係が分かる構成にする必要があった
Rejected: 日本語だけを追加 | 英語利用者の入口を弱める
Rejected: 完全な二重README化 | 保守コストが高く内容差分も発生しやすい
Confidence: high
Scope-risk: narrow
Reversibility: clean
Directive: 今後 README を更新する際も、Codex 中心の説明と日英対応を崩さずに追記すること
Tested: git diff --check -- README.md
Not-tested: 外部利用者による可読性確認
@@ -1,15 +1,16 @@
---
name: configure-canvas-mcp
version: 1.0.0
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We haven't used codex very much. Does it actually fail if these frontmatter fields are present, or does it just ignore them? IMO we shouldn't make the skills worse for Github Copilot and Claude just for Codex.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants