cherry

Drive SLICC cherry followers via postMessage-backed synthetic CDP with host-enforced capability limits.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the challenge of safely interacting with third-party web pages that have embedded SLICC cherry followers, which operate under strict, host-defined capability limits and cannot be controlled like standard, fully-owned browser tabs.

Core Features & Use Cases

  • Unified Browser Automation: Drive cherry targets using the same playwright, BrowserAPI, and teleport tools you use for regular browser tabs, with automatic enforcement of the host's advertised capability limits.
  • Bidirectional Event Communication: Use the cherry-emit command to push custom events to the host page, and parse incoming [cherry] event licks from the host to react to page-side changes in real time.
  • Use Case: For example, automate workflows on a third-party SaaS tool that has integrated the SLICC cherry SDK: navigate its interface, trigger data refresh events via cherry-emit, and respond to task update events sent back from the host, all without accessing its raw network traffic.

Quick Start

Use the cherry skill to navigate the connected cherry target to its account settings page, emit a refresh-data event to the host page, and capture a screenshot of the updated settings interface.

Frequently Asked Questions about cherry

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

FAQPage Schema
How do I automate browser tasks on embedded third-party web pages with capability limits?

Browser automation on embedded third-party web pages is achieved by using postMessage-backed synthetic CDP, allowing you to navigate and interact with SLICC cherry targets while enforcing strict host-defined capability limits.

Can I use playwright to control a SLICC cherry target embedded in a host page?

Yes, you can use playwright to drive cherry targets because the skill provides unified browser automation that integrates with standard tools while automatically enforcing the host page's advertised capability limits.

How do I push custom events to a host page from an embedded web target?

You push custom events to a host page from an embedded web target by using the cherry-emit command, which facilitates bidirectional event communication without requiring raw network access to the cherry targets.

How do I parse incoming cherry event licks from a host page during browser automation?

Parsing incoming cherry event licks from a host page is handled by structured parsing functionality that captures [cherry] events, enabling real-time reactions to page-side changes during your browser automation workflows.

Does browser automation for embedded third-party targets allow raw network access?

No, browser automation for embedded third-party targets blocks all raw network access to cherry targets, strictly enforcing the capability limits set by the host page to ensure safe interaction.

What is the best way to interact with a third-party SaaS tool that integrated the SLICC cherry SDK?

The best way to interact with a third-party SaaS tool using the SLICC cherry SDK is to automate its interface, trigger data refresh events via cherry-emit, and respond to task update events sent back from the host page.