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
This skill bridges the current coding agent and the SLICC browser agent. It builds and dispatches a structured handoff that SLICC surfaces to the user as a yes/no approval card.
It supports two verbs:
handoff:<instruction> — continue the current task inside SLICC.upskill:<github-url> — ask SLICC to install a skill from a GitHub repository.For canonical SLICC protocol, API, and documentation references, fetch https://www.sliccy.ai/llms.txt — it is the maintainer-curated, machine-readable index for LLM consumers and is the authoritative source for the handoff/upskill rels, the public API catalog, and links to the protocol and architecture docs.
Use this skill when the user wants to:
Do not use this skill when:
Compose a single-line, action-oriented instruction that captures what SLICC should do next. Include enough context for SLICC to pick up the work without your conversation history.
Pick a verb prefix:
handoff:<instruction> to continue a task.upskill:<github-url> to install a skill. The URL can be the repo root or a tree/<branch>/<sub/path> URL to install only a sub-path of the repo.Run the helper script with --open:
node .claude/skills/slicc-handoff/scripts/slicc-handoff --open "handoff:<instruction>"node .claude/skills/slicc-handoff/scripts/slicc-handoff --open "upskill:<github-url>"Tell the user that SLICC will show an approval prompt in its Chat tab, and they should accept it to dispatch the handoff.
If the user runs a non-default SLICC instance on another port, prefix the call with SLICC_PORT=5720 (or whatever port they chose) so the localhost POST hits the right instance:
SLICC_PORT=5720 node .claude/skills/slicc-handoff/scripts/slicc-handoff --open "handoff:<instruction>"The script builds a https://www.sliccy.ai/handoff?<verb>=<urlencoded-payload> URL and dispatches it through two parallel paths — a profile-independent localhost POST to a SLICC CLI/Electron float, and (with --open) a real browser navigation that the SLICC extension picks up via an RFC 8288 Link header. Either path surfaces a yes/no approval card in the SLICC cone, dispatched by verb prefix once accepted. For the full protocol details (rel URIs, payload shape, public API catalog), see https://www.sliccy.ai/llms.txt and the linked handoff protocol reference.
Continue an in-progress signup flow in the browser:
node .claude/skills/slicc-handoff/scripts/slicc-handoff --open "Continue the signup flow in the browser"Install a skill collection from a GitHub repo:
node .claude/skills/slicc-handoff/scripts/slicc-handoff --open "upskill:https://github.com/slicc/skills-extra"Install only a single skill (a sub-path of a repo on a specific branch):
node .claude/skills/slicc-handoff/scripts/slicc-handoff --open "upskill:https://github.com/slicc/skills-extra/tree/main/skills/foo"fetch and AbortSignal.timeout APIs).open on macOS, xdg-open on Linux, cmd /c start on Windows).localhost:${SLICC_PORT ?? 5710} (CLI/Electron float) or via the SLICC extension installed in the browser profile that opens the URL.--open when no local SLICC server is running..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