cy-research-competitors

Generate schema-compliant competitor analyses via parallel cy-researcher subagents.

182|8|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/compozy/agh --skill cy-research-competitors
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cy-research-competitors
Source: https://github.com/compozy/agh/tree/main/.agents/skills/cy-research-competitors
Command: npx skills add https://github.com/compozy/agh --skill cy-research-competitors

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) and references (resource) components.

What problem does it solve?

Producing reliable TechSpecs is slower when you need cross-system reference grounding, because competitor repos must be studied thoroughly and converted into a consistent, actionable format.

Core Features & Use Cases

  • Dispatches scoped-write competitor subagents in parallel: runs the dedicated cy-researcher subagent once per competitor, each writing exactly one analysis file to the task’s analysis directory.
  • Enforces a fixed analysis schema with validation: uses a canonical template to ensure every analysis includes the required seven sections and that evidence cites real file paths under the competitor’s .resources/<name>/.
  • Produces reusable architecture inputs: generates findings you can link into _techspec.md or task artifacts while keeping the analysis files as the authoritative source.

Use this when you need cross-system reference grounding for a TechSpec, refactor, or design decision that depends on patterns from multiple existing agent runtimes and harnesses.

Quick Start

Ask the AI to run the competitor research for your task by providing the task slug and a comma-separated list of competitor names, for example: Dispatch cy-research-competitors for task "my-feature" and competitors "hermes,openclaw,openfang".

Frequently Asked Questions about cy-research-competitors

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

FAQPage Schema
How do I generate cross-repository competitor analyses for TechSpec workflows?

To generate cross-repository competitor analyses, dispatch parallel subagents that read from each competitor's resource directory and write one schema-compliant analysis file per competitor. This provides evidence-backed architectural comparisons for TechSpecs and refactors.

How does parallel competitor research ensure evidence-based analysis?

Parallel competitor research ensures evidence-based analysis by validating that every output file cites real file paths located under the competitor's resource directory. If an analysis file fails this schema validation, the system re-dispatches the subagent to correct it.

What's the best way to compare agent runtime patterns across multiple repositories?

The best way to compare agent runtime patterns is dispatching scoped-write subagents in parallel for each repository, which produces consistent seven-section analysis files that serve as authoritative inputs for architectural design decisions.

Can I use parallel subagent dispatch for architectural decisions on daemon runtimes?

Yes, you can use parallel subagent dispatch for architectural decisions on daemon runtimes by running a dedicated researcher subagent per competitor system to study and convert their patterns into a consistent, actionable format.

How do I ensure competitor research outputs comply with a fixed analysis template?

To ensure competitor research outputs comply with a fixed analysis template, apply schema validation checks that enforce a canonical seven-section structure and verify evidence path existence, automatically re-dispatching subagents upon schema failures.

What are the limitations of parallel competitor research for TechSpecs?

A limitation of parallel competitor research is that it requires resource directories to be pre-populated under .resources/<competitor>/ for the subagents to read, and it enforces scoped-write constraints that restrict outputs to exactly one file per competitor in the task analysis directory.