gkt-node 3.3.0

package/assets/.agent/skills/jira-automation/SKILL.md

@@ -0,0 +1,185 @@
+---
+name: jira-automation
+description: "Automate Jira tasks via Rube MCP (Composio): issues, projects, sprints, boards, comments, users. Always search tools first for current schemas."
+requires:
+  mcp: [rube]
+---
+
+# Jira Automation via Rube MCP
+
+Automate Jira operations through Composio's Jira toolkit via Rube MCP.
+
+## Prerequisites
+
+- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
+- Active Jira connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `jira`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `jira`
+3. If connection is not ACTIVE, follow the returned auth link to complete Jira OAuth
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Search and Filter Issues
+
+**When to use**: User wants to find issues using JQL or browse project issues
+
+**Tool sequence**:
+1. `JIRA_SEARCH_FOR_ISSUES_USING_JQL_POST` - Search with JQL query [Required]
+2. `JIRA_GET_ISSUE` - Get full details of a specific issue [Optional]
+
+**Key parameters**:
+- `jql`: JQL query string (e.g., `project = PROJ AND status = "In Progress"`)
+- `maxResults`: Max results per page (default 50, max 100)
+- `startAt`: Pagination offset
+- `fields`: Array of field names to return
+- `issueIdOrKey`: Issue key like 'PROJ-123' for GET_ISSUE
+
+**Pitfalls**:
+- JQL field names are case-sensitive and must match Jira configuration
+- Custom fields use IDs like `customfield_10001`, not display names
+- Results are paginated; check `total` vs `startAt + maxResults` to continue
+
+### 2. Create and Edit Issues
+
+**When to use**: User wants to create new issues or update existing ones
+
+**Tool sequence**:
+1. `JIRA_GET_ALL_PROJECTS` - List projects to find project key [Prerequisite]
+2. `JIRA_GET_FIELDS` - Get available fields and their IDs [Prerequisite]
+3. `JIRA_CREATE_ISSUE` - Create a new issue [Required]
+4. `JIRA_EDIT_ISSUE` - Update fields on an existing issue [Optional]
+5. `JIRA_ASSIGN_ISSUE` - Assign issue to a user [Optional]
+
+**Key parameters**:
+- `project`: Project key (e.g., 'PROJ')
+- `issuetype`: Issue type name (e.g., 'Bug', 'Story', 'Task')
+- `summary`: Issue title
+- `description`: Issue description (Atlassian Document Format or plain text)
+- `issueIdOrKey`: Issue key for edits
+
+**Pitfalls**:
+- Issue types and required fields vary by project; use GET_FIELDS to check
+- Custom fields require exact field IDs, not display names
+- Description may need Atlassian Document Format (ADF) for rich content
+
+### 3. Manage Sprints and Boards
+
+**When to use**: User wants to work with agile boards, sprints, and backlogs
+
+**Tool sequence**:
+1. `JIRA_LIST_BOARDS` - List all boards [Prerequisite]
+2. `JIRA_LIST_SPRINTS` - List sprints for a board [Required]
+3. `JIRA_MOVE_ISSUE_TO_SPRINT` - Move issue to a sprint [Optional]
+4. `JIRA_CREATE_SPRINT` - Create a new sprint [Optional]
+
+**Key parameters**:
+- `boardId`: Board ID from LIST_BOARDS
+- `sprintId`: Sprint ID for move operations
+- `name`: Sprint name for creation
+- `startDate`/`endDate`: Sprint dates in ISO format
+
+**Pitfalls**:
+- Boards and sprints are specific to Jira Software (not Jira Core)
+- Only one sprint can be active at a time per board
+
+### 4. Manage Comments
+
+**When to use**: User wants to add or view comments on issues
+
+**Tool sequence**:
+1. `JIRA_LIST_ISSUE_COMMENTS` - List existing comments [Optional]
+2. `JIRA_ADD_COMMENT` - Add a comment to an issue [Required]
+
+**Key parameters**:
+- `issueIdOrKey`: Issue key like 'PROJ-123'
+- `body`: Comment body (supports ADF for rich text)
+
+**Pitfalls**:
+- Comments support ADF (Atlassian Document Format) for formatting
+- Mentions use account IDs, not usernames
+
+### 5. Manage Projects and Users
+
+**When to use**: User wants to list projects, find users, or manage project roles
+
+**Tool sequence**:
+1. `JIRA_GET_ALL_PROJECTS` - List all projects [Optional]
+2. `JIRA_GET_PROJECT` - Get project details [Optional]
+3. `JIRA_FIND_USERS` / `JIRA_GET_ALL_USERS` - Search for users [Optional]
+4. `JIRA_GET_PROJECT_ROLES` - List project roles [Optional]
+5. `JIRA_ADD_USERS_TO_PROJECT_ROLE` - Add user to role [Optional]
+
+**Key parameters**:
+- `projectIdOrKey`: Project key
+- `query`: Search text for FIND_USERS
+- `roleId`: Role ID for role operations
+
+**Pitfalls**:
+- User operations use account IDs (not email or display name)
+- Project roles differ from global permissions
+
+## Common Patterns
+
+### JQL Syntax
+
+**Common operators**:
+- `project = "PROJ"` - Filter by project
+- `status = "In Progress"` - Filter by status
+- `assignee = currentUser()` - Current user's issues
+- `created >= -7d` - Created in last 7 days
+- `labels = "bug"` - Filter by label
+- `priority = High` - Filter by priority
+- `ORDER BY created DESC` - Sort results
+
+**Combinators**:
+- `AND` - Both conditions
+- `OR` - Either condition
+- `NOT` - Negate condition
+
+### Pagination
+
+- Use `startAt` and `maxResults` parameters
+- Check `total` in response to determine remaining pages
+- Continue until `startAt + maxResults >= total`
+
+## Known Pitfalls
+
+**Field Names**:
+- Custom fields use IDs like `customfield_10001`
+- Use JIRA_GET_FIELDS to discover field IDs and names
+- Field names in JQL may differ from API field names
+
+**Authentication**:
+- Jira Cloud uses account IDs, not usernames
+- Site URL must be configured correctly in the connection
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| Search issues (JQL) | JIRA_SEARCH_FOR_ISSUES_USING_JQL_POST | jql, maxResults |
+| Get issue | JIRA_GET_ISSUE | issueIdOrKey |
+| Create issue | JIRA_CREATE_ISSUE | project, issuetype, summary |
+| Edit issue | JIRA_EDIT_ISSUE | issueIdOrKey, fields |
+| Assign issue | JIRA_ASSIGN_ISSUE | issueIdOrKey, accountId |
+| Add comment | JIRA_ADD_COMMENT | issueIdOrKey, body |
+| List comments | JIRA_LIST_ISSUE_COMMENTS | issueIdOrKey |
+| List projects | JIRA_GET_ALL_PROJECTS | (none) |
+| Get project | JIRA_GET_PROJECT | projectIdOrKey |
+| List boards | JIRA_LIST_BOARDS | (none) |
+| List sprints | JIRA_LIST_SPRINTS | boardId |
+| Move to sprint | JIRA_MOVE_ISSUE_TO_SPRINT | sprintId, issues |
+| Create sprint | JIRA_CREATE_SPRINT | name, boardId |
+| Find users | JIRA_FIND_USERS | query |
+| Get fields | JIRA_GET_FIELDS | (none) |
+| List filters | JIRA_LIST_FILTERS | (none) |
+| Project roles | JIRA_GET_PROJECT_ROLES | projectIdOrKey |
+| Project versions | JIRA_GET_PROJECT_VERSIONS | projectIdOrKey |

