chore: add listing metadata for the Claude plugin directory
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 75/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- dart
- Domain
- developer-experience
Research direction
Start by inspecting plugin.json and the plugin folder structure to choose where the icon asset belongs. Create a square PNG between 512 and 2048 px and under 2 MB, then set icon and displayName in the manifest. Run claude plugin validate . with Claude Code 2.1.281 or newer and check that CI/CD passes.
Written by the indexing model from the issue text.
Description
Description
plugin.json already carries everything the directory requires: name, description, author, version and license. Two optional listing fields are still missing:
icon: the directory reads it fromplugin.jsonfor the listing. The plugin has no icon today, so the listing would show a generic placeholder.displayName: the label shown in place ofname. Without it, the listing showsvgv-ffca-plugin.
Requirements
- A square PNG of 512 to 2048 px and under 2 MB inside the plugin folder, for example
assets/icon.png -
iconinplugin.jsonpoints to it, for example"icon": "./assets/icon.png" -
displayNameset inplugin.json, for example "VGV FFCA" -
claude plugin validate .reports no new warnings. Claude Code versions before2.1.281warnUnknown fieldforicon, so CI needs that version or newer - All CI/CD checks are passing
Additional Context
- Dominant language
- Dart
- Stars
- 7
- Forks
- 2
- Avg merge
- 9h 59m
- Merged PRs (30d)
- 7
Getting set up
- No Dockerfile or Docker Compose file
- Has a 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 VeryGoodOpenSource/vgv-ffca-plugin
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
chore
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 76/100
-
feature
Difficulty 3/5 1-2 days Newbie friendliness 48/100
All issues in VeryGoodOpenSource/vgv-ffca-plugin
Similar issues
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
StabilityNexus/Zplit#77 · 1 comment ·
-
🚀 [firebase_core] Bump Firebase C++ SDK (14.1.0 → 14.2.0)Possibly taken @SelaseKay claimed this today. OpenNeeds Attention type: enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
firebase/flutterfire#18977 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
-
agent: is checked on a wrapper holding several checkables answers from the first one in tree orderOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
AlphaWaveSystems/flutter-probe#865 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
ubuntu/app-center#2306 ·
Maintainers usually reply within 1 day