slicc-handoff
Skill37 starsChanged 20 days agoApache-2.0View on GitHub
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 in the SLICC browser agent or install a skill into it.
In this repository9 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- docs/CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- adding-slicc-featuresSkill
- cdp-smoke-testSkill
- demo-recordingSkill
- deploying-tray-workerSkill
- verifying-before-pushSkill
- writing-slicc-testsSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 9
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 …
- Very specific: line 17
Run the script with --open to open the handoff URL.
- Very specific: line 22
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 …
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
slicc-handoff
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 in the SLICC browser agent or install a skill into it.
What to do
- Compose a single-line, action-oriented instruction.
- Pick a verb prefix:
handoff:<instruction>— continue the task in SLICC.upskill:<github-url>— ask SLICC to install a skill from a GitHub repo.
- Run the script with
--opento open the handoff URL. Show one of:.agents/skills/slicc-handoff/scripts/slicc-handoff --open "handoff:<instruction>".agents/skills/slicc-handoff/scripts/slicc-handoff --open "upskill:<github-url>"
- Tell the user SLICC will show an approval prompt in the Chat tab.
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.
How it works
The script builds a URL like https://www.sliccy.ai/handoff?handoff=<urlencoded> (or ?upskill=<urlencoded-github-url>). Two delivery paths fire in parallel:
- Localhost POST to
http://localhost:${SLICC_PORT ?? 5710}/api/handoffwith the structured payload{ verb, target, instruction?, url, title }—verbishandofforupskill,targetis the github URL for upskill or the handoff URL for handoff, andinstructioncarries the prose for handoff. The local server (node-server or the Sliccstart swift-server) rebroadcasts it as anavigatelick to the connected webapp. Profile-independent: reaches SLICC even when the user's default browser is a different Chrome profile than the one SLICC controls. --openopens the URL in the local browser. If that browser profile has the SLICC extension installed,chrome.webRequestparses the response's RFC 8288Linkheader (relhttps://www.sliccy.ai/rel/handofforhttps://www.sliccy.ai/rel/upskill) and emits the navigate lick when one of those rels is present.
Either path results in a navigate lick in the cone. A handoff: shows a yes/no approval card the user must accept (the card flips to ✓/✗ on their click); an upskill: is installed when the cone calls lick_confirm (or skipped via lick_dismiss). See /workspace/skills/handoff/SKILL.md.
Examples
.agents/skills/slicc-handoff/scripts/slicc-handoff --open "Continue the signup flow in the browser".agents/skills/slicc-handoff/scripts/slicc-handoff --open "upskill:https://github.com/slicc/skills-extra"Install only a sub-path of a repo (a single skill on a specific branch):
.agents/skills/slicc-handoff/scripts/slicc-handoff --open "upskill:https://github.com/slicc/skills-extra/tree/main/skills/foo"Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

