ai-ecoverse

Manage a LinkedIn company page — publish posts with consistent brand voice, grow engagement, respond to comments, analyze performance, preview profiles, and aggregate engagement for the monday dispatcher. Maintains a knowledge base of content ideas, audience insights, and brand guidelines. Use when the user wants to publish a LinkedIn post, draft LinkedIn content, check LinkedIn comments, respond to engagement, plan content strategy, review brand voice, view a LinkedIn profile, or manage a company page. Activate on mentions of LinkedIn, LinkedIn post, company page, social media, content calendar, engagement, brand voice, or audience growth.

Interact with Microsoft Teams via the Graph API — read messages, post to channels, search, read threads, look up users, view mentions/activity, and get channel info. Supports all teams and channels the user has access to, with auth via the live browser session. Use when the user wants to check Teams messages, post a Teams message, search Teams channels, read a thread, get user info, view mentions, or automate any Teams task. Triggers on mentions of Teams, channels, messages, threads, mentions, activity, or digest.

Use this when the user wants to annotate, inspect, or leave element-level feedback on a local HTML page served in a browser tab. Injects a hover-highlight + click-to-annotate interaction into the target page. Annotations are sent as licks to a scoop that applies the user's instructions as AI-driven edits to the HTML. Use when the user says "annotate this page", "let me mark up elements", "add speck", "inspect elements with notes", or "inject speck".

Interact with GitHub via gh.jsh — a lightweight GitHub CLI for SLICC agents. Use this skill for any GitHub task: listing or viewing pull requests, merging PRs, posting comments, checking out branches, viewing issues, inspecting workflow runs, listing releases, searching PRs, managing Actions variables, creating branches, pushing file content, archiving repos, or calling any GitHub API endpoint directly. Trigger on requests like "list open PRs", "check CI status", "merge this PR", "what issues are open", "show the latest release", "post a comment on PR #42", "set a repo variable", "archive this repo", "create a branch", "push this file", or any task involving a GitHub repository.

Generate live-coded music patterns using the Strudel library (JavaScript port of TidalCycles). Use this skill whenever the user wants to create music, beats, melodies, rhythms, or sound patterns in the browser. Triggers on requests like "make some music", "create a beat", "generate a melody", "live code some audio", "play a pattern", "make a drum loop", "compose something", or any request involving Strudel, TidalCycles, or algorithmic music. Also use when the user asks to modify, remix, or explore existing musical patterns.

Interact with Garmin Connect — list activities, view fitness data, inspect health stats, browse devices, and check your profile. Use when the user mentions Garmin, Garmin Connect, activities, fitness tracking, health data, running, cycling, swimming, workouts, GPS watch, devices, activity history, fitness stats, heart rate, steps, or wants to query data from connect.garmin.com. Triggers on phrases like "my Garmin activities", "workout history", "list my runs", "show my Garmin data", "fitness summary", "check my Garmin", "recent activities", "my Garmin devices", or anything requesting health metrics, running stats, cycling data, step counts, heart rate zones, or device information.

Use this when interacting with Jira — fetching issues, searching by JQL, reading comments, or pulling issue detail to use in other workflows. Uses the Jira tab open in the browser for auth (SSO session, no token needed). Activate on any mention of Jira, issue keys (e.g. PROJ-123), JQL queries, or requests to read/find/list Jira tickets.

CLI access to Foursquare/Swarm check-in history, venue visits, and location search via the Foursquare v2 API. Use when the user mentions Foursquare, Swarm, check-ins, venues, venue history, places visited, top venues, location search, or wants stats about where they've been. Supports paginated check-in lookups, category filtering, nearby venue search, full venue detail (rating, hours, personal visit count), and overall check-in statistics with top 5 most-visited venues.

Use this when the user wants to write a new skill, edit an existing one, or understand SLICC's skill system. Covers SKILL.md frontmatter (name, description, allowed-tools), how to write a description that triggers reliably, native `/workspace/skills/` vs compatibility `.agents/` / `.claude/skills/` discovery, and when to ship companion files like `.jsh` scripts or `.bsh` browser hooks.

