Agent Manager Process Investigation

Classify failed agent-manager run root causes from timeline and diff attachments.

54|7|Updated Sep 19, 2021
One-click install
npx skills add https://github.com/Vrooli/Vrooli --skill agent-manager-process-investigation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Agent Manager Process Investigation
Source: https://github.com/Vrooli/Vrooli/tree/main/scenarios/prompt-manager/store/skills/packs/core/agent-manager-process-investigation
Command: npx skills add https://github.com/Vrooli/Vrooli --skill agent-manager-process-investigation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill organizes the chaotic attachments from a failed agent-manager execution into a coherent diagnosis so you can quickly spot why runs break and what needs to change.

Core Features & Use Cases

  • Evidence-first diagnosis: Prioritizes the provided timeline, overview, and diff attachments, calling CLI tools only when a detail is missing.
  • Root-cause classification: Labels each failure as Environment/Tooling or Agent Setup, attaches severity, and pairs it with a concrete fix referencing the responsible file.
  • Use Case: When a local agent run fails after a prompt-manager config push, compare the current and historical contexts to identify environmental issues or prompt drift and recommend precise file edits.

Quick Start

Ask the skill to analyze the provided agent run attachments, classify every failure, and recommend file-specific fixes.

Frequently Asked Questions about Agent Manager Process Investigation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose a failed agent-manager run after a prompt-manager config push?

To diagnose a failed agent-manager run, review timeline, overview, and diff attachments to classify root causes as environment issues or prompt drift, then apply file-level fixes. Evidence-based analysis isolates configuration flaws.

What is the best way to find the root cause of agent execution failures?

Finding the root cause of agent execution failures involves analyzing run attachments like timelines and diffs to categorize issues as environment tooling problems or agent setup flaws. Severity is assessed to recommend actionable fixes.

How do I get actionable fixes for prompt-engineering failures?

Getting actionable fixes for prompt-engineering failures requires analyzing historical context and run diffs to identify prompt drift. Recommendations provide precise file-level edits referencing the responsible prompt-manager setup configurations.

Can I investigate environment-diagnostics issues without manually collecting agent logs?

Yes, you can investigate environment-diagnostics issues without manual collection if attachments already summarize events, configurations, and history. The investigation focuses entirely on analyzing provided data rather than gathering logs.

Why does my agent setup break after applying a new prompt configuration?

Your agent setup breaks after a new prompt configuration due to prompt drift or environment tooling conflicts. Comparing current and historical contexts identifies whether the failure stems from setup flaws or environmental issues.

Do I need to provide complete execution timelines to classify agent failure root causes?

You need to provide complete execution timelines, overviews, and diffs as attachments to classify agent failure root causes. The analysis cites evidence from these inputs to label failures as environment tooling or agent setup issues.