Want to add your plugin to awesome-ai-plugins?

[zerocodefast]

Hey, we maintain awesome-ai-plugins and came across CloudBase-AI-Toolkit. It looks like a great fit alongside the other gemini cli extensions, and we'd love to include it.

Would you be up for submitting it? The whole submission is a small PR adding one entry to README.md; CONTRIBUTING.md shows the format.

Projects listed there can also receive a public profile in HOL's plugin directory at https://hol.org/registry/plugins, including a dofollow backlink to the project's repository or homepage.

No integration work or ongoing commitment, just the listing. We'd be glad to have it.

[github-actions]

🤖 AI Analysis

Classification

Triage / external listing request (non-issue, no code change required in this repo).

This is not a bug or feature request against CloudBase-AI-Toolkit itself. A maintainer of the third-party awesome-ai-plugins list (by HOL / hashgraph-online) is inviting us to submit a listing PR to their repo. No code, dependency, or behavior change is needed in this repository. It is an opt-in community visibility opportunity.

Likely area

• Project marketing / external ecosystem listing — outside the normal mcp/, config/, doc/ change surfaces.
• Decision owner: repo maintainers (@TencentCloudBase). The work, if accepted, happens in the external repo hashgraph-online/awesome-ai-plugins, not here.
• Per the issue, the only artifact on their side is "a small PR adding one entry to README.md" per their CONTRIBUTING.md. Optionally it yields a public profile + dofollow backlink at https://hol.org/registry/plugins.

Suggested next step

1. Decide whether maintainers want the listing. This is a judgment call about brand/exposure, not engineering. If yes:
2. Open a PR against hashgraph-online/awesome-ai-plugins following their CONTRIBUTING.md format. The entry should describe CloudBase-AI-Toolkit accurately and point to the canonical repo/homepage.
   • Repo: https://github.com/TencentCloudBase/CloudBase-AI-Toolkit
   • Suggested one-line description (adapt to their template): "CloudBase AI Toolkit — MCP server + AI IDE skills/plugins for building, deploying, and operating Tencent CloudBase (cloud-native backend) apps via natural language."
   • If they ask for a category, it fits "MCP servers" / "AI IDE extensions" / "Gemini CLI extensions" (they mention gemini cli extensions).
3. Align with our own docs before submitting: confirm the description matches README.md and doc/index.md so the external listing stays consistent with doc_freshness_rules. The submission references this repo only; no internal file change is mandated.
4. No internal PR needed unless we also want to add a "featured in / listed in awesome-ai-plugins" note to our own README.md — that would be a separate, optional cosmetic change here (follow git_push workflow: feature branch → git push origin HEAD → open PR, do not force-push or push to main).

This issue can be closed as informational once a maintainer replies (accept or decline). No specs/ workflow is required — it is low-risk, boundary-clear, and external.

Open questions

• Do @TencentCloudBase maintainers want the project listed on awesome-ai-plugins / hol.org registry? (The dofollow backlink is a minor SEO benefit but implies a public association.)
• Does the awesome-ai-plugins entry require a specific homepage URL vs. the GitHub repo? Our README.md / doc/index.md should reflect whichever we submit.
• Any policy about linking the project to third-party plugin directories that should be checked before accepting?

Recommendation: Acknowledge the invite in the issue, and either submit the external PR or politely decline. Keep this repo unchanged unless we choose to add a "listed in" badge.

---

Generated automatically by CodeBuddy CLI headless mode.