package/assets/.agent/skills/k8s-manifest-generator/SKILL.md

@@ -0,0 +1,35 @@
+---
+name: k8s-manifest-generator
+description: Create production-ready Kubernetes manifests for Deployments, Services, ConfigMaps, and Secrets following best practices and security standards. Use when generating Kubernetes YAML manifests, creating K8s resources, or implementing production-grade Kubernetes configurations.
+---
+
+# Kubernetes Manifest Generator
+
+Step-by-step guidance for creating production-ready Kubernetes manifests including Deployments, Services, ConfigMaps, Secrets, and PersistentVolumeClaims.
+
+## Use this skill when
+
+Use this skill when you need to:
+- Create new Kubernetes Deployment manifests
+- Define Service resources for network connectivity
+- Generate ConfigMap and Secret resources for configuration management
+- Create PersistentVolumeClaim manifests for stateful workloads
+- Follow Kubernetes best practices and naming conventions
+- Implement resource limits, health checks, and security contexts
+- Design manifests for multi-environment deployments
+
+## Do not use this skill when
+
+- The task is unrelated to kubernetes manifest generator
+- You need a different domain or tool outside this scope
+
+## Instructions
+
+- Clarify goals, constraints, and required inputs.
+- Apply relevant best practices and validate outcomes.
+- Provide actionable steps and verification.
+- If detailed examples are required, open `resources/implementation-playbook.md`.
+
+## Resources
+
+- `resources/implementation-playbook.md` for detailed patterns and examples.

