Concise skills rollout: attribution (2 skills, 1 model-invoked)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- shell
- Domain
- ai-infra-agents
Research direction
Read the 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 attribution skill files. Start by reviewing the audit and setup skills and their eval/probe coverage, then get approval for the eval spend before measured passes. Done means a merged draft PR with a per-skill decision table, measured shipped descriptions and bodies, and reasons for any unmeasured skills; a person must review it and mark it ready.
Written by the indexing model from the issue text.
Description
Part of #6476. Rewrite attribution'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:
audit,setup(user-invoked). - 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
- 5h 18m
- Merged PRs (30d)
- 869
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
-
good first issue needs-triage priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
melodic-software/claude-code-plugins#6699 · 1 comment ·
Maintainers usually reply within 1 day
-
good first issue needs-triage priority: medium
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
melodic-software/claude-code-plugins#6631 · 1 comment ·
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
melodic-software/claude-code-plugins#6547 ·
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
melodic-software/claude-code-plugins#6535 ·
Maintainers usually reply within 1 day
-
test_comment_census.py: SccArgv flag-shaped-filename test errors on Windows (#!/bin/sh scc shim)Opengood first issue needs-triage priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
melodic-software/claude-code-plugins#6532 · 1 comment ·
Maintainers usually reply within 1 day
All issues in melodic-software/claude-code-plugins
Similar issues
-
priority middle
Difficulty 1/5 Under an hour Newbie friendliness 72/100
KATO-Hiro/AtCoderClans#12838 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
heymegabyte/install.doctor#171 ·
-
area:cli bug
Difficulty 1/5 Under an hour Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
community-scripts/ProxmoxVE#17824 ·
Maintainers usually reply within 1 day
-
agent: ready area: submission priority: high type: docs
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
dkritarth/scopewatch#213 ·
Maintainers usually reply within 1 day