Concise skills rollout: x (1 skills, 1 model-invoked)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
- Issue type
- Feature
- 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; the issue identifies x's sole skill as read, with no eval cases or probes. First get approval for the /evals:plugin-eval estimate, then follow the runbook to measure the skill and prepare a draft PR. Done means the PR includes a per-skill decision table, accounts for every shipped description and body, and names any unmeasured skill and why; request review and mark it ready.
Written by the indexing model from the issue text.
Description
Part of #6476. Rewrite x'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:
read. - Outcome eval cases under
evals/: 0. Probe files underprobes/: 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-evalestimate) 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
- 8h 27m
- Merged PRs (30d)
- 957
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from melodic-software/claude-code-plugins
-
priority: medium
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
melodic-software/claude-code-plugins#7351 · 2 comments ·
Maintainers usually reply within 1 day
-
agent-ready priority: high work-class: scoped
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
melodic-software/claude-code-plugins#7312 · 3 comments ·
Maintainers usually reply within 1 day
-
priority: medium
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
melodic-software/claude-code-plugins#7288 · 2 comments ·
Maintainers usually reply within 1 day
-
knowledge: docpage-digest dual verification defines no verdict vocabulary or pass/fail thresholdOpenneeds-human
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
melodic-software/claude-code-plugins#7286 · 2 comments ·
Maintainers usually reply within 1 day
-
priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
melodic-software/claude-code-plugins#7282 · 2 comments ·
Maintainers usually reply within 1 day
All issues in melodic-software/claude-code-plugins
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
e2e-failure ready-to-code
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
redhat-developer/rhdh-plugin-export-overlays#4391 · 1 comment ·
Maintainers usually reply within 1 day
-
documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
graygarbage/HermesKey#20 ·
-
Version-drift constraint evaluator (#40): validate the candidate version and run its unit test in CIOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
n8n-io/terraform-google-n8n#41 ·
Maintainers usually reply within 5 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100