global/competitive-intel

Competitive Intelligence — analyze competitor content strategy.

Category: global
Source: workflows/research/competitive.py

Input Schema

Field	Type	Default	Description
`competitors`	`string[]`	—	Creator names/handles to analyze
`niche`	`string`	`""`	Content niche for competitor discovery
`platform`	`string`	`"YouTube"`	Target platform
`regenerate`	`object`	—	When set, this run is a regeneration. Workflows may read `direction` / `keep` / `extra_instructions` to modulate prompts; the engine persists `parent_run_id` and `parent_variant_index` as run lineage columns.
`variants`	`integer`	`1`	Number of independent variant executions (1–10). When > 1, the engine runs the workflow N times with different sampling, producing N outputs.

Output Schema

Field	Type	Default	Description
`competitive_analysis`	`object`	—	Analysis with competitors, opportunities, differentiators
`kind`	`object`	—	Variant card shape: video / carousel / image / text. Surfaced on the per-variant entry of the run-output API and used by gallery UIs to pick the right layout.
`workflow`	`string`	`"competitive-intel"`	Workflow identifier

Task Pipeline

analyze_competitors

Task	Description
`analyze_competitors`	Analyze competitors — delegates to SDK stage.

Run-spec example

Save the YAML below as my-run.yaml, edit the values, and run with the CLI or POST it to the API. Required fields are uncommented; optional knobs are documented above the input: block — copy any line under input: and uncomment to set.

workflow: global/competitive-intel

# Optional fields — copy any line(s) under `input:` and uncomment to set:
# Creator names/handles to analyze
#   competitors: []
#
# Content niche for competitor discovery
#   niche: ""
#
# Target platform
#   platform: YouTube
#

input: {}

Run it locally:

fab-workflow --from-file my-run.yaml

Or submit over the wire — the same file is the request body:

curl -X POST 'https://gofabric.dev/v1/workflows/runs?name=global/competitive-intel' \
  -H 'Authorization: Bearer fab_xxx' \
  -H 'content-type: application/yaml' \
  --data-binary @my-run.yaml

Every workflow also accepts the universal WorkflowInput fields — variants (1–10 fan-out) and regenerate (creative-direction hints with run lineage). See Run-specs (YAML / TOML / JSON) for the full top-level shape (metadata, priority, bundle, parent, etc.).

Warnings

Task analyze_competitors has no Pydantic types — contract is opaque to consumers.