Skip to content
TrustedSkillsbeta
Back to all skills

Dart Test Fundamentals

Checked
kevmoo·vlatest·testing·Apache-2.0

Helps with Dart, testing as part of agent workflows workflows.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add kevmoo/dash_skills --skill dart-test-fundamentals -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

kevmoo

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned kevmoo/dash_skills at 0b6371c265.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
0b6371c265
Manifest
skills/dart-test-fundamentals/SKILL.md
Scanned
2 files, 232 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill assists AI agents in understanding and implementing Dart testing fundamentals. It covers core concepts like test structure (tests and groups), lifecycle methods (setUp, tearDown, setUpAll, tearDownAll), configuration via dart_test.yaml, and file naming conventions. The skill is intended to help with writing new test files and structuring existing test suites within a Dart project.

When to use it

  • Writing new Dart test files.
  • Structuring tests into logical groups using the group construct.
  • Configuring test execution options, such as platforms and timeouts, in dart_test.yaml.
  • Understanding how lifecycle methods like setUp and tearDown affect test isolation.

Key capabilities

  • Test Structure: Defining tests and organizing them into nested groups.
  • Lifecycle Methods: Utilizing setUp, tearDown, setUpAll, and tearDownAll for managing test state.
  • Configuration: Configuring the Dart test runner through the dart_test.yaml file, including platforms, tags, and timeouts.
  • File Naming: Understanding the required naming convention (*_test.dart) for test files.

Example prompts

  • "Show me how to create a group of tests in Dart."
  • "Explain how to configure timeout settings using dart_test.yaml."
  • "What is the purpose of the setUp method in a Dart test?"

Tips & gotchas

  • Test files must end with _test.dart and reside within the test/ directory to be recognized by the test runner.
  • Avoid wrapping all tests in a single group at the file level.
  • Named parameters for tests (e.g., testOn, timeout) should be placed immediately after the description string for improved readability.