Run any Skill in Manus with one click

gnome-script-launchers

Stars4

Forks0

UpdatedJuly 4, 2026 at 18:18

Use when creating, updating, troubleshooting, or organizing Ubuntu GNOME dock buttons, .desktop launchers, Zenity control menus, script shortcuts, launcher icons, or taskbar actions for commands stored across multiple projects.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

ton-anywhere

ton-anywhere/my-favorite-prompts

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

2 files

SKILL.md

readonly

name	gnome-script-launchers
description	Use when creating, updating, troubleshooting, or organizing Ubuntu GNOME dock buttons, .desktop launchers, Zenity control menus, script shortcuts, launcher icons, or taskbar actions for commands stored across multiple projects.

GNOME Script Launchers

Overview

Create maintainable GNOME launchers that expose scripts as individual dock buttons or as actions in one Zenity control menu. Keep project commands in their projects and keep the desktop entry thin.

Workflow

Inspect the desktop environment and dependencies: zenity, notify-send, and update-desktop-database.
Inventory each action, its absolute command path, interactivity, failure behavior, and destructive impact.
Read existing dispatcher and .desktop files before editing; preserve unrelated actions and user customization.
Store the dispatcher in the owning project and the launcher in ~/.local/share/applications/<id>.desktop.
Validate paths and syntax, refresh the application database, then explain how to search for and pin the launcher.

Choose the UI

Create one .desktop file per action when the user explicitly wants several independent dock icons.
Create one Zenity dispatcher when actions belong together or would clutter the dock.
Use Terminal=false for non-interactive commands with graphical feedback.
Use Terminal=true or launch a terminal when a command requires input, passwords, or sustained log viewing.

Implementation Rules

Use absolute paths in Exec= and dispatcher actions; .desktop files do not reliably inherit the user's interactive shell environment.
Run aliases or shell functions through the intended interactive shell, such as /usr/bin/zsh -lic 'command'.
Quote action labels and paths defensively; do not construct executable commands from untrusted menu text.
Treat menu cancellation as a clean exit.
Show success only when the command exits successfully; display captured errors otherwise.
Add a confirmation dialog before reboot, shutdown, sleep, deletion, or other disruptive actions.
Use an icon-theme name or an absolute existing PNG/SVG path in Icon=.
Do not rewrite GNOME favorites with gsettings unless the user explicitly asks to pin or reorder icons.
Ask for approval before writing outside the active workspace when permissions require it.

Desktop Entry

Use this minimal shape:

[Desktop Entry]
Type=Application
Name=Control Menu
Comment=Run maintenance actions
Icon=utilities-system-monitor
Exec=/absolute/path/to/control-menu.sh
Terminal=false
Categories=Utility;

Verification

Run:

bash -n /absolute/path/to/control-menu.sh
desktop-file-validate ~/.local/share/applications/control-menu.desktop
update-desktop-database ~/.local/share/applications

If desktop-file-validate is unavailable, inspect the required desktop-entry fields manually. If GNOME retains an old icon, remove and re-add the favorite after refreshing the database.

More from this repository

same repository

atomic-git-commits

ton-anywhere/my-favorite-prompts

Invoke immediately if the Navigator mentions: inspecting changes (status, diff, log, show), staging/adding files (add, stage), creating commits (commit, amend, reset), branch management (branch, checkout, merge, rebase), remote operations (push, pull, fetch), or repository state (stash, worktree). Trigger words: git, commit, status, diff, add, stage, branch, merge, push, pull, log, revert, stash, worktree, 'what changed', 'save changes', 'commit this', 'show me the diff'.

2026-07-064

opencode-session-investigation

ton-anywhere/my-favorite-prompts

Use when investigating opencode sessions, subsessions, agent drift, missed handoffs, tool misuse, or feedback grounded in opencode session exports.

2026-06-284

front-end-tutor

ton-anywhere/my-favorite-prompts

Guide a user with basic CSS knowledge who is learning Tailwind CSS and frontend styling. Use when the user asks for help styling a page, layout, component, tag, or UI state and wants coaching through style categories, good frontend practices, CSS mental models, or Tailwind decision-making without being given the finished code solution.