Use this when the user wants a persistent UI panel — a dashboard, form, editor, report, or visualization that lives alongside the chat. Sprinkles are `.shtml` files under `/shared/sprinkles/` rendered in the side rail or as a full-screen tab. For ephemeral inline widgets, use dips instead. Covers creation, modification, layout constraints, the cone-to-scoop orchestration rules, the `slicc.*` bridge API, and `sprinkle chat` for blocking inline prompts.

Use this when a cherry target is connected — a third-party host web page that has embedded a SLICC follower via the @ai-ecoverse/cherry SDK and lent itself to you (a cloud-cone leader) as a driveable, capability-limited browser target. Covers what you can and cannot do with a cherry target (navigate / screenshot / open URL, NEVER raw network), the `cherry-emit` command for pushing host-page events, and the `[cherry]` licks you receive when the host page reports an event.

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.

Use this whenever a response could benefit from richer visualization, guided interaction, or a touch of fun — pickers, calculators, sliders, mini explorers, charts, animated demos, choose-your-own-adventure prompts, anything that lands better as a hydrating widget than as plain prose. Dips are ephemeral `shtml` code blocks rendered inline in chat (no state persistence, lick-only). Reach for them generously: every interactive moment the user gets is a moment they don't have to type a clarifying message. For persistent dashboards, editors, or multi-page apps use sprinkles instead.

Search X (formerly Twitter) for real-time posts, sentiment, and citations via xAI's `x_search` server-side tool. Works with any model — the search call runs through your xAI Grok OAuth credentials regardless of which model is steering the cone. Use when you need fresh social-media signal, public reactions, or to find specific posts by keyword, hashtag, or handle.

Use this when you receive a Navigate Event lick — emitted whenever the user opens a tab whose main-frame response advertises a SLICC handoff via an RFC 8288 `Link` header. This skill renders the yes/no approval card the user must accept before anything happens. Covers the `handoff:` and `upskill:` verb prefixes and the security rules (never auto-accept, never fetch before approval).

Use this whenever the user asks to browse, navigate, click, fill a form, scrape, take a screenshot, or otherwise interact with a web page. SLICC drives the browser through the `playwright-cli` shell command (also aliased as `playwright` and `puppeteer`). Read this BEFORE running any browser automation: every tab-operating command requires a `--tab` target id, and multi-agent tab handling has rules you must follow.

A minimal demo skill for x927's app-builder example. Says hello — use when the user greets the agent and asks for a friendly reply.

A second minimal demo skill used to show that x927's Tessl target auto-expands a skills-directory pointer into the per-skill record form Tessl expects.

Ranked GitHub triage — show what needs attention right now. Scans open PRs, issues, local repos, and AI coding sessions, then prioritizes by who acted last. Use when: (1) starting the day or week, (2) triaging GitHub notifications, (3) checking what needs attention, (4) reviewing PR queue, (5) finding stale work. Triggers on: "what should I work on", "Monday morning", "triage my GitHub", "what needs my attention", "check my PRs", "review queue", "It's Monday again", "weekly triage", "what's waiting on me", "GitHub status", "open PRs", "clean my inbox", "dismiss noise", "notification triage", "unread notifications".

Ranked GitHub triage — show what needs attention right now. Scans open PRs, issues, local repos, and AI coding sessions, then prioritizes by who acted last. Use when: (1) starting the day or week, (2) triaging GitHub notifications, (3) checking what needs attention, (4) reviewing PR queue, (5) finding stale work. Triggers on: "what should I work on", "Monday morning", "triage my GitHub", "what needs my attention", "check my PRs", "review queue", "It's Monday again", "weekly triage", "what's waiting on me", "GitHub status", "open PRs", "clean my inbox", "dismiss noise", "notification triage", "unread notifications".