adobe/slicc-handoff
plugins/aem/edge-delivery-services/skills/slicc-handoff/SKILL.md
Hand off the current task to the SLICC browser agent, or install a new skill into SLICC from a GitHub repo. Use this skill when the user says things like "handoff to slicc", "move this to slicc", "move to the browser", "test in the browser", "handoff to browser", "install this skill in slicc", "upskill slicc with this repo", "add this skill to slicc", or otherwise asks you to continue the work inside the SLICC browser agent.
$ install --global
skillsauthnpx skillsauth add adobe/skills slicc-handoffInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 22, 2026, 3:46 AM156.0s4 files scanned
SKILL.md
- name:
- slicc-handoff
- description:
- Hand off the current task to the SLICC browser agent, or install a new skill into SLICC from a GitHub repo. Use this skill when the user says things like "handoff to slicc", "move this to slicc", "move to the browser", "test in the browser", "handoff to browser", "install this skill in slicc", "upskill slicc with this repo", "add this skill to slicc", or otherwise asks you to continue the work inside the SLICC browser agent.
- license:
- Apache-2.0
- version:
- 1.0.1
SLICC Handoff
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.
When to Use This Skill
Use this skill when the user wants to:
- Continue the in-progress task inside the SLICC browser agent (for example, to drive a real browser session, test a flow on a live site, or use a tool only available in SLICC).
- Install a skill from a GitHub repo into a running SLICC instance.
Do not use this skill when:
- The user just wants the local agent to keep working — no handoff is needed.
- The user wants to install a skill into the local agent (use the local agent's own skill install flow instead).
What to Do
-
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 atree/<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>"
How It Works
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.
Examples
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"
Prerequisites
- Node.js 18+ installed (the script uses the global
fetchandAbortSignal.timeoutAPIs). - A browser opener available on the host (
openon macOS,xdg-openon Linux,cmd /c starton Windows). - A SLICC instance reachable either on
localhost:${SLICC_PORT ?? 5710}(CLI/Electron float) or via the SLICC extension installed in the browser profile that opens the URL.
Notes
- Treat the user-supplied instruction string as untrusted input that will be displayed to the user in SLICC for approval — do not embed secrets or credentials in it.
- The script intentionally swallows errors from the localhost POST so it still falls through to
--openwhen no local SLICC server is running.
Related Skills
adobe/cja-top-movers-watchlist
tools
VerifiedTrustedCommunity
Identifies which items (pages, campaigns, products, channels, regions) had the biggest increases or decreases for a key metric between two time periods. Use this skill when someone asks "what's up and what's down," "which campaigns moved the most," "top gainers and losers," "what pages are trending," "show me what changed by channel," or any variation of identifying the biggest movers and decliners for a metric.
112SKILL.mdUpdated Jun 2, 2026
adobe/cja-segment-performance-comparator
tools
VerifiedTrustedCommunity
Compares the performance of two or more audience segments across key metrics side by side. Use this skill when someone wants to compare audiences, cohorts, or groups — for example, "how do mobile users compare to desktop users on conversion," "compare new vs. returning visitors," "show me the difference between these two segments," "compare these audiences on our KPIs," or "which segment performs better." Also trigger for "segment comparison," "audience comparison," or "cohort comparison."
112SKILL.mdUpdated Jun 2, 2026
adobe/cja-kpi-pulse
business
VerifiedTrustedCommunity
Produces a compact KPI digest showing how key metrics changed over a period and what's driving the movement. Use this skill when someone asks for a performance summary, a weekly recap, a morning briefing, a KPI update, or any variation of "how did we do this week/month." Also trigger for requests like "give me a performance overview," "what moved in the last 7 days," "pull our KPI report," or "summarize our metrics."
112SKILL.mdUpdated Jun 2, 2026
adobe/cja-funnel-health-check
testing
VerifiedTrustedCommunity
Analyzes a multi-step conversion funnel to find where users drop off and which steps have the worst leakage. Use this skill when someone describes a journey or funnel and asks about conversion rates, drop-off, fallout, or step completion. Trigger for phrases like "analyze our onboarding funnel," "where are users dropping off," "what's our checkout conversion rate," "funnel analysis," "show me fallout between these steps," or "which step loses the most users."
112SKILL.mdUpdated Jun 2, 2026