AI Agent Use Cases
Views —

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 Identifying Slow Build Sections by Comparing Build Metrics and Code

This is an example where a build performance agent investigates slow sections by reading both build metrics and GitHub code context together.

n8n

How it works

  1. Connect Gradle and CocoaPods metrics, previous records, and a GitHub lookup tool.
  2. Configure the performance analysis agent so that it is linked with the GitHub API tool, allowing it to check both build regression indicators and code context together.

Results

The intended outcome in the public example is a review of build time changes and related code materials.

Notes

Gradle and CocoaPods metrics and historical records are external inputs. The actual effect of reducing build time has not been confirmed. The public configuration and tool connections were checked, but the process was not executed directly.

Source

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

Example prompt · n8n

Goal: Compare the point where the mobile app build has slowed down with the repository.

Inputs/Environment: [Current build metrics], [Previous records], [Repository], [Measurement environment information].

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

Prepare the configuration and connections so that a test environment can be created using the public setup from the original. If there are any missing sub-workflows, APIs, or account permissions, indicate that the connection is incomplete until they are actually linked.

Connections and materials to prepare: Connect Gradle and CocoaPods metrics, previous records, and a GitHub lookup tool.

Agent behavior to implement: Configure the performance analysis agent so that it is linked with the GitHub API tool, allowing it to check both build regression indicators and code context together.

Scope of operation: Gradle and CocoaPods metrics and historical records are external inputs. The actual effect of reducing build time has not been confirmed.

The deliverables are build time changes and related code review materials. Please also organize the necessary setup steps and actual execution methods. After checking the results returned by the tool, select the next task, and separately note any materials that could not be accessed or tasks that could not be executed.

Verification: Check that measurements taken under different device or cache conditions are not compared directly, and that candidate causes are actually linked to changed files. Clearly distinguish the inputs used for verification, the actual outputs, and any items not yet confirmed.