CtrlK
BlogDocsLog inGet started
Tessl Logo

migrate-oai-app

This skill should be used when the user asks to "migrate from OpenAI Apps SDK", "convert OpenAI App to MCP", "port from window.openai", "migrate from skybridge", "convert openai/outputTemplate", or needs guidance on converting OpenAI Apps SDK applications to MCP Apps SDK. Provides step-by-step migration guidance with API mapping tables.

68

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

73%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a well-organized, actionable migration guide with a strong validation/checklist workflow and runtime test steps. Its main weaknesses are mild repetition around CSP emphasis that could be tightened, and reliance on an external cloned repo for the bulk of the API mapping detail rather than curated bundle files.

Suggestions

Tighten the CSP guidance by stating the sandboxed-iframe / no-same-origin / 'every origin' rule once and referencing it from the checklist rather than restating it verbatim in both 'CSP Investigation' and 'Before Finishing'.

Add one complete before/after code example of a migrated tool handler (server-side registerAppTool plus client-side ontoolinput) inline, so the most common migration case is executable without opening the cloned repo.

Consider bundling the key API mapping tables into a local references/ file so the skill is self-contained and progressive disclosure relies on curated bundle files rather than a live external git clone.

DimensionReasoningScore

Conciseness

The body is mostly efficient and assumes Claude knows web/CSP basics, but the CSP-sandbox-no-same-origin point is restated in both 'CSP Investigation' and the 'Before Finishing' checklist, and the 'Every origin' emphasis is repeated, so it could be tightened — matching the anchor for mostly efficient with some unnecessary explanation.

3 / 5

Actionability

It gives concrete executable commands (version-pinned git clone, build/serve, basic-host test with exact env vars) and specific API mappings (registerAppTool, ontoolinput, app.getHostContext) plus old-to-new pattern tables, with only minor gaps such as no full end-to-end migrated handler example and some 'see migrate_from_openai_apps.md' pointers — matching the anchor for mostly executable guidance with minor gaps.

4 / 5

Workflow Clarity

The process is clearly sequenced from reference-gathering through CSP/CORS, conceptual changes, a 'Before Finishing' validation checklist with explicit checkboxes, and a Testing section with runtime verification steps (app loads, handlers fire), matching the anchor for a clear sequence with explicit validation steps and checklists.

5 / 5

Progressive Disclosure

No bundle files are provided; the body is a well-structured single SKILL.md with a table of contents and clear section headers, and it offloads bulk detail (API reference, mapping tables, examples) to clearly-signaled one-level-deep references in the cloned repo, matching the anchor for good structure with mostly clear references and minor organization gaps.

4 / 5

Total

16

/

20

Passed

Description

90%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong: it explicitly states what the skill does and when to use it, with a rich set of natural trigger phrases and a distinct, low-conflict niche. The only weakness is specificity, where the listed actions ('provides guidance', 'mapping tables') are somewhat generic rather than a comprehensive enumeration of concrete capabilities.

DimensionReasoningScore

Specificity

The description names the domain (converting OpenAI Apps SDK applications to MCP Apps SDK) and a concrete artifact ('API mapping tables', 'step-by-step migration guidance'), but the actions themselves are generic ('provides guidance') rather than a comprehensive list of specific actions, fitting the anchor that names domain plus 1-2 concrete actions without full coverage.

3 / 5

Completeness

It explicitly answers both 'what' ('Provides step-by-step migration guidance with API mapping tables') and 'when' ('This skill should be used when the user asks to...') with concrete trigger phrases, matching the anchor for clearly and explicitly answering both.

5 / 5

Trigger Term Quality

It quotes multiple natural trigger phrases a user would actually say — 'migrate from OpenAI Apps SDK', 'convert OpenAI App to MCP', 'port from window.openai', 'migrate from skybridge', 'convert openai/outputTemplate' — giving comprehensive coverage including synonyms and technical specifics, matching the top anchor.

5 / 5

Distinctiveness Conflict Risk

The niche is highly specific (OpenAI Apps SDK to MCP Apps SDK migration) with distinct trigger phrases and minimal overlap with other skills, matching the anchor for a clear niche with distinct triggers and minimal conflict risk.

5 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
seanGSISG/claude-depot
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.