Dart Skills Lint Setup Agent Skill

|- 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.

2k tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

2776

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/flutter/agent-plugins --skill dart-skills-lint-setup

What comes with it

3 702 bytes besides the instruction

evals/evals.json

The instruction itself

3 sections, as written by the author

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

Add dart_skills_lint as a dev_dependency.

   dev_dependencies:
     dart_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 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.

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-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.

When you're done

The dart-skills-lint-validation skill takes over from here for

day-to-day use.

Other skills for the same job

different authors, same section of the catalogue

Gemini

by softaworks

×2

Use when the user asks to run Gemini CLI for code review, plan review, or big context (>200k) processing. Ideal for comprehensive analysis requiring large context windows. Uses Gemini 3 Pro by default for state-of-the-art reasoning and coding.

Claude Skills meta-skill: extract domain material (docs/APIs/code/specs) into a reusable Skill (SKILL.md + references/scripts/assets), and refactor existing Skills for clarity, activation reliability, and quality gates.

13k tokens scripts

Backend Atomic Commit

by ComeOnOliver

×1

> Pedantic backend pre-commit and atomic commit Skill for Django/Optimo-style repos. Enforces local AGENTS.md / CLAUDE.md, pre-commit hooks, .security/* helpers, and Monty’s backend engineering taste – with no AI signatures in commit messages.

Automatically backs up files, saves diffs, uses agents/skills, and ensures modular code (<200 lines) before any implementation. Use this skill for ALL code changes to ensure safe, reversible, and clean implementations.

Use when you've developed a broadly useful skill and want to contribute it upstream via pull request - guides process of branching, committing, pushing, and creating PR to contribute skills back to upstream repository

4k tokens

Od Code Migration

by nexu-io

Default reference pipeline for the code-migration taskKind — code-import → design-extract → token-map → rewrite-plan → patch-edit ↔ build-test devloop → diff-review → handoff.

4k tokens

Review Agent Setup

by wshobson

Configure human-in-the-loop gating for AI agent review actions in Claude Code. Use when setting up a project where an agent may post PR reviews, comments, merges, or edit CI configuration, and you want a cryptographically auditable approval trail with Cedar-enforced gates.

> Check installed community skills for updates. Shows a diff and requires explicit approval before applying. Use when the user says "check for updates", "update my skills", "anything new for my installed skills", or when invoked from the registry-sync agent.

2k tokens

How to use it

Copy the folder

Take flutter/dart-skills-lint-setup from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.