handoff

Process SLICC navigate lick events from RFC 8288 Link headers.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When a user opens a browser tab whose response includes a SLICC-specific RFC 8288 Link header, the agent needs to correctly process the resulting navigate lick event without accidentally executing untrusted actions or skipping required user approvals for sensitive operations.

Core Features & Use Cases

  • Dual Verb Handling: Distinguishes between handoff (human-gated task handoffs from external agents) and upskill (agent-actionable skill installations from public GitHub repos) events.
  • Safety Guardrails: Enforces mandatory user approval for all handoff events, prevents premature fetching of handoff target content, and avoids auto-accepting untrusted external instructions.
  • Safe Inspection: Supports read-only pre-approval checking of link headers and post-approval discovery of origin capabilities via the discover command.
  • Use Case: If a user opens a tab that advertises a SLICC handoff for a cross-agent coding task, this skill ensures the agent only proceeds after the user explicitly approves the external instruction, preventing unintended execution of untrusted code.

Quick Start

Use the handoff skill to process a navigate lick event for a SLICC handoff or upskill link, following the appropriate approval and installation workflow for the detected verb type.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I process an RFC 8288 Link header advertising a SLICC handoff action?

To process an RFC 8288 Link header for a SLICC handoff, the skill intercepts navigate lick events and enforces mandatory human approval before fetching target content or executing cross-agent tasks. It prevents unintended execution of untrusted external instructions.

What is the safest way to inspect SLICC link targets before approving a handoff?

The safest way to inspect SLICC link targets is using the discover command, which provides read-only pre-approval checking of link headers and post-approval discovery of origin capabilities without executing untrusted actions.

How do I install new agent skills from a public GitHub repository using an upskill link?

To install new agent skills via an upskill link, the skill processes the SLICC navigate lick event and supports scoped GitHub skill installation directly into the agent runtime from the advertised public repository.

Can I auto-accept external instructions from cross-agent handoff events?

No, you cannot auto-accept external instructions. The skill enforces safety guardrails requiring mandatory user approval for all handoff events to prevent premature fetching and avoid auto-accepting untrusted external instructions.

Does the handoff skill distinguish between cross-agent task handoffs and upskill events?

Yes, the skill provides dual verb handling to distinguish between handoff events, which are human-gated task handoffs from external agents, and upskill events, which are agent-actionable skill installations from public GitHub repos.

When do I need to handle SLICC navigate lick events in a browser-native agent workflow?

You need to handle SLICC navigate lick events when a user opens a browser tab whose HTTP response includes a SLICC-specific RFC 8288 Link header, requiring correct processing to avoid skipping user approvals for sensitive operations.