slicc-handoff

Generate handoff or upskill URLs and trigger browser navigation for SLICC.

28|14|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/ai-ecoverse/slicc --skill slicc-handoff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: slicc-handoff
Source: https://github.com/ai-ecoverse/slicc/tree/main/.claude/skills/slicc-handoff
Command: npx skills add https://github.com/ai-ecoverse/slicc --skill slicc-handoff

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Switching context between your local workspace and the SLICC browser agent to continue ongoing tasks or add new capabilities to SLICC requires manual, error-prone steps that break your workflow.

Core Features & Use Cases

  • Task Handoff: Send any ongoing task directly to the SLICC browser agent to continue execution in the browser without manually recreating context.
  • Skill Installation: Upskill SLICC by installing new custom skills directly from public GitHub repositories with a single command.
  • Use Case: If you are debugging a web authentication flow in your local code editor, you can hand off the testing task to SLICC to run in the browser, or install a new web scraping skill to expand SLICC's capabilities instantly.

Quick Start

Use the slicc-handoff skill to hand off your current browser automation task to SLICC to complete it in the browser.

Frequently Asked Questions about slicc-handoff

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I hand off a browser automation task to SLICC without losing context?

Installing a new skill from a public GitHub repository into SLICC requires generating an upskill URL via this skill, which then communicates with the local SLICC node server to trigger browser navigation for user approval of the installation.

Does handing off tasks to the SLICC browser agent require a local node server?

Yes, handing off tasks to the SLICC browser agent requires a running local SLICC node server, which the skill communicates with to generate valid handoff or upskill URLs and trigger the requested browser action.

What is the best way to eliminate manual context switching between local workspaces and a browser agent?

The best way to eliminate manual context switching between local workspaces and the SLICC browser agent is using this skill to send ongoing tasks directly to the browser, generating handoff URLs that preserve your execution context.

Can I upskill SLICC directly from public GitHub repositories?

Yes, you can upskill SLICC directly from public GitHub repositories by using this skill to generate an upskill URL, which prompts the local SLICC node server to trigger browser navigation for user approval of the new custom skill.

Why does SLICC trigger browser navigation when handing off a task or installing a skill?

SLICC triggers browser navigation when handing off a task or installing a skill to require explicit user approval of the requested action, ensuring secure execution of browser-native tasks and GitHub repository installations.