hybrid-agent-detector

Detect hybrid agents by analyzing execution patterns in .claude/agents prompts.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/fractary/claude-plugins --skill hybrid-agent-detector
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hybrid-agent-detector
Source: https://github.com/fractary/claude-plugins/tree/main/plugins/faber-agent/skills/hybrid-agent-detector
Command: npx skills add https://github.com/fractary/claude-plugins --skill hybrid-agent-detector

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Detects agents that blur the line between orchestration and execution by performing direct work instead of delegating to skills.

Core Features & Use Cases

  • Analyzes agent definitions for execution patterns like file ops, data processing, API calls.
  • Returns structured JSON with severity and recommendations.
  • Guides consolidation of execution into dedicated skills.

Quick Start

Run the detector to surface hybrid agents and suggested migrations.

Frequently Asked Questions about hybrid-agent-detector

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

FAQPage Schema
How do I detect if my agents are performing execution work instead of delegating to skills?

Hybrid-agent-detector analyzes agent prompts and files under .claude/agents to identify execution patterns like file operations, data processing, and API calls that should be delegated to skills. It returns a structured JSON report with a hybrid_score and specific execution patterns found, helping you spot where orchestration logic bleeds into direct work.

What execution patterns does the detector identify in agent definitions?

The detector scans for direct execution across Read, Write, Edit, Bash, and API call tools within agent prompts. It distinguishes orchestration patterns from execution work, flagging cases where agents handle file operations, data transformation, or external calls instead of delegating to specialized skills.

How do I refactor a hybrid agent to separate orchestration from execution?

Run the detector to get execution_patterns and recommendations in the JSON output. The results guide you to consolidate flagged execution logic into dedicated skills, leaving the agent to orchestrate skill calls. Follow the recommendation field to identify which work should migrate into new or existing skills.

Can I use this detector across different project types and agent configurations?

Yes. The detector examines orchestration vs execution patterns across diverse project contexts by analyzing agent definitions in .claude/agents. It works regardless of your project structure, scaling from single agents to multiple orchestration patterns.

What output does the detector provide for tracking hybrid agents?

The detector returns a structured JSON with agent entries, a hybrid_score rating severity, execution_patterns listing found work, orchestration_present status, and a recommendation for refactoring. This structured format lets you prioritize which agents need consolidation into skills.