package/assets/.agent/skills/k8s-manifest-generator/assets/configmap-template.yaml

@@ -0,0 +1,296 @@
+# Kubernetes ConfigMap Templates
+
+---
+# Template 1: Simple Key-Value Configuration
+apiVersion: v1
+kind: ConfigMap
+metadata:
+  name: <app-name>-config
+  namespace: <namespace>
+  labels:
+    app.kubernetes.io/name: <app-name>
+    app.kubernetes.io/instance: <instance-name>
+data:
+  # Simple key-value pairs
+  APP_ENV: "production"
+  LOG_LEVEL: "info"
+  DATABASE_HOST: "db.example.com"
+  DATABASE_PORT: "5432"
+  CACHE_TTL: "3600"
+  MAX_CONNECTIONS: "100"
+
+---
+# Template 2: Configuration File
+apiVersion: v1
+kind: ConfigMap
+metadata:
+  name: <app-name>-config-file
+  namespace: <namespace>
+  labels:
+    app.kubernetes.io/name: <app-name>
+data:
+  # Application configuration file
+  application.yaml: |
+    server:
+      port: 8080
+      host: 0.0.0.0
+
+    logging:
+      level: INFO
+      format: json
+
+    database:
+      host: db.example.com
+      port: 5432
+      pool_size: 20
+      timeout: 30
+
+    cache:
+      enabled: true
+      ttl: 3600
+      max_entries: 10000
+
+    features:
+      new_ui: true
+      beta_features: false
+
+---
+# Template 3: Multiple Configuration Files
+apiVersion: v1
+kind: ConfigMap
+metadata:
+  name: <app-name>-multi-config
+  namespace: <namespace>
+  labels:
+    app.kubernetes.io/name: <app-name>
+data:
+  # Nginx configuration
+  nginx.conf: |
+    user nginx;
+    worker_processes auto;
+    error_log /var/log/nginx/error.log warn;
+    pid /var/run/nginx.pid;
+
+    events {
+      worker_connections 1024;
+    }
+
+    http {
+      include /etc/nginx/mime.types;
+      default_type application/octet-stream;
+
+      log_format main '$remote_addr - $remote_user [$time_local] "$request" '
+                      '$status $body_bytes_sent "$http_referer" '
+                      '"$http_user_agent" "$http_x_forwarded_for"';
+
+      access_log /var/log/nginx/access.log main;
+      sendfile on;
+      keepalive_timeout 65;
+
+      include /etc/nginx/conf.d/*.conf;
+    }
+
+  # Default site configuration
+  default.conf: |
+    server {
+      listen 80;
+      server_name _;
+
+      location / {
+        proxy_pass http://backend:8080;
+        proxy_set_header Host $host;
+        proxy_set_header X-Real-IP $remote_addr;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header X-Forwarded-Proto $scheme;
+      }
+
+      location /health {
+        access_log off;
+        return 200 "healthy\n";
+      }
+    }
+
+---
+# Template 4: JSON Configuration
+apiVersion: v1
+kind: ConfigMap
+metadata:
+  name: <app-name>-json-config
+  namespace: <namespace>
+  labels:
+    app.kubernetes.io/name: <app-name>
+data:
+  config.json: |
+    {
+      "server": {
+        "port": 8080,
+        "host": "0.0.0.0",
+        "timeout": 30
+      },
+      "database": {
+        "host": "postgres.example.com",
+        "port": 5432,
+        "database": "myapp",
+        "pool": {
+          "min": 2,
+          "max": 20
+        }
+      },
+      "redis": {
+        "host": "redis.example.com",
+        "port": 6379,
+        "db": 0
+      },
+      "features": {
+        "auth": true,
+        "metrics": true,
+        "tracing": true
+      }
+    }
+
+---
+# Template 5: Environment-Specific Configuration
+apiVersion: v1
+kind: ConfigMap
+metadata:
+  name: <app-name>-prod-config
+  namespace: production
+  labels:
+    app.kubernetes.io/name: <app-name>
+    environment: production
+data:
+  APP_ENV: "production"
+  LOG_LEVEL: "warn"
+  DEBUG: "false"
+  RATE_LIMIT: "1000"
+  CACHE_TTL: "3600"
+  DATABASE_POOL_SIZE: "50"
+  FEATURE_FLAG_NEW_UI: "true"
+  FEATURE_FLAG_BETA: "false"
+
+---
+# Template 6: Script Configuration
+apiVersion: v1
+kind: ConfigMap
+metadata:
+  name: <app-name>-scripts
+  namespace: <namespace>
+  labels:
+    app.kubernetes.io/name: <app-name>
+data:
+  # Initialization script
+  init.sh: |
+    #!/bin/bash
+    set -e
+
+    echo "Running initialization..."
+
+    # Wait for database
+    until nc -z $DATABASE_HOST $DATABASE_PORT; do
+      echo "Waiting for database..."
+      sleep 2
+    done
+
+    echo "Database is ready!"
+
+    # Run migrations
+    if [ "$RUN_MIGRATIONS" = "true" ]; then
+      echo "Running database migrations..."
+      ./migrate up
+    fi
+
+    echo "Initialization complete!"
+
+  # Health check script
+  healthcheck.sh: |
+    #!/bin/bash
+
+    # Check application health endpoint
+    response=$(curl -sf http://localhost:8080/health)
+
+    if [ $? -eq 0 ]; then
+      echo "Health check passed"
+      exit 0
+    else
+      echo "Health check failed"
+      exit 1
+    fi
+
+---
+# Template 7: Prometheus Configuration
+apiVersion: v1
+kind: ConfigMap
+metadata:
+  name: prometheus-config
+  namespace: monitoring
+  labels:
+    app.kubernetes.io/name: prometheus
+data:
+  prometheus.yml: |
+    global:
+      scrape_interval: 15s
+      evaluation_interval: 15s
+      external_labels:
+        cluster: 'production'
+        region: 'us-west-2'
+
+    alerting:
+      alertmanagers:
+      - static_configs:
+        - targets:
+          - alertmanager:9093
+
+    rule_files:
+    - /etc/prometheus/rules/*.yml
+
+    scrape_configs:
+    - job_name: 'kubernetes-pods'
+      kubernetes_sd_configs:
+      - role: pod
+      relabel_configs:
+      - source_labels: [__meta_kubernetes_pod_annotation_prometheus_io_scrape]
+        action: keep
+        regex: true
+      - source_labels: [__meta_kubernetes_pod_annotation_prometheus_io_path]
+        action: replace
+        target_label: __metrics_path__
+        regex: (.+)
+      - source_labels: [__address__, __meta_kubernetes_pod_annotation_prometheus_io_port]
+        action: replace
+        target_label: __address__
+        regex: ([^:]+)(?::\d+)?;(\d+)
+        replacement: $1:$2
+
+---
+# Usage Examples:
+#
+# 1. Mount as environment variables:
+#   envFrom:
+#   - configMapRef:
+#       name: <app-name>-config
+#
+# 2. Mount as files:
+#   volumeMounts:
+#   - name: config
+#     mountPath: /etc/app
+#   volumes:
+#   - name: config
+#     configMap:
+#       name: <app-name>-config-file
+#
+# 3. Mount specific keys as files:
+#   volumes:
+#   - name: nginx-config
+#     configMap:
+#       name: <app-name>-multi-config
+#       items:
+#       - key: nginx.conf
+#         path: nginx.conf
+#
+# 4. Use individual environment variables:
+#   env:
+#   - name: LOG_LEVEL
+#     valueFrom:
+#       configMapKeyRef:
+#         name: <app-name>-config
+#         key: LOG_LEVEL

package/assets/.agent/skills/k8s-manifest-generator/assets/deployment-template.yaml

@@ -0,0 +1,203 @@
+# Production-Ready Kubernetes Deployment Template
+# Replace all <placeholders> with actual values
+
+apiVersion: apps/v1
+kind: Deployment
+metadata:
+  name: <app-name>
+  namespace: <namespace>
+  labels:
+    app.kubernetes.io/name: <app-name>
+    app.kubernetes.io/instance: <instance-name>
+    app.kubernetes.io/version: "<version>"
+    app.kubernetes.io/component: <component>  # backend, frontend, database, cache
+    app.kubernetes.io/part-of: <system-name>
+    app.kubernetes.io/managed-by: kubectl
+  annotations:
+    description: "<application description>"
+    contact: "<team-email>"
+spec:
+  replicas: 3  # Minimum 3 for production HA
+  revisionHistoryLimit: 10
+
+  selector:
+    matchLabels:
+      app.kubernetes.io/name: <app-name>
+      app.kubernetes.io/instance: <instance-name>
+
+  strategy:
+    type: RollingUpdate
+    rollingUpdate:
+      maxSurge: 1
+      maxUnavailable: 0  # Zero-downtime deployment
+
+  minReadySeconds: 10
+  progressDeadlineSeconds: 600
+
+  template:
+    metadata:
+      labels:
+        app.kubernetes.io/name: <app-name>
+        app.kubernetes.io/instance: <instance-name>
+        app.kubernetes.io/version: "<version>"
+      annotations:
+        prometheus.io/scrape: "true"
+        prometheus.io/port: "9090"
+        prometheus.io/path: "/metrics"
+
+    spec:
+      serviceAccountName: <app-name>
+
+      # Pod-level security context
+      securityContext:
+        runAsNonRoot: true
+        runAsUser: 1000
+        runAsGroup: 1000
+        fsGroup: 1000
+        seccompProfile:
+          type: RuntimeDefault
+
+      # Init containers (optional)
+      initContainers:
+      - name: init-wait
+        image: busybox:1.36
+        command: ['sh', '-c', 'echo "Initializing..."']
+        securityContext:
+          allowPrivilegeEscalation: false
+          runAsNonRoot: true
+          runAsUser: 1000
+
+      containers:
+      - name: <container-name>
+        image: <registry>/<image>:<tag>  # Never use :latest
+        imagePullPolicy: IfNotPresent
+
+        ports:
+        - name: http
+          containerPort: 8080
+          protocol: TCP
+        - name: metrics
+          containerPort: 9090
+          protocol: TCP
+
+        # Environment variables
+        env:
+        - name: POD_NAME
+          valueFrom:
+            fieldRef:
+              fieldPath: metadata.name
+        - name: POD_NAMESPACE
+          valueFrom:
+            fieldRef:
+              fieldPath: metadata.namespace
+        - name: POD_IP
+          valueFrom:
+            fieldRef:
+              fieldPath: status.podIP
+
+        # Load from ConfigMap and Secret
+        envFrom:
+        - configMapRef:
+            name: <app-name>-config
+        - secretRef:
+            name: <app-name>-secret
+
+        # Resource limits
+        resources:
+          requests:
+            memory: "256Mi"
+            cpu: "250m"
+          limits:
+            memory: "512Mi"
+            cpu: "500m"
+
+        # Startup probe (for slow-starting apps)
+        startupProbe:
+          httpGet:
+            path: /health/startup
+            port: http
+          initialDelaySeconds: 0
+          periodSeconds: 10
+          timeoutSeconds: 3
+          failureThreshold: 30  # 5 minutes to start
+
+        # Liveness probe
+        livenessProbe:
+          httpGet:
+            path: /health/live
+            port: http
+          initialDelaySeconds: 30
+          periodSeconds: 10
+          timeoutSeconds: 5
+          failureThreshold: 3
+
+        # Readiness probe
+        readinessProbe:
+          httpGet:
+            path: /health/ready
+            port: http
+          initialDelaySeconds: 5
+          periodSeconds: 5
+          timeoutSeconds: 3
+          failureThreshold: 3
+
+        # Volume mounts
+        volumeMounts:
+        - name: tmp
+          mountPath: /tmp
+        - name: cache
+          mountPath: /app/cache
+        # - name: data
+        #   mountPath: /var/lib/app
+
+        # Container security context
+        securityContext:
+          allowPrivilegeEscalation: false
+          readOnlyRootFilesystem: true
+          runAsNonRoot: true
+          runAsUser: 1000
+          capabilities:
+            drop:
+            - ALL
+
+        # Lifecycle hooks
+        lifecycle:
+          preStop:
+            exec:
+              command: ["/bin/sh", "-c", "sleep 15"]  # Graceful shutdown
+
+      # Volumes
+      volumes:
+      - name: tmp
+        emptyDir: {}
+      - name: cache
+        emptyDir:
+          sizeLimit: 1Gi
+      # - name: data
+      #   persistentVolumeClaim:
+      #     claimName: <app-name>-data
+
+      # Scheduling
+      affinity:
+        podAntiAffinity:
+          preferredDuringSchedulingIgnoredDuringExecution:
+          - weight: 100
+            podAffinityTerm:
+              labelSelector:
+                matchLabels:
+                  app.kubernetes.io/name: <app-name>
+              topologyKey: kubernetes.io/hostname
+
+      topologySpreadConstraints:
+      - maxSkew: 1
+        topologyKey: topology.kubernetes.io/zone
+        whenUnsatisfiable: ScheduleAnyway
+        labelSelector:
+          matchLabels:
+            app.kubernetes.io/name: <app-name>
+
+      terminationGracePeriodSeconds: 30
+
+      # Image pull secrets (if using private registry)
+      # imagePullSecrets:
+      # - name: regcred