Source profileQuality 72/100Review permissions

sonichi/sutando/skills/overlay-apps/SKILL.md

overlay-apps

Framework + minimal example for Sutando desktop overlay applications — always-on-top, frameless Electron windows that float over the desktop, controllable from the Sutando web UI's /overlays manager. Ships one example overlay (System Resources). Add new overlays by registering them in app/main.js.

Source repository stars
359
Declared platforms
0
Static risk flags
1
Last source update
2026-07-28
Source checked
2026-07-28

Decision brief

What it does—and where it fits

A small framework for Sutando desktop overlays: always-on-top, frameless, transparent Electron windows that float over whatever you're working on, controllable from the web UI's /overlays manager view.

Best for

    Not for

    • Tasks that require unconfirmed production actions or broad system permissions.
    • Environments where the pinned source and install steps cannot be inspected.

    Compatibility matrix

    Platform support, with evidence labels

    PlatformStatusEvidenceWhat to check
    CodexNot declaredNo explicit evidencePortability before use
    Claude CodeNot declaredNo explicit evidencePortability before use
    CursorNot declaredNo explicit evidencePortability before use
    Gemini CLINot declaredNo explicit evidencePortability before use
    Open the compatibility checker

    Installation

    Inspect first. Install second.

    The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

    Source-detected install commandSource
    npx skills add https://github.com/sonichi/sutando --skill "skills/overlay-apps"
    Safe inspection promptEditorial

    Inspect the Agent Skill "overlay-apps" from https://github.com/sonichi/sutando/blob/6a8f0fccd32e5aa620a3572c8885544f144bb6fe/skills/overlay-apps/SKILL.md at commit 6a8f0fccd32e5aa620a3572c8885544f144bb6fe. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

    Workflow

    What the source asks the agent to do

    1. 01

      Ships with

      One example overlay: System Resources — live CPU / memory / disk / network / load (Cmd+Shift+S). The framework is overlay-agnostic; the example is just a working starting point.

      One example overlay: System Resources — live CPU / memory / disk / network / load (Cmd+Shift+S). The framework is overlay-agnostic; the example is just a working starting point.
    2. 02

      Layout — workspace contract

      scripts/launch.sh syncs source → workspace, installs dependencies, and starts the app.

      Source of truth: skills/overlay-apps/app/ (in the repo).Running instance: /overlay-apps/benchmark-overlay/- Source of truth: skills/overlay-apps/app/ (in the repo). - Running instance: /overlay-apps/benchmark-overlay/ — nodemodules and any local state live here, not in the repo. Code in the repo, mutable runtime in the work…
    3. 03

      Launch

      Review the “Launch” section in the pinned source before continuing.

      Review and apply the “Launch” source section.
    4. 04

      Adding a new overlay

      1. Drop in app/.html and app/-renderer.js. 2. Register it in OVERLAYS in app/main.js:

      Drop in app/.html and app/-renderer.js.Register it in OVERLAYS in app/main.js:If your overlay needs data, add an IPC handler in main.js and expose it

    Permission review

    Static risk signals and limitations

    Runs scripts

    medium · line 39

    The documentation asks the agent to run terminal commands or scripts.

    bash skills/overlay-apps/scripts/launch.sh

    Evidence record

    Why each signal appears

    EvidenceSourceComputedTestedEditorial
    SignalValueEvidence typeMeaning
    Quality score72/100ComputedDocumentation, specificity, maintenance, and trust rules
    Repository stars359SourceRepository attention, not individual Skill quality
    Compatibility0 platformsSourceDeclared in the catalog source record
    Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

    Pinned source

    Provenance and original SKILL.md

    Repository
    sonichi/sutando
    Skill path
    skills/overlay-apps/SKILL.md
    Commit
    6a8f0fccd32e5aa620a3572c8885544f144bb6fe
    License
    MIT
    Collected
    2026-07-28
    Default branch
    main
    View the original SKILL.md

    Overlay Apps

    A small framework for Sutando desktop overlays: always-on-top, frameless, transparent Electron windows that float over whatever you're working on, controllable from the web UI's /overlays manager view.

    The framework gives you, for free:

    • A localhost control server the web UI manager talks to (open / close / show / hide / opacity / always-on-top).
    • Multi-display placement — move every overlay to a chosen monitor; the choice persists across restarts.
    • Auto-dim on app blur — overlays fade to ~20% opacity when you click into another app, restore to their configured opacity when you click an overlay back.
    • A simple OVERLAYS registry — add a new overlay by registering it.

    Ships with

    One example overlay: System Resources — live CPU / memory / disk / network / load (Cmd+Shift+S). The framework is overlay-agnostic; the example is just a working starting point.

    Layout — workspace contract

    • Source of truth: skills/overlay-apps/app/ (in the repo).
    • Running instance: <workspace>/overlay-apps/benchmark-overlay/node_modules and any local state live here, not in the repo. Code in the repo, mutable runtime in the workspace, per the Sutando workspace contract. <workspace> resolves via bash scripts/sutando-config.sh workspace (M0 helper, PR #1395) — defaults to <repo>/workspace/.

    scripts/launch.sh syncs source → workspace, installs dependencies, and starts the app.

    Launch

    bash skills/overlay-apps/scripts/launch.sh
    

    Requires Node.js.

    Adding a new overlay

    1. Drop in app/<your>.html and app/<your>-renderer.js.
    2. Register it in OVERLAYS in app/main.js:
      yourId: {
        name: 'Your Overlay',
        file: 'your.html',
        w: 320, h: 380,
        shortcut: 'CommandOrControl+Shift+Y',
        win: null,
        config: { opacity: 1, alwaysOnTop: true },
      },
      
    3. If your overlay needs data, add an IPC handler in main.js and expose it via preload.js; renderers call window.overlay.<your-method>().

    That's it — control-server, manager-UI, multi-display and auto-dim all pick it up automatically.

    Control surface

    The app runs a localhost control server (port 7849+) and writes a discovery file to <workspace>/state/overlay-control.json. The web UI's /overlays view proxies to it. Endpoints:

    MethodPathPurpose
    GET/overlayslist overlays + state + bounds
    GET/displaysconnected monitors
    POST/overlays/:id/{open,close,show,hide}window lifecycle
    POST/overlays/:id/config{opacity, alwaysOnTop}
    POST/overlays/display{index} — move all to a display

    Alternatives

    Compare before choosing

    Computed 10042,015

    coreyhaines31/marketingskills

    ab-testing

    When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program

    Computed 10042,015

    coreyhaines31/marketingskills

    churn-prevention

    When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers o

    Computed 1007

    event4u-app/agent-config

    design-intelligence

    Grounded design brief from the adopted corpus — style, WCAG-checked color tokens, typography, layout pattern, anti-patterns. Use on ui-design-brief or any which-style/palette/font/chart decision.

    Computed 1007

    event4u-app/agent-config

    design-system-capture

    Write and maintain DESIGN.md + PRODUCT.md — captures visual decisions and interaction patterns so design tasks stay consistent across sessions without re-scanning past work.