本文へ移動
cccskills
無料GitHub で公開

slicc-handoff

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.

aemgdc/aemdev
インストール方法を見る

含まれるファイル（5）

  • SKILL.md4.7 KB
  • .releaserc.json49 B
  • CHANGELOG.md636 B
  • package.json93 B
  • scripts/slicc-handoff3.9 KB

SKILL.md（原文）

インストールする前に、エージェントに与えられる指示の中身を確認できます。

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

  1. 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.

  2. 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.

  3. 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>"

  4. 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 fetch and AbortSignal.timeout APIs).
  • A browser opener available on the host (open on macOS, xdg-open on Linux, cmd /c start on 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 --open when no local SLICC server is running.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

ログインしてレビューを書く

同じリポジトリのスキル

概要と使いどころ

aa-conversion-funnel-analysis

無料

Analyzes a multi-step conversion funnel to find where visitors drop off and which steps have the worst leakage. Use this skill when someone describes a journey and asks about conversion rates, drop-off, fallout, or step completion. Trigger for "analyze our checkout funnel," "where are visitors dropping off," "what's our add-to-cart to purchase conversion rate," "funnel analysis," "show me fallout between steps," or "which step loses the most visitors."

日本語の概要は準備中です。原文の説明を表示しています。

aemgdc/aemdev22026年10月10日 更新

aa-executive-briefing

無料

Generates a concise, executive-ready performance summary covering key metrics, trends, and what's driving movement. Use this skill when someone needs to produce a briefing, executive summary, performance narrative, or stakeholder readout — for example, "write an exec summary of last week's performance," "create a performance briefing for our leadership team," "produce a monthly business review summary," "what should I tell executives about our metrics," or "generate a performance narrative." Also trigger for "QBR summary," "weekly business review," or "stakeholder briefing."

日本語の概要は準備中です。原文の説明を表示しています。

aemgdc/aemdev22026年10月10日 更新

aa-kpi-pulse

無料

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 "give me a performance overview," "what moved in the last 7 days," "pull our AA KPI report," or "summarize our metrics."

日本語の概要は準備中です。原文の説明を表示しています。

aemgdc/aemdev22026年10月10日 更新

aa-segment-performance-comparator

無料

Compares the performance of two or more audience segments across key metrics side by side. Use this skill when someone wants to compare audiences or visitor groups — for example, "how do mobile visitors compare to desktop 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" or "audience comparison."

日本語の概要は準備中です。原文の説明を表示しています。

aemgdc/aemdev22026年10月10日 更新

aa-top-movers-watchlist

無料

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.

日本語の概要は準備中です。原文の説明を表示しています。

aemgdc/aemdev22026年10月10日 更新

accessibility-fix

無料

Scan an AEM Edge Delivery Services page for WCAG 2.1 AA accessibility violations and generate specific fixes. Identifies missing alt text, heading hierarchy issues, link text problems, color contrast concerns, and EDS-specific accessibility patterns. Use when fixing accessibility issues, preparing for compliance audits, or remediating WCAG violations.

日本語の概要は準備中です。原文の説明を表示しています。

aemgdc/aemdev22026年10月10日 更新

aemgdc のスキルをすべて見る

このスキルの問題を報告する