google-agents-cli-scaffold
Project scaffolding, deployment configuration, and CI/CD setup for Google ADK agents.
Identity management and authentication systems. Activate when: (1) Configuring Keycloak realms/clients, (2) Writing OPA policies, (3) Managing Vault secrets, (4) Implementing OIDC/OAuth2 flows, or (5) Setting up RBAC/ABAC authorization.
Full skill instructions
This skill covers identity management, authentication, and authorization using Keycloak, OPA (Open Policy Agent), and HashiCorp Vault.
| Concept | Description |
|---|---|
| Realm | A tenant - isolated namespace for users, clients, roles |
| Client | An application that can request authentication |
| User | An identity that can authenticate |
| Role | A set of permissions |
| Group | A collection of users |
| Identity Provider | External auth source (LDAP, social login) |
# Configure CLI
kcadm.sh config credentials \
--server http://localhost:8080 \
--realm master \
--user admin \
--password admin
# Create realm
kcadm.sh create realms -s realm=myrealm -s enabled=true
# Create client
kcadm.sh create clients -r myrealm \
-s clientId=myapp \
-s enabled=true \
-s publicClient=false \
-s secret=mysecret \
-s 'redirectUris=["http://localhost:8080/*"]' \
-s 'webOrigins=["http://localhost:8080"]'
# Create user
kcadm.sh create users -r myrealm \
-s username=testuser \
-s enabled=true \
-s emailVerified=true \
-s [email protected]
# Set password
kcadm.sh set-password -r myrealm --username testuser --new-password test123
# Create role
kcadm.sh create roles -r myrealm -s name=admin
# Assign role to user
kcadm.sh add-roles -r myrealm --uusername testuser --rolename admin
# Get token (password grant - dev only)
curl -X POST "http://localhost:8080/realms/myrealm/protocol/openid-connect/token" \
-H "Content-Type: application/x-www-form-urlencoded" \
-d "client_id=myapp" \
-d "client_secret=mysecret" \
-d "username=testuser" \
-d "password=test123" \
-d "grant_type=password"
# Introspect token
curl -X POST "http://localhost:8080/realms/myrealm/protocol/openid-connect/token/introspect" \
-H "Content-Type: application/x-www-form-urlencoded" \
-d "client_id=myapp" \
-d "client_secret=mysecret" \
-d "token=<access_token>"
# policy.rego
package authz
import future.keywords.if
import future.keywords.in
default allow := false
# Allow admins everything
allow if {
"admin" in input.user.roles
}
# Allow users to read own resources
allow if {
input.action == "read"
input.resource.owner == input.user.id
}
# Allow read on public resources
allow if {
input.action == "read"
input.resource.public == true
}
# Evaluate policy
opa eval -d policy.rego -i input.json "data.authz.allow"
# Test policies
opa test . -v
# Run as server
opa run --server policy.rego
# Query server
curl -X POST http://localhost:8181/v1/data/authz/allow \
-H "Content-Type: application/json" \
-d '{"input": {"user": {"roles": ["admin"]}}}'
# policy_test.rego
package authz
test_admin_allowed {
allow with input as {
"user": {"roles": ["admin"]},
"action": "delete",
"resource": {"type": "post"}
}
}
test_user_cannot_delete {
not allow with input as {
"user": {"roles": ["user"]},
"action": "delete",
"resource": {"type": "post"}
}
}
# Start dev server
vault server -dev
# Set address
export VAULT_ADDR='http://127.0.0.1:8200'
# Login
vault login <token>
# KV Secrets Engine
vault secrets enable -path=secret kv-v2
vault kv put secret/myapp/config api_key=xxx db_pass=yyy
vault kv get secret/myapp/config
vault kv get -field=api_key secret/myapp/config
# List secrets
vault kv list secret/myapp/
# myapp-policy.hcl
path "secret/data/myapp/*" {
capabilities = ["read", "list"]
}
path "secret/metadata/myapp/*" {
capabilities = ["list"]
}
path "database/creds/myapp" {
capabilities = ["read"]
}
# Create policy
vault policy write myapp myapp-policy.hcl
# List policies
vault policy list
# Enable AppRole
vault auth enable approle
# Create role
vault write auth/approle/role/myapp \
secret_id_ttl=10m \
token_num_uses=10 \
token_ttl=20m \
token_max_ttl=30m \
secret_id_num_uses=40 \
token_policies="myapp"
# Get role ID
vault read auth/approle/role/myapp/role-id
# Generate secret ID
vault write -f auth/approle/role/myapp/secret-id
# Login with AppRole
vault write auth/approle/login \
role_id=<role_id> \
secret_id=<secret_id>
# Enable database secrets engine
vault secrets enable database
# Configure PostgreSQL
vault write database/config/mydb \
plugin_name=postgresql-database-plugin \
connection_url="postgresql://{{username}}:{{password}}@localhost:5432/mydb" \
allowed_roles="readonly" \
username="vault" \
password="vault"
# Create role
vault write database/roles/readonly \
db_name=mydb \
creation_statements="CREATE ROLE \"{{name}}\" WITH LOGIN PASSWORD '{{password}}' VALID UNTIL '{{expiration}}'; GRANT SELECT ON ALL TABLES IN SCHEMA public TO \"{{name}}\";" \
default_ttl="1h" \
max_ttl="24h"
# Get credentials
vault read database/creds/readonly
# Python example with PyJWT
import jwt
from jwt import PyJWKClient
KEYCLOAK_URL = "http://localhost:8080/realms/myrealm"
jwks_client = PyJWKClient(f"{KEYCLOAK_URL}/protocol/openid-connect/certs")
def validate_token(token: str) -> dict:
signing_key = jwks_client.get_signing_key_from_jwt(token)
return jwt.decode(
token,
signing_key.key,
algorithms=["RS256"],
audience="myapp",
issuer=KEYCLOAK_URL
)
# Kubernetes deployment with OPA sidecar
spec:
containers:
- name: app
image: myapp:latest
- name: opa
image: openpolicyagent/opa:latest
args:
- "run"
- "--server"
- "--addr=localhost:8181"
- "/policies"
volumeMounts:
- name: policies
mountPath: /policies
Project scaffolding, deployment configuration, and CI/CD setup for Google ADK agents.
Set up tracing, logging, and monitoring for deployed ADK agents across Cloud Trace, BigQuery, and third-party platforms.
Enterprise Azure infrastructure architect generating Bicep or Terraform from workload descriptions.
Plan and configure production-ready Azure Kubernetes Service clusters with Day-0 and Day-1 best practices.
Raw mechanical interfaces fusing Swiss typographic print with military terminal aesthetics. Rigid grids, extreme type scale contrast, utilitarian color, analog degradation effects. For data-heavy dashboards, portfolios, or editorial sites that need to feel like declassified blueprints.
Web search, scraping, extraction, crawling, and monitoring via ScrapeGraph AI CLI.
Skill for working with Firebase Hosting (Classic). Use this when you want to deploy static web apps, Single Page Apps (SPAs), or simple microservices. Do NOT use for Firebase App Hosting.
Deploy and manage web apps with Firebase App Hosting. Use this skill when deploying Next.js/Angular apps with backends.
Deploy applications and websites to Vercel. Use when the user requests deployment actions like "deploy my app", "deploy and give me the link", "push this live", or "create a preview deployment".
Build SEO-optimized pages at scale using templates, data, and proven playbook patterns.
Design and build isolated, reusable Convex backend components with clear boundaries and app-facing wrappers.
Deploy and manage projects on Vercel using token-based authentication. Use when working with Vercel CLI using access tokens rather than interactive login — e.g. "deploy to vercel", "set up vercel", "add environment variables to vercel".
Opus.ai: Revolutionize Your Web Experience
Build a no-code AI app in minutes.
An IDE for code migration from legacy to modern frameworks through coding agents.
Automate CGI animation in live-action scenes
Branded artistic QR-code concepts
Launch a website in seconds with AI.
Streamline Your Coding Experience with AI Code Helper
Convert any screenshot or design to clean code.