Aem CLI

What it does

When your agent uses it

• Tasks that involve API design

Example prompts

• “/aem-cli”

Requirements

• Node.js
• A credential in AEM_TLS_KEY

Workflow steps

7 steps, taken from the step headings in SKILL.md.

1. 1Install
2. 2aem up — Local Dev Server
3. 3.env Configuration
4. 4HTTPS / TLS
5. 5Corporate Proxy and Certificate Trust
6. 6aem import — Import Server
7. 7aem content — da.live Content Sync

What it can do on your machine

Read from SKILL.md and the folder at commit cbc9952. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  Shell commands in SKILL.md call:

  • npm
  • curl
  • jq
  • npx
  • openssl
  • brew
  • choco
  • go

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  Hosts in commands or code, which the agent is likely to contact:

  • admin.da.live
  • content.da.live

  Also links to:

  • npmjs.com

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names these keys or tokens, usually read from environment variables:

  • AEM_TLS_KEY

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Aem CLI loads about 2.6k tokens when it runs, and up to ~4.3k if it reads all its reference files. Until then it costs about 159 tokens; SKILL.md has 882 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~159

When it runs · the whole SKILL.md, loaded when a task matches

~2.6k

With references · SKILL.md plus every file in references/, read only if the agent opens them

~4.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

• NoteMentions a .env fileSKILL.md:3

  ion, the local Edge Delivery dev server, .env / AEM_* configuration, HTTPS/TLS, proxy and certificate trust, content syn

• NoteMentions a .env fileSKILL.md:98

  ## 3. `.env` Configuration

• NoteMentions a .env fileSKILL.md:100

  All options can be persisted in `.env` at the project root; loaded automatically. `[verified]`

• NoteMentions a .env fileSKILL.md:103

  # .env example

• NoteMentions a .env fileSKILL.md:139

  ### Persisting TLS in .env

• NoteMentions a .env fileSKILL.md:162

  set it in the shell profile or CI, not `.env`.

• NoteMentions a .env fileSKILL.md:267

  mypath` (or `AEM_HTML_FOLDER=mypath` in `.env`) |

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from adobe/skills at commit cbc9952, republished under its Apache-2.0 licence (© adobe). 882 words, ~2,594 tokens.

name

aem-cli

description

Use this when installing, running, or configuring the Adobe AEM CLI (@adobe/aem-cli, formerly the helix-cli npm package; commands `aem up`, `aem import`, `aem content`), when `aem up` fails (port conflicts, cert errors, proxy 404s, pipeline vs. local-file confusion), or when migrating from the old helix-cli package. Covers installation, the local Edge Delivery dev server, .env / AEM_* configuration, HTTPS/TLS, proxy and certificate trust, content sync with da.live, and troubleshooting. For da.live content-format rules or the DA Source API contract use da-content; for writing EDS block code use content-driven-development.

license

Apache-2.0

metadata.version

1.0.0

# Global install
npm install -g @adobe/aem-cli

# One-off via npx (no global install needed)
npx -y @adobe/aem-cli up

aem --version   # or: hlx --version

npm uninstall -g @adobe/helix-cli
npm install -g @adobe/aem-cli

aem up --no-open --forward-browser-logs

curl -s -o /dev/null -w "%{http_code}" http://localhost:3000
# Expected: 200

aem up --html-folder drafts --no-open --forward-browser-logs
# Files in ./drafts/ are served at /drafts/<name> (no extension needed)

# .env example
AEM_PORT=8080
AEM_PAGES_URL=https://stage.myproject.com
AEM_FORWARD_BROWSER_LOGS=true
AEM_HTML_FOLDER=drafts
AEM_TLS_CERT=server.crt
AEM_TLS_KEY=server.key
AEM_OPEN=/products

mkcert -install                                          # one-time CA install
mkcert -cert-file server.crt -key-file server.key localhost 127.0.0.1
aem up --tls-cert server.crt --tls-key server.key

openssl req -new -newkey rsa:4096 -x509 -sha256 -days 365 -nodes \
  -out server.crt -keyout server.key -subj "/CN=localhost"
aem up --tls-cert server.crt --tls-key server.key

AEM_TLS_CERT=server.crt
AEM_TLS_KEY=server.key

# macOS / Linux
export NODE_EXTRA_CA_CERTS=/path/to/corporate-ca.crt
aem up

# Windows
set NODE_EXTRA_CA_CERTS=./certs/corporate-ca.pem
aem up

aem import                   # opens Importer UI in browser at port 3001
aem import --no-open         # headless / background start
aem import --port 3002       # different port

aem content clone [--path /]   # auth via browser popup; clones into ./content/
aem content status             # show added / modified / deleted files
aem content diff [path]        # diff local vs remote
aem content merge [path]       # sync remote changes into local files
aem content add <files..>      # stage changes (like git add)
aem content commit -m "..."    # commit staged changes (like git commit)
aem content push               # upload committed changes to da.live
aem content push --force       # overwrite remote on conflict

TOKEN=$(jq -r .access_token .hlx/.da-token.json)

curl -sI https://content.da.live/<org>/<repo>/path/to/image.png | grep -i "content-type"

TOKEN=$(jq -r .access_token .hlx/.da-token.json)
curl -X POST \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: image/png" \
  --data-binary @./image.png \
  "https://admin.da.live/source/<org>/<repo>/path/to/image.png"

curl -X POST \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: text/html" \
  --data-binary @./page.html \
  "https://admin.da.live/source/<org>/<repo>/path/to/page.html"

© adobe, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files (references) in plugins/aem/edge-delivery-services/skills/aem-cli of adobe/skills.

• SKILL.md
• .releaserc.json
• CHANGELOG.md
• package.json
• references/command-reference.md

Open the folder on GitHubat commit cbc9952