Dart Agent Skills
Official Dart team Agent Skills for AI coding agents working on Dart unit tests, CLI apps, coverage, runtime errors, mocks, package conflicts, static analysis, Native Assets, FFI, ffigen, and pattern matching.
Open the source and read safety notes before installing.
Safety notes
- Dart skills can modify source code, tests, pubspec dependencies, analysis options, generated mocks, coverage output, native hooks, FFI bindings, and package constraints.
- `dart fix --apply`, formatter runs, mock generation, build_runner, ffigen, and Native Assets hooks can create broad mechanical diffs; inspect changes before committing.
- Native Assets and FFI workflows may compile C/C++ code, run local toolchains, download precompiled binaries, and link dynamic or static libraries.
- Downloaded binaries should use cryptographic hash validation and offline fallbacks as the skill describes.
- Package conflict fixes can upgrade or downgrade dependencies and affect transitive package behavior across Dart and Flutter projects.
Privacy notes
- Dart projects may contain private package names, API schemas, service URLs, test fixtures, generated mocks, coverage paths, stack traces, native library names, and build logs.
- Runtime-error workflows can expose stack traces, local paths, active app state, logs, and user-input data from the running program.
- FFI and Native Assets workflows may include proprietary C/C++ source, platform-specific build settings, binary hashes, and downloaded artifact URLs.
- Keep credentials, private package registries, source paths when sensitive, proprietary native code, test data, and generated coverage reports out of public prompts, issues, PRs, and examples.
Prerequisites
- Dart SDK and project-local tooling installed for the package being edited.
- An AI coding assistant or skill host compatible with Agent Skills, preferably using the standard `.agents/skills` install target.
- Project `pubspec.yaml`, `analysis_options.yaml`, test structure, package constraints, and platform targets available before modifying code.
- For FFI or Native Assets work, compatible host compiler toolchains, package hooks, native source, binding generation configuration, and platform targets.
Schema details
- Install type
- package
- Reading time
- 8 min
- Difficulty score
- 75
- Troubleshooting
- Yes
- Breaking changes
- No
- Scope
- Source repo
- Skill type
- capability-pack
- Skill level
- expert
- Verification
- validated
- Verified at
- 2026-06-18
| Platform | Support | Install path |
|---|---|---|
| claude-code | Native | .claude/skills/<skill-name>/SKILL.md |
| codex | Native | .agents/skills/<skill-name>/SKILL.md |
| windsurf | Native | .windsurf/skills/<skill-name>/SKILL.md |
| gemini | Native | .gemini/skills/<skill-name>/SKILL.md or .agents/skills/<skill-name>/SKILL.md |
| cursor | Adapter | .cursor/rules/<skill-name>.mdc |
| cli | Manual | AGENTS.md or tool-specific context file |
Full copyable content
npx skills add dart-lang/skills --skill '*' --agent universal --yes
# Update installed skills
npx skills updateAbout this resource
Dart Agent Skills
dart-lang/skills is the official Dart team Agent Skills repository. It gives
AI coding agents repeatable workflows for common Dart development tasks:
unit tests, CLI apps, coverage, runtime errors, generated mocks, package
conflicts, static analysis, FFI, Native Assets, ffigen, and pattern matching.
The README describes skills as complementary to MCP: MCP gives an agent access to specialized tools, while a skill teaches the agent how to use tools for a specific task. That is useful for Claude Code, Codex, Gemini CLI, and other coding agents that need Dart-specific guardrails instead of generic language advice.
Knowledge Freshness
The repository is maintained by the Dart team and representative skills include
recent 2026 metadata. Dart analyzer behavior, language features, package
versions, Native Assets hooks, ffigen, package:test, package:checks,
package:mockito, and build tooling can change.
Use the skills for workflow structure and Dart-specific guardrails, then verify exact commands, packages, SDK constraints, analyzer settings, and generated outputs against the target project and current Dart documentation.
Retrieval Sources
This listing is grounded in:
- The
dart-lang/skillsrepository README. - The public skills.sh listing for Dart skills.
- Representative
SKILL.mdfiles for static analysis, FFI/Native Assets, and runtime-error workflows. - The repository license text.
- Current GitHub repository metadata from the official Dart organization.
Core Workflow
Install all Dart skills into the standard universal skill location:
npx skills add dart-lang/skills --skill '*' --agent universal --yes
Update installed skills:
npx skills update
The README recommends the universal .agents/skills target so most agents can
discover the installed skills.
Capability Scope
The repository currently lists these Dart skills:
| Skill | Scope |
|---|---|
dart-add-unit-test |
Write and organize unit tests with package:test |
dart-build-cli-app |
CLI entrypoints, exit codes, and cross-platform script structure |
dart-collect-coverage |
Collect coverage and create LCOV reports |
dart-setup-ffi-assets |
Compile and package C/C++ code using Native Assets hooks |
dart-fix-runtime-errors |
Locate stack traces, fix failures, and verify with reload or tests |
dart-generate-test-mocks |
Generate mocks with package:mockito and build_runner |
dart-migrate-to-checks-package |
Replace matcher-style expectations with package:checks |
dart-resolve-package-conflicts |
Fix pub dependency version conflicts |
dart-run-static-analysis |
Run dart analyze, apply dart fix, format, and verify diagnostics |
dart-use-ffigen |
Generate FFI bindings instead of hand-writing dart:ffi bindings |
dart-use-pattern-matching |
Apply switch expressions and Dart pattern matching where appropriate |
Production Rules
Use these skills with Dart-specific change control:
- Inspect
pubspec.yaml,analysis_options.yaml, SDK constraints, package layout, test conventions, and generated-file rules before editing. - Run
dart analyzeand focused tests before broad changes. - Preview
dart fix --dry-runbefore applying mechanical fixes. - Review generated mocks, bindings, coverage output, and formatter changes before committing.
- For FFI and Native Assets, keep path handling portable, validate downloaded binaries, and avoid raw shell toolchain orchestration where package APIs exist.
- Treat package conflict resolution as a dependency change with possible transitive runtime impact.
- Do not publish generated examples, stack traces, native source, or test data that expose private code or environment details.
Use Cases
- Ask Codex to run Dart static analysis, preview automated fixes, and resolve remaining analyzer errors safely.
- Use Claude Code to add unit tests for a package with
package:test. - Ask Gemini CLI to resolve
pub getdependency conflicts without blindly upgrading unrelated packages. - Use an agent to set up Native Assets hooks for a C library with hash-checked prebuilt binary fallback.
- Have an assistant generate ffigen bindings rather than writing brittle
dart:ffibindings by hand.
Source Review
- The README describes Agent Skills for Dart as maintained by the Dart team.
- The README says the skills provide tailored instructions for common Dart development workflows.
- The README says skills complement MCP by teaching an agent how to use tools for a specific task.
- The install command uses
npx skills add dart-lang/skills --skill '*' --agent universal --yes. - The available skills list covers unit tests, CLI apps, coverage, FFI/native assets, runtime errors, mocks, package conflicts, static analysis, ffigen, and pattern matching.
- The static-analysis skill documents
analysis_options.yaml, strict type checks, analyzer plugins,dart analyze,dart fix --dry-run,dart fix --apply, and formatting. - The Native Assets skill covers build/link hooks, compiler toolchains, precompiled binary downloads, cryptographic validation, and tree-shaking.
- The license file identifies the repository as BSD-style terms from the Dart authors.
Duplicate Review
Checked current content/skills/, content/tools/, content/mcp/, open pull
requests, and repository-wide content for dart-lang/skills, Dart Agent
Skills, Dart skills, Dart static analysis skills, Dart FFI skills, Dart Native
Assets skills, and representative skill names. No dedicated Dart Agent Skills
entry, exact source URL duplicate, target file, or open duplicate PR was found.
Disclosure
Editorial listing. No paid placement or affiliate link is used. The upstream repository is maintained by the Dart team and uses BSD-style license terms.
Source citations
Add this badge to your README
How it compares
Dart Agent Skills side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
| Field | Dart Agent Skills Official Dart team Agent Skills for AI coding agents working on Dart unit tests, CLI apps, coverage, runtime errors, mocks, package conflicts, static analysis, Native Assets, FFI, ffigen, and pattern matching. Open dossier | Flutter Agent Skills Official Flutter team Agent Skills for AI coding agents building Flutter apps, fixing layout issues, adding widget and integration tests, creating widget previews, applying layered architecture, routing, localization, JSON serialization, and HTTP workflows. Open dossier | Google Cloud Agent Skills Google Agent Skills catalog for AI agents working with Google Cloud, Gemini Enterprise Agent Platform, Gemini APIs, Skill Registry, Cloud Run, BigQuery, Firebase, GKE, Cloud SQL, AlloyDB, gcloud, auth, onboarding, and Well-Architected Framework guidance. Open dossier | Vercel Agent Skills Vercel Labs' official Agent Skills collection for AI coding agents working on Vercel deployments, React and Next.js performance, React Native, web design guidelines, writing guidelines, composition patterns, view transitions, CLI token workflows, and Vercel optimization audits. Open dossier |
|---|---|---|---|---|
| Trust | ||||
| Install risk | Review first | Review first | Review first | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Category | skills | skills | skills | skills |
| Source | source-backed | source-backed | source-backed | source-backed |
| Author | Dart Team | Flutter Team | Vercel Labs | |
| Added | 2026-06-18 | 2026-06-18 | 2026-06-18 | 2026-06-18 |
| Platforms | Claude CodeCodexWindsurfGeminiCursorCLI | Claude CodeCodexWindsurfGeminiCursorCLI | Claude CodeCodexWindsurfGeminiCursorCLI | Claude CodeCodexWindsurfGeminiCursorCLI |
| Source repo | — | — | — | — |
| Safety notes | ✓Dart skills can modify source code, tests, pubspec dependencies, analysis options, generated mocks, coverage output, native hooks, FFI bindings, and package constraints. `dart fix --apply`, formatter runs, mock generation, build_runner, ffigen, and Native Assets hooks can create broad mechanical diffs; inspect changes before committing. Native Assets and FFI workflows may compile C/C++ code, run local toolchains, download precompiled binaries, and link dynamic or static libraries. Downloaded binaries should use cryptographic hash validation and offline fallbacks as the skill describes. Package conflict fixes can upgrade or downgrade dependencies and affect transitive package behavior across Dart and Flutter projects. | ✓Flutter skills can modify application code, tests, pubspec dependencies, routing, localization files, serialization code, architecture boundaries, and app entry points. Integration-test workflows may enable Flutter Driver extensions, add keys to widgets, launch apps through MCP tools, interact with running UI, and create driver scripts. Do not run device, emulator, browser, Firebase Test Lab, or network-backed integration tests against production services without explicit approval and test credentials. Architecture and routing changes can alter navigation, state management, API access, caching, offline behavior, and user-visible app flows. Use project-local conventions and Flutter version constraints before applying generated examples. | ✓Google Cloud skills can create, update, delete, deploy, query, or configure cloud resources, datasets, IAM policies, service accounts, APIs, containers, jobs, and networking. The gcloud skill requires command validation and safety guardrails before invoking Google Cloud CLI commands; do not let agents improvise cloud commands from memory. Skill Registry guidance includes skill lifecycle management such as upload, update, and permanent delete operations; validate environment and approval before use. Cloud Run, GKE, BigQuery, Firebase, Cloud SQL, AlloyDB, and Gemini API workflows can create cost, expose endpoints, alter data, or change production behavior. The repository notes active development, so verify exact commands, product names, API availability, and launch-stage limits before production use. | ✓The deploy-to-vercel and Vercel CLI token skills can guide agents toward git pushes, preview deployments, Vercel project linking, environment variable changes, and account-scoped CLI calls; keep human approval on those actions. The vercel-cli-with-tokens skill includes token-handling workflows. Prefer environment variables over command-line token flags and avoid echoing secrets into prompts, logs, screenshots, or public PRs. The vercel-optimize skill reads Vercel metrics, usage, project configuration, and code scan results; verify the linked project and team scope before collecting or acting on recommendations. The web-design-guidelines and writing-guidelines skills fetch current upstream rule documents at use time, so review fetched guidance before treating output as policy. React, Next.js, and React Native performance rules are strong defaults, but agents still need local tests, framework-version checks, and product-specific review before broad refactors. |
| Privacy notes | ✓Dart projects may contain private package names, API schemas, service URLs, test fixtures, generated mocks, coverage paths, stack traces, native library names, and build logs. Runtime-error workflows can expose stack traces, local paths, active app state, logs, and user-input data from the running program. FFI and Native Assets workflows may include proprietary C/C++ source, platform-specific build settings, binary hashes, and downloaded artifact URLs. Keep credentials, private package registries, source paths when sensitive, proprietary native code, test data, and generated coverage reports out of public prompts, issues, PRs, and examples. | ✓Flutter projects may contain API URLs, Firebase project IDs, mobile bundle IDs, analytics keys, user fixtures, screenshots, test traces, device logs, crash output, and integration-test artifacts. MCP app exploration can expose widget trees, screen text, test data, typed inputs, navigation paths, and screenshots from the running app. HTTP, JSON, localization, and repository-layer work may touch private API schemas, user data models, translations, product copy, and backend payloads. Keep credentials, private endpoints, screenshots with user data, device logs, Firebase tokens, and proprietary UI flows out of public prompts, issues, PRs, and examples. | ✓Google Cloud workflows may expose project IDs, service account emails, OAuth tokens, API keys, ADC credentials, Terraform state, dataset names, table schemas, query text, logs, traces, prompts, model outputs, embeddings, and customer data. BigQuery, Firebase, Cloud SQL, AlloyDB, GKE, and Agent Platform workflows may process regulated or proprietary data; review data residency, IAM, retention, audit logging, and sharing rules before use. Gemini API and Agent Platform skills can send prompts, files, images, audio, video, tool inputs, structured outputs, cached contexts, and batch datasets to Google services. Keep credentials, project IDs when sensitive, private queries, logs, trace payloads, Terraform state, customer data, and generated datasets out of public prompts, issues, PRs, and screenshots. | ✓Deployment and optimization workflows may expose project names, team slugs, deployment URLs, routes, metrics, usage details, billing signals, source paths, build configuration, environment variable names, and CLI account context. Keep VERCEL_TOKEN, VERCEL_ORG_ID, VERCEL_PROJECT_ID, API keys, environment values, claim URLs, deployment logs, and private preview URLs out of public artifacts unless intentionally disclosed. Design, writing, React, and performance reviews can reveal proprietary UI, product copy, documentation strategy, source code, routes, and business priorities to the configured model provider. |
| Prerequisites |
|
|
|
|
| Install | | | | |
| Config | — | — | — | — |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Signals
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.