Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Concise skills rollout: playwright (3 skills, 2 model-invoked)

Open
#6,587 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
43/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
shell
Domain
devtools

Research direction

Read the linked per-plugin runbook at plugins/playbooks/skills/skill-authoring/reference/rewrite-a-plugin.md and the rewrite protocol it cites; the plugin's three skills are check, playwright, and setup. First obtain approval for the /evals:plugin-eval estimate, then follow the runbook to measure and rewrite skills in one draft PR. Done when the PR merges with a per-skill decision table, measured descriptions and bodies, and reasons for any unmeasured skills.

Written by the indexing model from the issue text.

Description

needs-triage priority: medium

Part of #6476. Rewrite playwright's skills to the skill criteria in one draft PR, following the per-plugin runbook (/playbooks:skill-authoring, reference/rewrite-a-plugin.md). The runbook and the rewrite protocol it cites decide what ships; this issue holds only what is specific to the plugin.

The plugin today

  • Skills: check, playwright, setup (user-invoked).
  • Outcome eval cases under evals/: 0. Probe files under probes/: 0.
  • Synced skills here change only in their house-owned parts (umbrella decision).

Done when

  • The PR merges with a per-skill decision table in its body, and every shipped description and body was measured.
  • Any skill left unmeasured, and why, is named in the PR.

Needs a person

  • Approve the eval spend for this plugin (the /evals:plugin-eval estimate) before the measured passes.
  • Review the draft PR and mark it ready.

Generated by Claude Code

Dominant language
Shell
Stars
22
Forks
2
Avg merge
5h 15m
Merged PRs (30d)
833

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from melodic-software/claude-code-plugins

All issues in melodic-software/claude-code-plugins

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.