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

Concise skills rollout: computer-use (2 skills, 1 model-invoked)

Open
  • Is something wrong?
#6,601 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
35/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Active
Tech stack
shell
Domain
ai-infra-agents

Research direction

Start with the linked per-plugin runbook at plugins/playbooks/skills/skill-authoring/reference/rewrite-a-plugin.md and the rewrite protocol it cites; this issue does not name the computer-use skill file paths. First get approval for the /evals:plugin-eval estimate, then review the existing diagnose and setup skills and their eval/probe coverage. Done when a draft PR has a per-skill decision table, measured descriptions and bodies for shipped skills, and names any unmeasured skills and why; the draft also needs review before it is marked ready.

Written by the indexing model from the issue text.

Description

needs-triage priority: low

Part of #6476. Rewrite computer-use'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: diagnose, setup (user-invoked).
  • Outcome eval cases under evals/: 0. Probe files under probes/: 0.

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
6h 10m
Merged PRs (30d)
937

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.