AI Agent Use Cases

Added today

44All 189

Prompt to Prepare a Shopping Cart from a Recipe Photo

The author reports that Grok Bot receives a recipe photo, organizes the ingredients and quantities, and creates a shopping list by excluding ingredients already available at home.

Grok Bot
Life & Hobbies

1–20 of 189

DevWalkthrough

Agent for Checking Permission and Exposure Issues in Kubernetes Settings

The author reports that an agent inspected Kubernetes settings to find permission and service exposure issues, and then linked these findings to proposed fixes after approval.

How it works

  1. The author connected resource, service, RBAC, and container inspection APIs, policy search tools, and a Slack approval workflow.
  2. The agent selected tools for inspecting resource limits, exposed services, RBAC, privileged containers, and for searching security policies.

Results

In the public example, the intended outcome is a security review for each configuration and an approved pull request with the proposed fixes.

Notes

A connection to a scanner API is required. The author explains that the commit and pull request for fixes occur after Slack approval. The author confirmed the connection of public configurations and tools, but did not execute them directly.

Source

n8n 공개 워크플로 #19232 Original post ↗

Example prompt · n8n

Goal: Identify and propose fixes for permission and exposure issues in Kubernetes settings.

Input/Environment: [Kubernetes settings], [scanner API], [security policies], [Slack test approval].

Reference original: https://n8n.io/workflows/19232

Prepare the settings and connections so that a test environment can be created using the public configuration from the original. If there are any missing sub-workflows, APIs, or account permissions, mark them as incomplete until they are actually connected.

Required connections and materials: Connect resource, service, RBAC, and container inspection APIs, policy search tools, and a Slack approval workflow.

Agent actions to implement: The agent selects tools for inspecting resource limits, exposed services, RBAC, privileged containers, and for searching security policies.

Scope of actions: A scanner API connection is required. The commit and pull request for fixes are described as steps after Slack approval.

The deliverables are a security review for each configuration and an approved pull request with the proposed fixes. Also organize the necessary setup steps and actual execution methods. After checking the results returned by the tools, select the next task, and separately note any inaccessible materials or tasks that could not be executed.

Verification: Check whether the inspection results match the actual configuration locations, whether no commit is created if approval is denied, and confirm the results of re-inspection after fixes. Clearly distinguish the inputs used for verification, the actual outputs, and any items not yet confirmed.