This skill should be used when the user wants to check whether an agent skill is portable across providers. Common triggers include "is this skill cross-provider safe", "will my skill work in cursor", "audit skill compatibility", "check if this loads in codex", and "which providers support this skill". Spawns one agent per provider in parallel using bundled provider-doc snapshots (refreshed on cadence — never fetched at runtime) and produces a compatibility matrix plus a COMPAT.md report. Skip w
SkillScore50Maintained
Automatic
◆AI Engineer pack
Last verified 8/4/2026
What it changes
Passed 9 of 17 test cases with the skill, and 3 of 17 without it.
Without skill18%
With skill50%
Checks it passed that the model alone missed
Assigns a verdict value of `unknown`.
Specifies `subagent_type: "general-purpose"`.
Includes provider `docUrls` in the persisted file.
and 6 more in the full report
8 fixed3 passed either way10 still failing1 broke
Pass-rate lift
+32 pp
Tokens
+94%
Agent turns
0%
Response time
-55%
Model gemini-3.6-flashMeasured 8/4/2026v111 of 22 cases passed with skill · 17 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 8
Prompt
When gathering provider requirements during a portability audit, you might be tempted to parse provider format docs manually. What command should be run to obtain the provider metadata list?
case-06 · gemini-3.6-flash · 8/4/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md234 lines4 filesincludes scripts
skill-portability
Audits whether an agent skill loads and behaves correctly across the major
providers — Claude Code, Cursor, OpenAI Codex CLI, and the Agents-Skills
Baseline (covering Gemini CLI, OpenCode, Pi). See scripts/providers.mjs
for the canonical list. The audit covers three layers:
Format-level — does the file/dir structure and frontmatter match what
the provider expects?
Body-level — does the body reference provider-specific conventions
(XML tags, headings) that other providers ignore?
Tool-surface-level — does the body name tools (e.g.,
AskUserQuestion) that only exist in one provider?
The canonical provider list, required/forbidden frontmatter fields, and
bundled doc snapshots live in scripts/providers.mjs
and references/providers/. Provider docs are
refreshed by hand on cadence (quarterly+) and committed — the audit never
fetches at runtime, so per-provider verdicts are deterministic and
offline-capable. See CONTRIBUTING.md for the refresh workflow.
Inputs
$ARGUMENTS — one of:
A path to a skill directory (skills/code-reviewer/ or
skills/skill-creator/)
A path to a single SKILL.md / .mdc / AGENTS.md file
A glob (skills/*) — bulk audit
A literal frontmatter+body block pasted into the prompt
Empty — discover via ls skills/ and ask which to audit
This skill should be used when the user wants to write, review, or refactor TypeScript code to follow industry best practices. Common triggers include "follow ts best practices", "review this typescript", "fix the typescript style", "make this idiomatic typescript", "apply typescript conventions", and "audit this ts file". Bakes in branded types, discriminated unions, ts-pattern for multi-branch logic, JSDoc on exports, kebab-case file naming, and *Params/*Options object-arg conventions. Skip wh