anthropics / anthropics/claude-plugins-official
[Question] Plugin submission "Relevio" pending review since July 18
- Vorherrschende Sprache
- Python
- Sterne
- 36.3k
- Forks
- 4.1k
- Ø Merge
- 2 T. 14 Std.
- Gemergte PRs (30 T.)
- 539
Beschreibung
Hi team,
I submitted a Claude Code plugin called "Relevio" through the Console submission form (platform.claude.com/plugins/submissions). It still shows "Submitted and pending review" and hasn't appeared in the community marketplace.json yet. I'd like to get a status update, and I want to flag a couple of things that might be holding it up.
Details:
- Plugin name: Relevio
- First submitted: July 18
- Submitted again: July 28
- Organization ID: 351f2c19-2a96-4e7f-b9d7-4aafa55984e8
- Current status in Console: "Submitted and pending review" (both entries)
Two things I'd like to clarify:
1. There are two Relevio entries in my submissions list, both pending. The second was a re-submission, so one is effectively a duplicate. Could you tell me which one to keep, and confirm the duplicate isn't blocking the review?
2. I had been pushing new commits to the plugin's repository while it was in review. I've now frozen the repo on a stable version and won't push further changes until this is resolved, in case ongoing commits were resetting or stalling the review.
Could you let me know whether Relevio is genuinely in the review queue, or if there's anything I need to fix on my end (validation, manifest, repo access)? I ran `claude plugin validate` locally and it passes.
Thanks for taking a look.
Beitragsleitfaden
Für dieses Repository ist kein Beitragsleitfaden indexiert
Rechercherichtung
Start with the Console submission form and the plugin marketplace.json entry mentioned in the issue, then verify the result of `claude plugin validate`. Determine whether the two Relevio submissions are duplicates, whether either is in the review queue, and whether the submitter needs to change validation, manifest, or repository access; done means a clear status or an identified blocker.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Bereich
- release
- Issue-Typ
- Bug
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Ruhig
- Klarheit
- Muss geklärt werden
- Anfängerfreundlichkeit
- 25/100