New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Dokan Automation

by getdokan in getdokan/dokan

Build, scaffold, and run the Dokan Lite/Pro Playwright suite.

No licenceAuto-check: notesTesting & QA

Install Dokan Automation

skills CLI
$ npx skills add getdokan/dokan --skill dokan-automation -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install getdokan/dokan dokan-automation --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/getdokan/dokan.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/dokan-automation .claude/skills/dokan-automation && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
dokan-automation
GitHub stars
288
Token cost
~6.1k tokens
SKILL.md length
2,917 words
Files
1
Skills in repo
9
Repo updated
First seen
Licence
None found

At a glance

Build, scaffold, and run the Dokan Lite/Pro Playwright suite.

  • Works in 12 steps: confirm intent → interview → collect scenarios, sectioned → …
  • The user asks to add tests for a feature
  • SKILL.md covers Non-negotiables (apply to…, Quick orientation, Detecting which flow to run and AUTHOR FLOW, plus 5 more sections
  • Calls npm, npx and docker; needs USER_PASSWORD and LICENSE_KEY

What it does

Dokan Automation is an agent skill from getdokan/dokan. Build, scaffold, and run the Dokan Lite/Pro Playwright suite. Use when the user asks to add tests for a feature, scaffold from test-cases.md, or run the automation suite (Lite Only / PR / Full). Knows the folderized format, tag system, Docker / wp-env preconditions, and the .env / license-key requirements for Pro runs.

Its SKILL.md is about 6.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA, covering Test generation, Browser testing and Containers. It works with Playwright and Docker. The repository describes itself as: Multivendor marketplace platform for WordPress.

When your agent uses it

  • The user asks to add tests for a feature
  • Scaffold from test-cases.md
  • Run the automation suite (Lite Only / PR / Full)

Example prompts

  • “/dokan-automation”

Requirements

  • Node.js
  • Docker

Workflow steps

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

  1. confirm intent
  2. interview
  3. collect scenarios, sectioned
  4. write the block
  5. confirm and hand off
  6. read inputs
  7. confirm the plan
  8. validate sections
  9. scaffold per feature
  10. verify the scaffold
  11. report
  12. ask which suite

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
    • 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, 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:

    • USER_PASSWORD
    • LICENSE_KEY
    • ADMIN_PASSWORD

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

Context cost

Dokan Automation loads about 6.1k tokens when it runs. Until then it costs about 84 tokens; SKILL.md has 2,917 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~84
When it runs · the whole SKILL.md, loaded when a task matches
~6.1k

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

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:7
    , Docker / wp-env preconditions, and the .env / license-key
  • NoteMentions a .env fileSKILL.md:17
    (Lite Only / PR / Full), verify Docker, `.env`, and license preconditions, then invoke the right `npm` script.
  • NoteMentions a .env fileSKILL.md:302
    ### Step 3 — `.env` check
  • NoteMentions a .env fileSKILL.md:304
    Path: `$SUITE_ROOT/.env`.
  • NoteMentions a .env fileSKILL.md:308
    2. Tell the user `.env is missing. I'll create it from .env.example.`
  • NoteMentions a .env fileSKILL.md:321
    `Write` the file. Do not commit it — `.env` is gitignored.
  • NoteMentions a .env fileSKILL.md:329
    1. Grep `LICENSE_KEY=` in `$SUITE_ROOT/.env`. If empty or set to the placeholder `your_dokan_pro_license_key`, ask:
  • NoteMentions a .env fileSKILL.md:333
    user provides a key, write it back into `.env` via `Edit`.
  • NoteMentions a .env fileSKILL.md:348
    If the user's `.env` already has `NO_SETUP=true` AND they confirm the environment is already seeded, you may skip `docke
  • NoteMentions a .env fileSKILL.md:383
    2. **Never commit `.env`.** It's gitignored. Writing it locally is fine; committing it is not.

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,917 words (~6,121 tokens).

“A QA-facing skill for the Dokan Playwright suite. Three flows:”

— opening of SKILL.md by getdokan
name
dokan-automation

Read the full SKILL.md on GitHub

Files

Just SKILL.md in .claude/skills/dokan-automation of getdokan/dokan.

Open the folder on GitHubat commit 63ad893

Compare with similar skills

Dokan Automation next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Dokan Automation compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Dokan Automation this skillgetdokan/dokan288—~6.1kAutomated safety check: NotesNone
Dozzle Visual Snapshot Updateramir20/dozzle15k—~797Automated safety check: PassMIT
E2Eopenathleteorg/openathlete101—~699Automated safety check: PassAGPL-3.0
Testing Orcaqcin12211/orca-q224—~1.6kAutomated safety check: PassMIT
Run Dashboard E2E Local ChangesBlackBeltTechnology/pi-agent-dashboard315—~1.3kAutomated safety check: PassMIT
Acarshub Tool Additionssdr-enthusiasts/docker-acarshub117—~707Automated safety check: PassGPL-3.0

Similar skills

  • Dozzle Visual Snapshot Updater

    amir20/dozzle

    Regenerates Playwright visual snapshots for Dozzle after an intentional UI change, running them through Docker Compose so filenames match the Linux CI platform.

    15k GitHub stars~797 tokensUpdated today
    Testing & QAAuto-check passed

  • E2E

    openathleteorg/openathlete

    Run, debug or extend the OpenAthlete Playwright end-to-end tests, which exercise the production Docker images (API, worker, web, PostgreSQL, Redis) through the API and a real browser on desktop and…

    101 GitHub stars~699 tokensUpdated today
    Testing & QAAuto-check passed

  • Testing Orcaq

    cin12211/orca-q

    OrcaQ-specific testing guide. An agent skill from cin12211/orca-q.

    224 GitHub stars~1.6k tokensUpdated 18 days ago
    Testing & QAAuto-check passed

  • Run Dashboard E2E Local Changes

    BlackBeltTechnology/pi-agent-dashboard

    Run Playwright E2E (tests/e2e/) against the docker/ all-in-one harness so it reflects LOCAL code changes, not a stale cached image.

    315 GitHub stars~1.3k tokensUpdated today
    Testing & QAAuto-check passed

  • Acarshub Tool Additions

    sdr-enthusiasts/docker-acarshub

    Use ONLY when working in the docker-acarshub repository AND a task may require adding a system tool, npm package, or other dependency.

    117 GitHub stars~707 tokensUpdated 2 days ago
    DevOps & CloudAuto-check passed

  • Verifier Web

    polarsource/polar

    Evidence-capture protocol for verifying web/dashboard/backoffice/checkout changes in the Polar local stack by driving the real UI with Playwright.

    10k GitHub stars~3k tokensUpdated yesterday
    Data & AnalyticsAuto-check: notes

More from getdokan/dokan

All 9 skills in this repo

  • Dokan Backend Dev

    getdokan/dokan

    Add or modify Dokan backend PHP code following project conventions.

    288 GitHub stars~4.9k tokensUpdated yesterday
    Auto-check passed

  • Dokan Code Review

    getdokan/dokan

    Review Dokan code changes and pull requests for coding standards, security, and architectural compliance.

    288 GitHub stars~3.2k tokensUpdated yesterday
    Auto-check passed

  • Dokan Dev Cycle

    getdokan/dokan

    Run tests, linting, and quality checks for Dokan development.

    288 GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed

  • Dokan Frontend Dev

    getdokan/dokan

    Add or modify Dokan frontend code (React, TypeScript, Vue, Tailwind).

    288 GitHub stars~1.9k tokensUpdated yesterday
    Auto-check passed

  • Dokan Run Test Suite

    getdokan/dokan

    Execute the Dokan Playwright test suite (E2E + API), locally or via GitHub Actions.

    288 GitHub stars~4.7k tokensUpdated yesterday
    Auto-check: notes

  • Dokan Settings

    getdokan/dokan

    Implementation patterns for the Dokan admin settings system — flat-array schema, single-option storage, and @wedevs/plugin-ui rendering.

    288 GitHub stars~3.5k tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Dokan Automation

What does Dokan Automation do?

Build, scaffold, and run the Dokan Lite/Pro Playwright suite. Dokan Automation is an agent skill from getdokan/dokan. Build, scaffold, and run the Dokan Lite/Pro Playwright suite.

When should I use Dokan Automation?

Dokan Automation fits situations like: the user asks to add tests for a feature; scaffold from test-cases.md; run the automation suite (Lite Only / PR / Full).

How do I install Dokan Automation in Claude Code?

Run `npx skills add getdokan/dokan --skill dokan-automation -a claude-code`. Or copy the skill folder (.claude/skills/dokan-automation in getdokan/dokan) into .claude/skills/dokan-automation in your project. Claude Code loads it when a task matches its description.

How do I install Dokan Automation in Codex?

Run `npx skills add getdokan/dokan --skill dokan-automation -a codex`. Or copy the skill folder (.claude/skills/dokan-automation in getdokan/dokan) into .agents/skills/dokan-automation in your project. Codex loads it when a task matches its description.

Can I use Dokan Automation in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add getdokan/dokan --skill dokan-automation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/dokan-automation, .gemini/skills/dokan-automation, .github/skills/dokan-automation and .opencode/skills/dokan-automation in your project.

What does Dokan Automation need to run?

Going by SKILL.md and its folder, Dokan Automation needs the command-line tools its instructions call (npm, npx and docker) and credentials named USER_PASSWORD, LICENSE_KEY and ADMIN_PASSWORD. Our summary lists: Node.js; Docker.

Does Dokan Automation access the network?

SKILL.md contains no URLs. Its commands use npm, npx and docker, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Dokan Automation safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Dokan Automation use?

No licence was found for Dokan Automation or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.

How many tokens does Dokan Automation use?

About 6.1k tokens (SKILL.md is roughly 24k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Dokan Automation?

Skills that share tags, products or a category with Dokan Automation: Dozzle Visual Snapshot Updater (amir20/dozzle, 15k stars), E2E (openathleteorg/openathlete, 101 stars), Testing Orcaq (cin12211/orca-q, 224 stars) and Run Dashboard E2E Local Changes (BlackBeltTechnology/pi-agent-dashboard, 315 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Dokan Automation?

getdokan (a GitHub organization) maintains it in getdokan/dokan, which has 288 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 9, 2026.

Source: getdokan/dokan on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.