Skip to content

Add picoads - AI Agent Ad Marketplace #293

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ililic wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Add picoads - AI Agent Ad Marketplace #293

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions index.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -230,6 +230,7 @@
"@mazzz/plugin-elizaos-compchembridge": "github:Mazzz-zzz/plugin-elizaos-compchembridge",
"@nuggetslife/plugin-nuggets": "github:NuggetsLtd/eliza-plugin-nuggets",
"@onbonsai/plugin-bonsai": "github:onbonsai/plugin-bonsai",
"@picoads/eliza-plugin": "github:picoads/eliza-plugin",
Copy link

@greptile-apps greptile-apps bot Mar 12, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Generic plugin name deviates from registry convention

Most entries in this registry follow the @org/plugin-<functionality> naming pattern (e.g. @mazzz/plugin-elizaos-compchembridge, @nuggetslife/plugin-nuggets, @onbonsai/plugin-bonsai). Both the NPM package name and the GitHub repo here use the suffix eliza-plugin, which is generic and doesn't communicate what the plugin actually does (Ad Marketplace / PicoAds).

A more descriptive name such as @picoads/plugin-picoads or @picoads/plugin-ads would better align with the convention and make the registry entry self-documenting. There is a precedent with @proofgate/eliza-plugin, but that shouldn't prevent new entries from following the preferred pattern.

Consider renaming the NPM package and GitHub repo before merging.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

"@proofgate/eliza-plugin": "github:ProofGate/proofgate-eliza-plugin",
"@pyboom/plugin-moralis-v2": "github:matteo-brandolino/plugin-moralis-v2",
"@standujar/plugin-composio": "github:standujar/plugin-composio",
Expand Down