Developer-Native Marketing

`gtm-toolkit analyze`

Generate local assistant prompts to review your content strategy, find keyword opportunities, and analyze competitors.

The CLI does not ship a generic --ai flag; use the focused modes like --keywords, --competitor, or --gaps depending on the analysis you need.

Requirements

Prep your workspace before running the command

• Run the CLI from a project with gtm.config.js configured.
• Decide which local assistant (Cursor, Copilot, Claude Desktop, etc.) will receive the generated prompt.
• Use the --output flag if you want to persist the instructions for later sharing.

Usage

Different analysis modes tailored to common workflows

--competitor <url>

Review a competitor website and compare content pillars

--gaps

Scan your own markdown files for missing coverage

--keywords <topic>

Generate a structured keyword list for a topic

--output <file>

Persist results as JSON for later processing

Each run prints a summary of these entry points so you always know which analyses are available before you choose a flag.

Sample Keyword Output

Structured JSON that can feed directly into briefs or spreadsheets

{
  "topic": "gtm as code",
  "primary": [
    { "keyword": "gtm as code", "intent": "informational", "difficulty": 32 },
    { "keyword": "marketing engineering playbook", "intent": "informational", "difficulty": 27 }
  ],
  "supporting": [
    { "keyword": "continuous marketing delivery", "intent": "informational" },
    { "keyword": "developer native marketing", "intent": "informational" }
  ]
}

Pro Tips

Get more signal from your local assistant-powered analysis

• Pair --gaps with --output and store results in version control for trend tracking.
• Combine competitor runs with gtm-toolkit lint results to spot structural deltas quickly.
• Redirect output to a file (e.g., --output competitor.json) so you can diff changes over time.