メニュー
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コマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
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).
SKILL.md を表示中
| 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.