菜单
Use this skill when you need to set up validation for AI agent skills in a Dart project for the first time. Adds the linter as a dev_dependency, creates a configuration file, and generates a baseline for legacy repos.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/google/skills_lint.dart --skill dart-skills-lint-setup命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
How to roll, update, and integrate the skills_lint dependency into repositories (such as flutter/flutter). Use this skill when tasked with bumping skills_lint pinned commit refs in pubspec.yaml, configuring downstream test harnesses, managing package hashes, and generating submission pull requests. Do NOT use this skill for day-to-day skill validation or fixing skill markdown errors (use dart-skills-lint-validation instead).
Use this skill when you need to validate AI agent skills with skills_lint — running the linter, interpreting failures, fixing violations, and authoring custom rules.
Instructions for adding a new validation rule and CLI flag to skills_lint. Use this skill when asked to create a new rule that validates aspects of skills (like frontmatter metadata).
| name | dart-skills-lint-setup |
| description | Use this skill when you need to set up validation for AI agent skills in a Dart project for the first time. Adds the linter as a dev_dependency, creates a configuration file, and generates a baseline for legacy repos. |
| metadata | {"internal":true} |
This skill covers first-time wiring of 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.
Add skills_lint as a dev_dependency.
dev_dependencies:
skills_lint: ^0.5.0
Isolate 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.
Create skills_lint.yaml at the repository root so both
the CLI and any embedded test invocation share the same config:
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.
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 skills_lint --skills-directory=.agents/skills --generate-baseline
This 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.
Wire it into CI. Use the GitHub Actions recipe from the README verbatim, or follow the pre-commit hook recipe below it.
The dart-skills-lint-validation skill takes over from here for day-to-day use.