name	webdriverio-webdriverio
description	Triage playbook for github.com/webdriverio/webdriverio issues. Load whenever classifying, labeling, duplicate-checking, investigating, or commenting on issues in that repository. Encodes maintainer best practices learned from historical triage.

webdriverio/webdriverio — Issue Triage Skill

Use this skill for every triage turn on webdriverio/webdriverio.

Read the references as needed (do not skip the playbook on first touch of a thread):

Reference	When
references/triage-playbook.md	Always — decision rules, labels, tone
references/recurring-themes.md	Before duplicate search / investigation
references/historical-examples.md	When unsure how maintainers handled a similar case

Quick rules (from real maintainer practice)

Thank first, ask second — short thanks + one concrete ask beats a checklist dump.
Repro before deep dig — if there is no forkable repo/gist, ask for one and add Reproducible Example Missing. Do not invent a reproduction.
Duplicates are blunt and linked — preferred shape: Duplicate of #N plus one sentence. Close only when confidence is high. Re-open if wrong (maintainers do).
“Closing in favor of” — when a newer tracking issue supersedes an older one, close the older with an explicit link (e.g. Appium work moved to a dedicated issue).
Upstream honesty — Chrome/Gecko/Appium/Node bugs get Driver Releated (exact spelling) or a clear “outside WDIO” explanation; still welcome workarounds/docs.
Invite contributions lightly — “Any contributions are welcome” / “want to raise a PR?” for docs and easy bugs. Mention expensable contributions via Open Collective; do not invent dollar amounts unless an Expensable $… label is already present.
Remove Needs Triaging ⏳ after your pass, even when waiting on the author.
Support ≠ bug — usage questions → Discord (https://discord.webdriver.io) or a short doc pointer; do not keep pure support threads open as bugs.

Repo facts

Issue templates auto-add Needs Triaging ⏳ plus type labels (Bug 🐛, Docs 📖, Idea 💡, …).
Changelog PR labels (PR: …) are out of scope (different agent).
Expense workflow is maintainer-driven (.github/workflows/expense.yml); bot suggests, maintainers apply Expensable $….
Primary checkout in the sandbox: workspace/webdriverio.

After loading

Continue with the global pipeline in /instructions.md, refined by this skill’s references.

webdriverio/webdriverio — Issue Triage Skill

Use this skill for every triage turn on webdriverio/webdriverio.

Read the references as needed (do not skip the playbook on first touch of a thread):

Reference

When

references/triage-playbook.md

Always — decision rules, labels, tone

references/recurring-themes.md

Before duplicate search / investigation

references/historical-examples.md

When unsure how maintainers handled a similar case

Quick rules (from real maintainer practice)

Thank first, ask second — short thanks + one concrete ask beats a checklist dump.

Repro before deep dig — if there is no forkable repo/gist, ask for one and add Reproducible Example Missing. Do not invent a reproduction.

Duplicates are blunt and linked — preferred shape: Duplicate of #N plus one sentence. Close only when confidence is high. Re-open if wrong (maintainers do).

“Closing in favor of” — when a newer tracking issue supersedes an older one, close the older with an explicit link (e.g. Appium work moved to a dedicated issue).

Upstream honesty — Chrome/Gecko/Appium/Node bugs get Driver Releated (exact spelling) or a clear “outside WDIO” explanation; still welcome workarounds/docs.

Invite contributions lightly — “Any contributions are welcome” / “want to raise a PR?” for docs and easy bugs. Mention expensable contributions via Open Collective; do not invent dollar amounts unless an Expensable $… label is already present.

Remove Needs Triaging ⏳ after your pass, even when waiting on the author.

Support ≠ bug — usage questions → Discord (https://discord.webdriver.io) or a short doc pointer; do not keep pure support threads open as bugs.

Repo facts

Issue templates auto-add Needs Triaging ⏳ plus type labels (Bug 🐛, Docs 📖, Idea 💡, …).

Changelog PR labels (PR: …) are out of scope (different agent).

Expense workflow is maintainer-driven (.github/workflows/expense.yml); bot suggests, maintainers apply Expensable $….

Primary checkout in the sandbox: workspace/webdriverio.

After loading

Continue with the global pipeline in /instructions.md, refined by this skill’s references.

webdriverio-webdriverio