analyze-agent-overlap

Name: analyze-agent-overlap
Author: JBurlison

70stars8forks

How to install analyze-agent-overlap?

jburlison/metaprompts/analyze-agent-overlap

$npx -y skills add JBurlison/MetaPrompts --skill analyze-agent-overlap

Installs into the current project.

Summary

Analyzes existing agents, skills, prompts, and instructions to identify overlaps, redundancies, and conflicts. Works with GitHub Copilot, Claude Code, Codex, OpenCode, and other providers. Use before creating new customization files to avoid duplication, when consolidating agents

Files · 1

View on GitHub

SKILL.md

1	# Analyze Agent Overlap
2
3	Detects redundancy, overlap, and potential conflicts between AI coding assistant customization files.
4
5	## Provider Folder Reference
6
7	This skill works across multiple AI coding assistant providers:
8
9	\| Provider \| Base Folder \|
10	\|----------\|-------------\|
11	\| GitHub Copilot \| `.github/` \|
12	\| Claude Code \| `.claude/` \|
13	\| Codex \| `.codex/` \|
14	\| OpenCode \| `.config/opencode/` \|
15
16	Throughout this document, `<provider>/` represents your chosen provider's base folder.
17
18	## When to Use
19
20	- Before creating a new agent, skill, prompt, or instruction
21	- When you suspect two agents are doing similar things
22	- To audit and consolidate your customization files
23	- When agent behaviors seem to conflict
24
25	## Analysis Process
26
27	### Step 1: Inventory Existing Items
28
29	Scan these locations (replace `<provider>/` with actual folder):
30	- `<provider>/agents/*.md` - All agent definitions (including `.subagent.agent.md`)
31	- `<provider>/skills/*/SKILL.md` - All skill definitions
32	- `<provider>/prompts/*.prompt.md` - All prompt templates
33	- `<provider>/instructions/*.instructions.md` - All instruction files
34
35	For each item, extract:
36	- Name: The identifier
37	- Purpose: What problem it solves (from description)
38	- Domain: What areas/topics it covers
39	- Triggers: Keywords or scenarios that activate it
40	- User-Invokable: Whether it's a user-facing agent or sub-agent
41
42	### Step 2: Compare Against Proposed Item
43
44	When analyzing a proposed new item, compare:
45
46	Direct Overlap Indicators:
47	- Same or very similar name
48	- Same primary purpose statement
49	- Identical target domain
50	- Overlapping trigger keywords (>50% match)
51
52	Partial Overlap Indicators:
53	- Related but distinct purposes
54	- Some shared expertise areas
55	- Similar but different trigger scenarios
56	- Complementary functionality
57
58	No Overlap Indicators:
59	- Different domains entirely
60	- Non-overlapping use cases
61	- Distinct trigger keywords
62
63	### Step 3: Detect Conflicts
64
65	Look for these conflict types:
66
67	Behavioral Conflicts:
68	- Two agents giving contradictory guidance for same scenario
69	- Instructions that override each other for same file patterns
70	- Skills that produce incompatible outputs
71
72	Scope Conflicts:
73	- Multiple agents claiming the same use cases
74	- Overlapping `applyTo` patterns in instructions
75	- Ambiguous routing between similar agents
76
77	Naming Conflicts:
78	- Names too similar causing confusion
79	- Same name in different contexts
80
81	## Overlap Severity Levels
82
83	### 🔴 Critical (Do Not Proceed)
84	- Exact duplicate of existing item
85	- Direct contradiction with existing guidance
86	- Name collision
87	- >80% purpose overlap
88
89	### 🟡 Warning (Needs Discussion)
90	- Significant overlap (50-80% shared purpose)
91	- Potential user confusion about which to use
92	- Overlapping triggers with different behaviors
93	- Partial scope conflict
94
95	### 🟢 Low Risk (Proceed with Awareness)
96	- Minor overlap (<50% shared concerns)
97	- Complementary purposes
98	- Clear differentiation possible
99	- Different trigger contexts
100
101	## Resolution Strategies
102
103	When overlap is detected, consider:
104
105	### Merge
106	Combine into single, more comprehensive item.
107	- Best when: Items serve nearly identical purpose
108	- Action: Create unified item, deprecate duplicates
109
110	### Extend
111	Add new functionality to existing item.
112	- Best when: New need is subset of existing item's scope
113	- Action: Modify existing item, don't create new
114
115	### Differentiate
116	Clarify boundaries between items.
117	- Best when: Items serve related but distinct needs
118	- Action: Update descriptions to make distinctions clear
119
120	### Reference
121	Have one item delegate to another.
122	- Best when: Items have hierarchical relationship
123	- Action: Add handoff or reference in description
124
125	### Supersede
126	Replace older item with improved version.
127	- Best when: New item is strictly better
128	- Action: Create new, mark old as deprecated
129
130	## Output Format
131
132	```markdown
133	## Overlap Analysis: [Proposed Item Name]
134
135	### Summary
136	Proposed Type: [Agent\|Skill\|Prompt\|Instruction]
137	Proposed Purpose: [Brief description]
138	Overlap Level: None \| Low \| Medium \| High \| Critical
139	Recommendation: Proceed \| Modify \| Merge \| Reconsider
140
141	### Comparison Matrix
142
143	\| Existing Item \| Type \| Overlap \| Shared Concerns \|
144	\|---------------\|------\|---------\|-----------------\|
145	\| [name] \| [type] \| [level] \| [what overlaps] \|
146
147	### Detailed Findings
148
149	#### High/Critical Overlap Items
150	[For each significant overlap:]
151
152	[Existing Item Name]
153	- Type: [type]
154	- Purpose: [their purpose]
155	- Overlap Areas: [specific shared concerns]
156	- Key Distinction: [how proposed differs]
157	- Resolution: [recommended action]
158
159	#### Potential Conflicts
160	[List any behavioral or scope confl

People who liked this also viewed

6 picks

Type

analyze-agent-overlap

70stars8forks

View on GitHub

How to install analyze-agent-overlap?

jburlison/metaprompts/analyze-agent-overlap

$npx -y skills add JBurlison/MetaPrompts --skill analyze-agent-overlap

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Analyze Agent Overlap
2
3	Detects redundancy, overlap, and potential conflicts between AI coding assistant customization files.
4
5	## Provider Folder Reference
6
7	This skill works across multiple AI coding assistant providers:
8
9	\| Provider \| Base Folder \|
10	\|----------\|-------------\|
11	\| GitHub Copilot \| `.github/` \|
12	\| Claude Code \| `.claude/` \|
13	\| Codex \| `.codex/` \|
14	\| OpenCode \| `.config/opencode/` \|
15
16	Throughout this document, `<provider>/` represents your chosen provider's base folder.
17
18	## When to Use
19
20	- Before creating a new agent, skill, prompt, or instruction
21	- When you suspect two agents are doing similar things
22	- To audit and consolidate your customization files
23	- When agent behaviors seem to conflict
24
25	## Analysis Process
26
27	### Step 1: Inventory Existing Items
28
29	Scan these locations (replace `<provider>/` with actual folder):
30	- `<provider>/agents/*.md` - All agent definitions (including `.subagent.agent.md`)
31	- `<provider>/skills/*/SKILL.md` - All skill definitions
32	- `<provider>/prompts/*.prompt.md` - All prompt templates
33	- `<provider>/instructions/*.instructions.md` - All instruction files
34
35	For each item, extract:
36	- Name: The identifier
37	- Purpose: What problem it solves (from description)
38	- Domain: What areas/topics it covers
39	- Triggers: Keywords or scenarios that activate it
40	- User-Invokable: Whether it's a user-facing agent or sub-agent
41
42	### Step 2: Compare Against Proposed Item
43
44	When analyzing a proposed new item, compare:
45
46	Direct Overlap Indicators:
47	- Same or very similar name
48	- Same primary purpose statement
49	- Identical target domain
50	- Overlapping trigger keywords (>50% match)
51
52	Partial Overlap Indicators:
53	- Related but distinct purposes
54	- Some shared expertise areas
55	- Similar but different trigger scenarios
56	- Complementary functionality
57
58	No Overlap Indicators:
59	- Different domains entirely
60	- Non-overlapping use cases
61	- Distinct trigger keywords
62
63	### Step 3: Detect Conflicts
64
65	Look for these conflict types:
66
67	Behavioral Conflicts:
68	- Two agents giving contradictory guidance for same scenario
69	- Instructions that override each other for same file patterns
70	- Skills that produce incompatible outputs
71
72	Scope Conflicts:
73	- Multiple agents claiming the same use cases
74	- Overlapping `applyTo` patterns in instructions
75	- Ambiguous routing between similar agents
76
77	Naming Conflicts:
78	- Names too similar causing confusion
79	- Same name in different contexts
80
81	## Overlap Severity Levels
82
83	### 🔴 Critical (Do Not Proceed)
84	- Exact duplicate of existing item
85	- Direct contradiction with existing guidance
86	- Name collision
87	- >80% purpose overlap
88
89	### 🟡 Warning (Needs Discussion)
90	- Significant overlap (50-80% shared purpose)
91	- Potential user confusion about which to use
92	- Overlapping triggers with different behaviors
93	- Partial scope conflict
94
95	### 🟢 Low Risk (Proceed with Awareness)
96	- Minor overlap (<50% shared concerns)
97	- Complementary purposes
98	- Clear differentiation possible
99	- Different trigger contexts
100
101	## Resolution Strategies
102
103	When overlap is detected, consider:
104
105	### Merge
106	Combine into single, more comprehensive item.
107	- Best when: Items serve nearly identical purpose
108	- Action: Create unified item, deprecate duplicates
109
110	### Extend
111	Add new functionality to existing item.
112	- Best when: New need is subset of existing item's scope
113	- Action: Modify existing item, don't create new
114
115	### Differentiate
116	Clarify boundaries between items.
117	- Best when: Items serve related but distinct needs
118	- Action: Update descriptions to make distinctions clear
119
120	### Reference
121	Have one item delegate to another.
122	- Best when: Items have hierarchical relationship
123	- Action: Add handoff or reference in description
124
125	### Supersede
126	Replace older item with improved version.
127	- Best when: New item is strictly better
128	- Action: Create new, mark old as deprecated
129
130	## Output Format
131
132	```markdown
133	## Overlap Analysis: [Proposed Item Name]
134
135	### Summary
136	Proposed Type: [Agent\|Skill\|Prompt\|Instruction]
137	Proposed Purpose: [Brief description]
138	Overlap Level: None \| Low \| Medium \| High \| Critical
139	Recommendation: Proceed \| Modify \| Merge \| Reconsider
140
141	### Comparison Matrix
142
143	\| Existing Item \| Type \| Overlap \| Shared Concerns \|
144	\|---------------\|------\|---------\|-----------------\|
145	\| [name] \| [type] \| [level] \| [what overlaps] \|
146
147	### Detailed Findings
148
149	#### High/Critical Overlap Items
150	[For each significant overlap:]
151
152	[Existing Item Name]
153	- Type: [type]
154	- Purpose: [their purpose]
155	- Overlap Areas: [specific shared concerns]
156	- Key Distinction: [how proposed differs]
157	- Resolution: [recommended action]
158
159	#### Potential Conflicts
160	[List any behavioral or scope confl

People who liked this also viewed

6 picks

Type