2026-06-264

ai-server-memory-diagnostics

ton-anywhere/my-favorite-prompts

Use when investigating swap, memory pressure, compressor usage, llama.cpp memory, Metal/unified memory, or model-server RAM issues on the Mac Studio ai-server.

2026-06-214

llm-council

ton-anywhere/my-favorite-prompts

Run any question, idea, or decision through a council of 5 AI advisors who independently analyze it, peer-review each other anonymously, and synthesize a final verdict. Based on Karpathy's LLM Council methodology. MANDATORY TRIGGERS: 'council this', 'run the council', 'war room this', 'pressure-test this', 'stress-test this', 'debate this'. STRONG TRIGGERS (use when combined with a real decision or tradeoff): 'should I X or Y', 'which option', 'what would you do', 'is this the right move', 'validate this', 'get multiple perspectives', 'I can't decide', 'I'm torn between'. Do NOT trigger on simple yes/no questions, factual lookups, or casual 'should I' without a meaningful tradeoff (e.g. 'should I use markdown' is not a council question). DO trigger when the user presents a genuine decision with stakes, multiple options, and context that suggests they want it pressure-tested from multiple angles.

2026-05-314

code-comments

ton-anywhere/my-favorite-prompts

Use when writing new code or reviewing existing code to decide which comments to add, keep, or remove. Defines what makes a comment valuable vs. noise.

2026-05-314

name	gnome-script-launchers
description	Use when creating, updating, troubleshooting, or organizing Ubuntu GNOME dock buttons, .desktop launchers, Zenity control menus, script shortcuts, launcher icons, or taskbar actions for commands stored across multiple projects.

GNOME Script Launchers

Overview

Create maintainable GNOME launchers that expose scripts as individual dock buttons or as actions in one Zenity control menu. Keep project commands in their projects and keep the desktop entry thin.

Workflow

Inspect the desktop environment and dependencies: zenity, notify-send, and update-desktop-database.
Inventory each action, its absolute command path, interactivity, failure behavior, and destructive impact.
Read existing dispatcher and .desktop files before editing; preserve unrelated actions and user customization.
Store the dispatcher in the owning project and the launcher in ~/.local/share/applications/<id>.desktop.
Validate paths and syntax, refresh the application database, then explain how to search for and pin the launcher.

Choose the UI

Create one .desktop file per action when the user explicitly wants several independent dock icons.
Create one Zenity dispatcher when actions belong together or would clutter the dock.
Use Terminal=false for non-interactive commands with graphical feedback.
Use Terminal=true or launch a terminal when a command requires input, passwords, or sustained log viewing.

Implementation Rules

Use absolute paths in Exec= and dispatcher actions; .desktop files do not reliably inherit the user's interactive shell environment.
Run aliases or shell functions through the intended interactive shell, such as /usr/bin/zsh -lic 'command'.
Quote action labels and paths defensively; do not construct executable commands from untrusted menu text.
Treat menu cancellation as a clean exit.
Show success only when the command exits successfully; display captured errors otherwise.
Add a confirmation dialog before reboot, shutdown, sleep, deletion, or other disruptive actions.
Use an icon-theme name or an absolute existing PNG/SVG path in Icon=.
Do not rewrite GNOME favorites with gsettings unless the user explicitly asks to pin or reorder icons.
Ask for approval before writing outside the active workspace when permissions require it.

Desktop Entry

Use this minimal shape:

[Desktop Entry]
Type=Application
Name=Control Menu
Comment=Run maintenance actions
Icon=utilities-system-monitor
Exec=/absolute/path/to/control-menu.sh
Terminal=false
Categories=Utility;

Verification

Run:

bash -n /absolute/path/to/control-menu.sh
desktop-file-validate ~/.local/share/applications/control-menu.desktop
update-desktop-database ~/.local/share/applications

If desktop-file-validate is unavailable, inspect the required desktop-entry fields manually. If GNOME retains an old icon, remove and re-add the favorite after refreshing the database.