By vngcloud
Manage the full lifecycle of AI agents on GreenNode AgentBase: scaffold, configure, deploy, monitor, and teardown agents with identity, authentication, memory, and gateway management.
Deploy and operate AI agents on GreenNode AgentBase. Supports two resource types: Custom Agent (user-built Docker image, /agent-runtimes) and OpenClaw (platform templates for Telegram/Zalo bots, /openclaws). Part 1 — Deploy Custom Agent (build, push, create/update runtime in PUBLIC or VPC mode). Trigger: deploy my agent, ship it, redeploy, deploy in VPC. Part 2 — Custom Agent runtime management (endpoints, scaling, versions, network mode). Trigger: list runtimes, scale, delete runtime, list flavors. Part 3 — OpenClaw (Telegram/Zalo bot templates). Trigger: deploy a Telegram bot, deploy a Zalo bot, create/list/start/stop OpenClaw, switch OpenClaw version. Part 4 — Container Registry (managed Docker repo, credentials, images, artifacts). Trigger: get repo info, docker login, push image, list/delete images. DO NOT use for non-AI-agent apps. For logs/metrics use /agentbase-monitor.
Manage GreenNode AgentBase Resource Gateway (MCP) — a managed proxy in front of user MCP servers with inbound auth, per-target outbound auth, and policy enforcement. Trigger: create/list/update/delete a gateway, register an MCP target, configure inbound auth (NONE/IAM/JWT) or per-target outbound auth (APIKEY/OAUTH, each with 2LO or 3LO flow), change VPC routes, bind a Policy Group. DO NOT use for agent runtimes (/agentbase-deploy) or for authoring policy rules (/agentbase-policy).
Register agent identities and manage outbound authentication providers for AI agents. Covers CRUD for agent identities, storing API keys or secrets for external services (OpenAI, Google, Slack), OAuth2 providers, and delegated keys. When user mentions an external service name with API key or credentials, trigger this skill — not /agentbase-llm. DO NOT use for agent source code (use /agentbase-wizard), platform LLM API keys (use /agentbase-llm), agent memory (use /agentbase-memory), or runtime logs (use /agentbase-monitor).
Manage platform LLM model access and API keys for AI agents. Use when user wants to set up LLM access, get a platform API key, browse available models, choose which LLM to use, configure model access, check rate limits, or get an OpenAI-compatible endpoint. Trigger for which models are available, set up LLM, API key for the model, list models, LLM key, connect to LLM. When user says API key without specifying an external service name, default to this skill. DO NOT use for storing API keys for external services (OpenAI, Google, Slack) — use /agentbase-identity instead.
Add memory to AI agents — conversation history, semantic fact extraction, and long-term memory records. Covers creating memory stores, managing events/sessions, memory records, long-term memory strategies (SEMANTIC, USER_PREFERENCE, CUSTOM), and LangChain/LangGraph memory integration. DO NOT use for agent source code (use /agentbase-wizard), agent identity or outbound auth (use /agentbase-identity), platform LLM API keys (use /agentbase-llm), or runtime logs (use /agentbase-monitor).
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimnpx claudepluginhub vngcloud/greennode-agentbase-skills --plugin greennode-agentbaseBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
A bundle of SKILL.md-compatible skills that drive the full GreenNode AgentBase lifecycle — scaffold → configure → code → test → deploy → monitor → teardown — from inside your AI coding tool.
Drop them into Claude Code, Cursor, OpenAI Codex, or any other SKILL.md-aware client and you get slash commands like /agentbase-wizard, /agentbase-deploy, /agentbase-monitor. The skills are plain Markdown + shell — no client-specific runtime — so the full lifecycle works in every tool that can read SKILL.md and run a shell.
claude plugin marketplace add vngcloud/greennode-agentbase-skills
Then inside Claude Code:
/plugin install greennode-agentbase@greennode-agentbase
Team distribution — add to your project's .claude/settings.json so teammates are prompted to install automatically:
{
"extraKnownMarketplaces": {
"greennode-agentbase": {
"source": { "source": "github", "repo": "vngcloud/greennode-agentbase-skills" }
}
}
}
Add to ~/.codex/config.toml:
[plugins]
greennode-agentbase = { source = "github:vngcloud/greennode-agentbase-skills" }
Cursor CLI (any plan) — inside a Cursor CLI session:
/plugin
Then paste the repo URL: https://github.com/vngcloud/greennode-agentbase-skills.git
Cursor IDE (Team/Enterprise) — Dashboard → Settings → Plugins → Add Marketplace → Import from GitHub: vngcloud/greennode-agentbase-skills
git clone https://github.com/vngcloud/greennode-agentbase-skills.git
cp -r greennode-agentbase-skills/skills/* <your-tool-skills-dir>/
| Tool | Install method | Shell scripts supported |
|---|---|---|
| Claude Code | /plugin install via marketplace | Yes |
| Codex CLI | config.toml plugin entry | Yes |
| Cursor CLI | /plugin + Git URL | Yes |
| Cursor IDE | Team/Enterprise marketplace | Yes |
Before any skill that hits the platform, set GreenNode IAM credentials:
export GREENNODE_CLIENT_ID="<service-account-client-id>"
export GREENNODE_CLIENT_SECRET="<service-account-secret>"
Put them in your shell profile or in a project-local .env (never commit it — .env.example is the tracked template).
Skills that only read local files (e.g. agentbase-wizard init) work without credentials.
| Skill | What it does |
|---|---|
/agentbase-wizard | Start here. Guided 9-step lifecycle: scaffold → configure → code → test → deploy → verify. Also handles init, test, resume. |
/agentbase | Platform reference — architecture, services, IAM, "which skill should I use". |
/agentbase-identity | Register agent identities; store API keys / OAuth2 credentials for external services (OpenAI, Google, Slack, …). |
/agentbase-llm | Manage platform LLM access — API keys, model catalog, rate limits, OpenAI-compatible endpoint. |
/agentbase-memory | Conversation history, semantic memory, long-term memory stores (LangChain/LangGraph integration). |
/agentbase-deploy | Build & push Docker image, create/update Custom Agent runtimes (PUBLIC/VPC), deploy OpenClaw Telegram/Zalo bots, manage the Container Registry. |
/agentbase-monitor | Runtime logs, endpoint logs, CPU/RAM metrics, unified resource dashboard. |
/agentbase-gateway | Resource Gateway (MCP) CRUD; inbound auth (NONE / IAM / JWT); per-target outbound auth (APIKEY / OAUTH 2LO / 3LO); VPC routes; Policy Group binding. |
/agentbase-policy | Authorization policies — Policy Groups, Policies, and statement bodies (effect / principal / actions / resources / condition). Enforced today on the Resource Gateway. |
/agentbase-teardown | Delete all resources for a project. Always supports --dry-run. |
Scaffold, develop, evaluate, and deploy AI agents with Google ADK. Bundles 7 skills for the agent development lifecycle.
Production ADK orchestrator for A2A protocol and multi-agent coordination on Vertex AI
Connect Claude Code to the Viche agent network — discover, message, and collaborate with other AI agents in real-time
Build, deploy, and operate AI agents on AWS. Skills for scaffolding agents with Amazon Bedrock AgentCore (Strands, LangGraph), connecting tools via Gateway and MCP, multi-agent and A2A orchestration, memory, Cedar policies, evaluation, observability, debugging traces and logs, and production hardening (inbound auth, IAM, rate limiting, cold-start tuning).
Portable, vendor-agnostic agent harness for project-specific skills, workflows, and agent teams aligned with your codebase, conventions, and engineering standards.
Build, configure, and deploy AI agents using the Motus framework. The single /motus plugin includes guided agent creation and local or cloud deployment.