Skills for building AEM Edge Delivery Services sites — site creation, block development, content modeling, code review, testing, and page import.
91%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
The text of this part of SKILL.md, which keeps the heading and points here. "Above" and "below" refer to the order of the sections in that file.
Verify the run can actually complete before reading the design or writing to DA — a missing prerequisite caught here is one actionable message; caught mid-run it is a confusing, half-built page. Run these checks in order and, on the first that fails, stop with the specific remediation below — do not proceed on a guess or a partial capability.
whoami, or listing its tools). If no Figma MCP tool is
available at all, stop: "No Figma MCP is connected. Connect one (Claude
desktop Dev Mode, an IDE Figma integration, or a remote Figma MCP) and
re-run." Record the authenticated identity (whoami) for the next check.fileKey (e.g. get_metadata scoped to the frame, or get_design_context
on the node). A permission / not-found error (403/404/"no access")
means the file is not shared with the authenticated account → stop: "Figma
reports no access to <fileKey> as <whoami>. Share the file with that
account, switch accounts, or provide a file you can open." Distinguish this
from a transport cap — a truncated, garbled, or JSON-parse-error response is
the size cap (see Phase 1), not an access failure: retry narrower, do not
report it as no access.DA_TOKEN is obtainable via da-auth
— prefer a $DA_TOKEN already set in the session, else the helper cache at
~/.aem/da-token.json, else freshly minted. If the cache exists but can't be
read because this execution sandbox has no $HOME access, the token is not
missing — it is unreachable; do not loop re-minting. Stop with that
distinction spelled out: "A DA token exists but this sandbox can't read
~/.aem/da-token.json — run where the cache is readable, or provide the token
as $DA_TOKEN (or a readable path)." If no token can be obtained at all,
stop: "Can't obtain a DA token (da-auth) — authenticate to DA and re-run."
Either way, don't spend a full Figma read only to fail at the deploy step.blocks/ and to add new-block code) and the skills
this one orchestrates (da-auth, da-content, the block skills) are
available. If the checkout path is unknown, ask for it.On all-pass, print a one-line preflight summary — Figma identity, the file/frame,
and the DA org/repo + branch you will write to — then proceed to Phase 1.
.tessl-plugin
skills
aem-block-library
aem-cli
aem-layout-view
block-collection-and-party
brand-setup
references
building-blocks
code-review
content-driven-development
references
content-modeling
create-site
da-auth
figma-to-content
find-test-content
generate-import-html
identify-page-structure
migrate-header
page-decomposition
page-import
preview-import
scrape-webpage
slicc-handoff
snowflake
assets
substrate
substrate-milo
examples
knowledge
scripts
testing-blocks
ue-component-model