
Dart Skills Lint Setup
- 5 installs
- 2.8k repo stars
- Updated August 4, 2026
- flutter/skills
Sets up dart_skills_lint validation in a Dart project for the first time, adding the dev dependency, config file, and a legacy baseline.
About
Covers first-time wiring of dart_skills_lint: adding it as a git dev_dependency, creating dart_skills_lint.yaml, and generating a baseline for repos with legacy violations. A developer uses it when introducing skills validation to a project.
- Add dart_skills_lint as an isolated git dev_dependency in a tool/ package
- Create dart_skills_lint.yaml and generate a baseline for legacy skills
Dart Skills Lint Setup by the numbers
- 5 all-time installs (skills.sh)
- Ranked #568 of 782 Skill Development skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/flutter/skills --skill dart-skills-lint-setupAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 5 |
|---|---|
| repo stars | ★ 2.8k |
| Last updated | August 4, 2026 |
| Repository | flutter/skills ↗ |
What it does
Sets up dart_skills_lint validation in a Dart project for the first time, adding the dev dependency, config file, and a legacy baseline.
Files
Setting up Skill Validation with dart_skills_lint
This skill covers first-time wiring of dart_skills_lint into a repository. For ongoing use — running the linter, interpreting output, and writing custom rules — see the `dart-skills-lint-validation` skill. For copy-pasteable CI workflow and pre-commit hook recipes, see the `Recipes` section of the README.
Steps
1. Add `dart_skills_lint` as a `dev_dependency`. Prefer a git dependency (the package isn't on pub.dev yet):
dev_dependencies:
dart_skills_lint:
git:
url: https://github.com/flutter/skills.git
path: tool/dart_skills_lintIsolate the dependency in a tool/ package when you can, instead of putting it on the root pubspec.yaml — keeps the linter's deps out of your runtime closure. If you must add it to multiple pubspec.yaml files, ensure the ref: (commit hash) is identical across all of them so resolution doesn't diverge.
2. Create `dart_skills_lint.yaml` at the repository root so both the CLI and any embedded test invocation share the same config:
dart_skills_lint:
rules:
check-relative-paths: error
check-trailing-whitespace: error
directories:
- path: ".agents/skills"Rules enabled by default — check-absolute-paths, valid-yaml-metadata, invalid-skill-name, description-too-long — only need to be listed if you want to change their severity. See `RULES.md` for the full list.
3. Generate a baseline if you're integrating into a repository with pre-existing skills that have legacy violations you don't want to fix immediately:
dart run dart_skills_lint:cli --skills-directory=.agents/skills --generate-baselineThis writes the current set of failures into an ignore file so the next run exits clean. New violations introduced after the baseline still surface as errors.
4. Wire it into CI. Use the GitHub Actions recipe from the README verbatim, or follow the pre-commit hook recipe below it.
When you're done
The dart-skills-lint-validation skill takes over from here for day-to-day use.