EDS Ops Agent

Scan, diagnose, and fix Adobe Edge Delivery Services sites from the command line or a GitHub Action. Produces a letter grade (A+ through F), a prioritized issue list, and actionable remediation steps.

Quick Start

npx @focusgts/eds-ops check --owner adobe --repo aem-boilerplate

Commands

Command	What it does
check	Scan a site and produce a health report with grade, score, and issues
fix	Auto-remediate issues (dry-run by default, --execute to apply)
compare	Compare up to 3 EDS sites side-by-side
fleet	Scan multiple sites and generate a fleet dashboard
trend	Show issue trend over time from scan history
history	Manage scan history (clear, verify chain integrity)
serve	Start an MCP server on stdio for LLM tool integration

Options

--owner <org>        GitHub org/user          (or EDS_OWNER env var)
--repo <name>        GitHub repo name         (or EDS_REPO env var)
--ref <branch>       Git branch               (default: main)
--domain <domain>    Site domain for CWV/404   (or EDS_DOMAIN)
--api-key <key>      Admin API key             (or EDS_API_KEY)
--domain-key <key>   OpTel domain key          (or EDS_DOMAIN_KEY)
--max-pages <n>      Max pages for status checks (default: 50)
--format <fmt>       Output: text, json, html  (default: text)
--deep               Fetch page content for deep content & block analysis
--verbose            Show all findings (no truncation)

Output Formats

Text (default) — human-readable report for the terminal:

EDS Site Health: adobe/aem-boilerplate (main)
Grade: A (92 pts)

Critical (0) | Warning (2) | Info (4)

[WARN] Missing custom 404 page
  → Create a /404 page in your content source

[WARN] No redirects spreadsheet found
  → Add a redirects sheet to manage URL migrations

JSON — machine-readable for CI pipelines and dashboards.

HTML — styled report with color-coded grades for sharing with clients.

GitHub Action

Add to any EDS repository for automated health checks on pull requests:

name: EDS Health Check
on:
  pull_request:
    types: [opened, synchronize, reopened]

permissions:
  contents: read
  pull-requests: write

jobs:
  health-check:
    runs-on: ubuntu-latest
    steps:
      - name: EDS Ops Check
        uses: Focus-GTS/eds-ops@main
        with:
          owner: ${{ github.repository_owner }}
          repo: ${{ github.event.repository.name }}
          fail-on-critical: 'true'
          fail-below-grade: 'C'
          comment-on-pr: 'true'

Action Inputs

Input	Default	Description
owner	(required)	GitHub org/user
repo	(required)	GitHub repo name
ref	main	Git branch to scan
domain		Site domain for CWV and 404 data
api-key		EDS Admin API key
domain-key		RUM domain key
deep	false	Enable deep content and block analysis
fail-on-critical	true	Fail the action if critical issues are found
fail-below-grade		Fail if grade drops below this threshold (A, B, C, D)
comment-on-pr	true	Post results as a PR comment

Action Outputs

Output	Description
grade	Letter grade (A+ through F)
score	Numeric score (0-100)
total-issues	Total issue count
critical-issues	Critical issue count
report-json	Full report as JSON string

Grading Formula

score = max(0, 100 - (critical * 15 + warning * 3 + info * 0.5))

A+  ≥ 95    A  ≥ 90    B  ≥ 75    C  ≥ 55    D  ≥ 30    F  < 30

What It Checks

• Project structure — fstab.yaml, required directories, boilerplate files
• Configuration — robots.txt, sitemap.xml, metadata, redirects, headers
• Page status — preview/live sync, stale content, unpublished changes
• Performance — Core Web Vitals (LCP, CLS, INP, TTFB) via OpTel/RUM
• Content quality — (with --deep) duplicate detection, heading structure, image optimization
• 404 monitoring — broken links and referrer analysis
• Block health — (with --deep) block usage, accessibility, rendering issues

Advanced Features

Self-learning fix recommendations — the fix engine tracks which remediation steps actually resolve issues across your sites, and re-ranks suggestions based on real-world success rates.

Cross-site learning — when scanning fleets, fixes that work on one site inform recommendations for similar sites.

Predictive grade forecasting — after 5+ scans, trend projects your grade 2-12 weeks forward using linear regression.

Tamper-evident history — scan history uses hash chaining so you can verify no results were modified after the fact.

Related Tools

Tool	What it does
@focusgts/eds-mcp-server	MCP server giving AI agents direct access to EDS preview, publish, metrics, and config APIs
eds-content-ops-skills	43 AI skills for EDS content ops — auditing, SEO, accessibility, migration, and more
EDS Score	Free browser-based site health analyzer for EDS sites

About

Built by FocusGTS — Adobe Silver Solution Partner specializing in Edge Delivery Services.

License

Apache-2.0