How do I install Skill Portability Check?

Install Skill Portability Check with a single command: npx mdskills install proskillpacks/skill-portability-check. This downloads the skill files into your project and your AI agent picks them up automatically.

What platforms support Skill Portability Check?

Skill Portability Check works with Claude Code, Claude Desktop, Cursor, Vscode Copilot, Windsurf, Continue Dev, Codex, Gemini Cli, Amp, Roo Code, Goose, Opencode, Trae, Qodo, Command Code. Skills use the open SKILL.md format which is compatible with any AI coding agent that reads markdown instructions.

Skill Portability Check

Name: Skill Portability Check: AI Agent Skill
Brand: proskillpacks
Availability: InStock
Author: proskillpacks

ProductivityIntermediate

Checks Agent Skills (SKILL.md folders) for portability and common mistakes with a standard-library Python script, then explains each finding and the fix. It catches frontmatter that strict YAML parsers reject (such as an unquoted colon in the description, which makes tools like npx skills skip the skill), keys other than name and description, bad name format, a description that does not say when to use the skill, vendor tool names and paths, missing fallbacks when a tool or the network is...

by kaiventura.founder

npx mdskills install proskillpacks/skill-portability-check

Fact Claim Checker

Reads a draft article, post, newsletter, report or script and lists every claim that needs a source before it is published, sorted by risk, with what kind of source would settle each one. It marks which claims the draft itself already supports, which are plain opinion, and which are risky (numbers, studies, quotes, dates, "first/only/best", cause and effect, claims about people or companies). It does not rule claims true or false from memory.

CSV Profile And Sanity Check

Reads a CSV or spreadsheet export without changing it and reports what is in it, including row and column counts, each column's type, blanks, distinct values, numeric ranges, duplicates, mixed formats, odd outliers and case or spacing variants, then lists what to ask the data's owner before anyone uses it.

Cold Email Checker

Checks a drafted cold email before it is sent. It tests every claim about the prospect against text you supply, flags claims about you that need proof, checks length, subject line and the single ask, checks the legal basics of commercial email (sender identity, postal address, opt-out), and returns a tightened version with unsupported claims removed.

Readme First Run Check

Reads a project's README the way a new user would and checks, against the repository itself, every step they are told to take - the prerequisites and versions, the install and setup commands, the files, scripts, environment variables and ports the README mentions, and the run and test commands. It reports each step as OK, BROKEN, MISSING or UNVERIFIED with file evidence, then gives the first-run path a newcomer would actually experience and the README edits that fix it.

SKILL.md

1---
2name: skill-portability-check
3description: Checks Agent Skills (SKILL.md folders) for portability and common mistakes with a standard-library Python script, then explains each finding and the fix. It catches frontmatter that strict YAML parsers reject (such as an unquoted colon in the description, which makes tools like npx skills skip the skill), keys other than name and description, bad name format, a description that does not say when to use the skill, vendor tool names and paths, missing fallbacks when a tool or the network is absent, long bodies, and broken links. Use when the user says "check my skill", "lint SKILL.md", "is this skill portable", "why is my skill not found", "validate my skills repo", or points at a skill folder or a repository of skills.
4---
5 
6# Skill Portability Check
7 
8You run a checker over one or more skills and explain what to fix. The script does the finding. You do not guess about files you did not check.
9 
10## Input
11- **Required:** a path to a skill folder (one with `SKILL.md`), or to a repository or folder that holds many.
12- **Optional (don't ask; use defaults):** whether warnings should fail the check (default: only errors fail).
13 
14## Step 1: Run the checker
15```bash
16python3 <this-skill-dir>/scripts/skill_check.py <path> [<path> ...]
17```
18Add `--json` for machine-readable output, `--strict` to make warnings fail the run, `--quiet` for findings only. It reads files and changes nothing. A folder that contains a file named `.skill-check-ignore` is skipped (for test fixtures).
19**Fallback.** If you have no shell or no Python, ask the user to paste the `SKILL.md` (the whole file, including the frontmatter), and check it by reading against the rules in Step 2. Say that you checked by reading, not with the script, and that the script may find more.
20 
21**Stop condition.** If neither the script nor a pasted `SKILL.md` is available, say that nothing was checked and stop. Do not report a skill as clean from its name.
22 
23## Step 2: What the checks mean
24**Errors (the script exits 1):**
25- Frontmatter missing, not closed, or rejected by strict YAML. The usual cause is an unquoted `: ` or ` #` in the description. Fix: reword it, or wrap the whole value in double quotes and escape inner double quotes.
26- Missing `name` or `description`; a `name` that is not lowercase letters, digits and single hyphens, is over 64 characters, or differs from the folder name; a description over 1024 characters.
27- A markdown link to a file that does not exist next to `SKILL.md`.
28**Warnings:**
29- Frontmatter keys other than `name` and `description` (the portable core). `license`, `compatibility` and `metadata` are in the public spec and only noted; `allowed-tools` and anything else is tool-specific.
30- A description that does not say when to use the skill: add "Use when the user says ...".
31- Vendor tool names (the names of one product's web, shell, skill or connector tools) and vendor skill folders (a product's hidden config folder): say the action in plain words, and name `.agents/skills/` or "your tool's skills folder".
32- No fallback when the text relies on the web, a shell or a script: add one sentence such as "if you have no shell, ask the user to paste it".
33- Text that some tools substitute with the user's arguments (a dollar sign followed by ARGUMENTS or by a digit): write amounts as "15 USD".
34- A body over 500 lines: move detail into `references/` files.
35- A `scripts/` or `references/` file that the text mentions but that is not in the folder.
36 
37## Step 3: Report
381. The table the script printed (skill, errors, warnings, lines, script languages), unchanged.
392. For each error and warning, in order of severity: the finding, why it matters in one sentence, and the exact fix (the replacement line when it is a single line).
403. What it did not check: whether the instructions actually work, whether the skill triggers, and anything outside the folder.
414. If the user wants a CI check, give them the workflow in the README.
42 
43## Rules
44- Never claim a skill is "portable" or "valid". Say what the checks found and what they do not cover.
45- Do not edit the user's files unless asked. Propose the exact replacement text.
46- Quote findings from the output. Do not invent findings the script did not print.
47

Full transparency — inspect the skill content before installing.