Dokan Run Test Suite

What it does

When your agent uses it

• Inspect the automated test runs
• Execute the QA suite
• Check the failed run should activate this skill

Example prompts

• “run the suite”
• “run e2e tests”
• “trigger CI”
• “/dokan-run-test-suite”

Requirements

• Node.js
• Docker
• A credential in LICENSE_KEY

Workflow steps

8 steps, taken from the step headings in SKILL.md.

1. 1Docker pre-flight
2. 2.env pre-flight
3. 3Environment setup
4. 4Verify required plugins
5. 5Enable the React UI
6. 6Test execution
7. 7Tag conventions
8. 8Inspecting local results

What it can do on your machine

Read from SKILL.md and the folder at commit 63ad893. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  Shell commands in SKILL.md call:

  • npm
  • gh
  • npx
  • docker

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  No URLs in SKILL.md. Its commands use npm, gh, npx and docker, which can reach the network depending on how they are called.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names these keys or tokens, usually read from environment variables:

  • LICENSE_KEY
  • USER_PASSWORD

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Dokan Run Test Suite loads about 4.7k tokens when it runs. Until then it costs about 88 tokens; SKILL.md has 2,057 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~88

When it runs · the whole SKILL.md, loaded when a task matches

~4.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

• NoteRuns commands with sudoSKILL.md:46

  docker info >/dev/null 2>&1 || sudo systemctl start docker

• NoteMentions a .env fileSKILL.md:51

  ### 2. `.env` pre-flight

• NoteMentions a .env fileSKILL.md:53

  tests read configuration from `tests/pw/.env` (loaded via `dotenv`). Without it the helpers fall back to `cd undefined

• NoteMentions a .env fileSKILL.md:55

  reset:env` or any test command, inspect `.env` and resolve every missing key by asking the user. Do not silently scaffol

• NoteMentions a .env fileSKILL.md:59

  | `.env` does not exist | Ask the user for `LICENSE_KEY` (when Pro), `GMAP`, and `USER_PASSWORD` in one bundled `AskUser

• NoteMentions a .env fileSKILL.md:60

  | `.env` exists, `DOKAN_PRO=true`, `LICENSE_KEY=` empty | Stop and ask for the key. License-related Pro tests will fail

• NoteMentions a .env fileSKILL.md:61

  | `.env` exists, `GMAP=` empty | Tell the user explicitly: *all 12 `tests/e2e/geolocation/*` specs will fail without `GM

• NoteMentions a .env fileSKILL.md:62

  | `.env` exists, `USER_PASSWORD=` empty, equal to the `.env.example` placeholder `your_test_password`, or contains no di

• NoteMentions a .env fileSKILL.md:63

  | `.env` exists, all required keys populated | Pass. |

• NoteMentions a .env fileSKILL.md:70

  # Inspect existing .env without printing secret values

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

Without a licence we can't republish the file, so here is its outline and opening line. It has 2,057 words (~4,726 tokens).

name

dokan-run-test-suite

Read the full SKILL.md on GitHub

Files

Just SKILL.md in .claude/skills/dokan-run-test-suite of getdokan/dokan.

Open the folder on GitHubat commit 63ad893