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.
What this skill does
# SLICC Handoff
This skill bridges the current coding agent and the [SLICC](https://www.sliccy.ai) 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`](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`:
```bash
node .claude/skills/slicc-handoff/scripts/slicc-handoff --open "handoff:<instruction>"
```
```bash
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:
```bash
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`](https://www.sliccy.ai/llms.txt) and the linked handoff protocol reference.
## Examples
Continue an in-progress signup flow in the browser:
```bash
node .claude/skills/slicc-handoff/scripts/slicc-handoff --open "Continue the signup flow in the browser"
```
Install a skill collection from a GitHub repo:
```bash
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):
```bash
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.
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.