← Search

Dart and Flutter test coverage
Developer tools 🧪 Install ran in our test sandbox · Nov 18, 2026 📌 Pinned version: commit 0ef3972
Install test only, on the date shown. This does not guarantee the code is safe.
⚙ Needs: a Dart or Flutter project with tests (package:test…

Dart and Flutter test coverage

Collect Dart/Flutter test coverage into LCOV reports — automated test_with_coverage script plus an advanced manual VM-service workflow

At a glance
What
Collect Dart/Flutter test coverage into LCOV reports — automated test_with_coverage script plus an advanced manual VM-service workflow
Cost
Free
Needs
a Dart or Flutter project with tests (package:test or flutter_test); the Dart/Flutter toolchain installed — no accounts or keys required
Install
Copy the installer prompt below into your Muse — your agent does the rest.

Version:

Quick answer

Dart and Flutter test coverage is a free Muse skill, the Flutter team's workflow for Dart and Flutter test coverage: add the coverage package as a dev_dependency, run the test_with_coverage script executing tests and formatting VM-collected JSON into an LCOV report, then validate coverage.json, lcov.info exist, plus an advanced manual workflow, VM service exposed, raw JSON collection.

⌁

Install

Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 18, 2026📌 Pinned version: commit 0ef3972

Step 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 or Flutter project with tests (package:test or flutter_test); the Dart/Flutter toolchain installed — no accounts or keys required Install "Dart and Flutter test coverage" for me. It teaches the agent the official Flutter team's coverage workflow: add the coverage package as a dev_dependency, run the bundled test_with_coverage script to collect JSON coverage from the Dart VM and format it into an LCOV report, validate that coverage/ holds coverage.json and lcov.info, use // coverage:ignore-line / ignore-start/ignore-end / ignore-file directives to exclude untestable code, and fall back to the advanced manual workflow (VM service on a port, collect_coverage --wait-paused, format_coverage --lcov --check-ignore) for granular control including function and branch coverage. Repository: https://raw.githubusercontent.com/flutter/agent-plugins/0ef3972f93e2baa4156ba1cbb1e515cd53079c68/skills/dart-collect-coverage/SKILL.md Pinned version: install the code at commit 0ef3972f93e2baa4156ba1cbb1e515cd53079c68 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-collect-coverage". 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 coverage as a dev_dependency in my project and run the test_with_coverage script — pass test dirs explicitly if it's a monorepo). 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.

🔒 Security, provenance and what this touches
🧭 What this touches
Based on the install prompt we scanned, this skill does not run commands, make third-party network calls, install packages, write files, or ask for API keys.
Install prompt analysis · 2026-10-13
🔒 Security and provenance
📌 Pinned version: commit 0ef3972 · 2026-10-13
🧪 Install ran in our test sandbox · Nov 18, 2026
👁 Observed during the install test · Nov 18, 2026 : no network contact
🔎 Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
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
Wanna be extra careful?

The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?

How to check a skill before installing →

✓

Verification certificate

Dated facts about what was checked for this listing, and how. This is not a safety certification.

Pinned version
0ef3972 · 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.