Migrate Dart tests from package:matcher to package:checks
Systematically migrate a Dart test suite from legacy package:matcher expect calls to the modern type-safe package:checks assertion library
- What
- Systematically migrate a Dart test suite from legacy package:matcher expect calls to the modern type-safe package:checks assertion library
- Cost
- Free
- Needs
- a Dart project with a test suite using package:matcher (package:test)
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — the official Dart team's migration skill for moving a Dart test suite from legacy `package:matcher` (`expect`) to the modern, type-safe `package:checks` assertion library. Walks the agent through the full workflow: dependency setup (add `dev:checks`, incremental vs full migration), a matcher-to-checks mapping table, and — the genuinely valuable part — ten documented syntax differences and pitfalls that a line-for-line translation gets wrong (collection `equals` vs `deepEquals`, `reason` now `because`, `matches` vs `matchesPattern` needing an explicit RegExp, sync vs async `throws`, `bool?` strictness, map `containsKey`, custom expectations via extensions on `Subject<T>`, discovery grep patterns). Includes before/after examples for collections, cascades, property matching and async futures/streams. Honest caveat: written against the checks API as of June 2026 — re-verify syntax if you run a newer package:checks; a line-for-line translation without reading the pitfalls section can introduce false passes. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Quick answer
Migrate Dart tests is a free Muse skill, the official Dart team migration skill for moving a Dart test suite from legacy package:matcher expect calls to the modern, type-safe package:checks assertion library. It walks through dependency setup, a matcher-to-checks mapping table, and ten documented syntax differences and pitfalls that a line-for-line translation gets wrong.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 0d9f1c4Step 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 Dart project with a test suite using package:matcher (package:test) Install "Migrate Dart tests from package:matcher to package:checks" for me. The official Dart team's migration skill: dependency setup, a matcher-to-checks mapping table, ten documented syntax differences and pitfalls (deepEquals, because, matchesPattern, sync/async throws, bool? strictness, containsKey, custom expectations), discovery grep patterns, and before/after examples. Repository: https://raw.githubusercontent.com/dart-lang/skills/0d9f1c4a0ae29d6f5180bf6143d7997ec3bacf49/skills/dart-migrate-to-checks-package/SKILL.md Pinned version: install the code at commit 0d9f1c4a0ae29d6f5180bf6143d7997ec3bacf49 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, allowed hosts declared in the SKILL.md. 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 "dart-migrate-to-checks-package". 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 (e.g. add checks as a dev_dependency in pubspec.yaml). 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
- 0d9f1c4 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 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.