Migrate to Shoehorn
Replaces `as` type assertions in tests with type-safe @total-typescript/shoehorn helpers — fromPartial(), fromAny(), fromExact() — with before/after patterns and a step-by-step migration workflow
- What
- Replaces `as` type assertions in tests with type-safe @total-typescript/shoehorn helpers — fromPartial(), fromAny(), fromExact() — with before/after patterns and a step-by-step migration workflow
- Cost
- Free
- Needs
- a TypeScript project with test files using `as` assertions. The skill's workflow installs @total-typescript/shoehorn via npm.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — a TypeScript test-migration skill that replaces `as` type assertions with the type-safe helpers of `@total-typescript/shoehorn`, so tests can pass partial data while keeping TypeScript happy. It states the case plainly: shoehorn is test-code only, never for production code, and `as` in tests is a pain — the target type must be spelled out manually, and intentionally wrong data needs the ugly double-`as` (`as unknown as Type`). The skill teaches the three functions and when to use each: `fromPartial()` for partial data that still type-checks (the big win — pass only the properties you care about instead of faking all 20 fields of a Request), `fromAny()` for intentionally wrong data that keeps autocomplete, `fromExact()` to force a full object (swap with fromPartial later). Before/after patterns make each migration concrete, and the workflow is actionable: ask which test files have problematic `as` assertions, install (`npm i @total-typescript/shoehorn`), find test files with a grep (`grep -r " as [A-Z]" --include="*.test.ts" --include="*.spec.ts"`), replace `as Type` with `fromPartial()`, `as unknown as Type` with `fromAny()`, add the imports, then run the type check to verify. By @mattpocock, listed here with credit to its creator. Honest caveats: test code only — shoehorn must never ship in production; it replaces assertions, it doesn't add real type coverage, so run your type checker and test suite after migrating; the workflow asks you which files to migrate first, it's not an automatic whole-repo rewrite. Skill Harbor never reviews the code, review it yourself before use.
Version:
Quick answer
Migrate to Shoehorn is a free Muse skill that replaces `as` type assertions in tests with type-safe Shoehorn helpers. It uses fromPartial, fromAny and fromExact, with before-and-after patterns and a step-by-step migration workflow. Tests become safer and clearer, without the silent risks that unchecked type assertions can hide.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 18, 2026📌 Pinned version: commit 49dd158Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: a TypeScript project with test files using `as` assertions. The skill's workflow installs @total-typescript/shoehorn via npm. Install "Migrate to Shoehorn" for me. A test-migration skill that replaces `as` type assertions with type-safe @total-typescript/shoehorn helpers (fromPartial(), fromAny(), fromExact()) — with before/after patterns and a step-by-step workflow (find test files, replace, import, run type check). Test code only — never for production code. Repository: https://raw.githubusercontent.com/mattpocock/skills/49dd158d1076134a641b33efb035946536778336/skills/misc/migrate-to-shoehorn/SKILL.md Pinned version: install the code at commit 49dd158d1076134a641b33efb035946536778336 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "mattpocock-migrate-to-shoehorn". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself. GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 49dd158 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 18, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.