ghostty
Purpose
Control the Ghostty terminal emulator via AppleScript. Provides commands to manipulate splits, send input, and display content in new terminal panes.
Prerequisites
- Ghostty terminal emulator must be running on macOS
- glow CLI must be installed for markdown rendering (
brew install glow)
Commands
render-markdown-split
Open a right split in the current Ghostty window and render a markdown file using glow.
Arguments
file(required): Path to the markdown file to render
Workflow
- Resolve the markdown file path to an absolute path
- Verify the file exists and has a
.mdextension - Run the following AppleScript via
osascriptto create a split and render the file:
osascript -e "
tell application \"Ghostty\"
set w to front window
set t to focused terminal of selected tab of w
set t2 to split t direction right
delay 0.5
input text \"glow -p ${ABSOLUTE_FILE_PATH}\" & return to t2
end tell
"
Important Notes
- The
delay 0.5is necessary to allow the new split to initialize before sending input - Always use absolute paths for the file to avoid working directory issues in the new split
- The
-pflag enables pager mode in glow for scrollable output - If
glowis not installed, inform the user and suggestbrew install glow
Error Handling
- If the file does not exist, report the error to the user — do not run the AppleScript
- If
osascriptreturns an error aboutfocused terminal, Ghostty may not be the active application — advise the user to focus Ghostty first
More from kadel/claude-plugins
jira cli usage
This skill should be used when the user asks to "interact with Jira", "list Jira issues", "create Jira issue", "manage sprints", "view epics", "search issues", "move issue status", "assign issue", or mentions using the jira command-line tool for project management.
13backstage custom resource
This skill should be used when the user asks to "create Backstage CR", "create RHDH custom resource", "configure rhdh-operator", "create Backstage manifest", "modify Backstage CR", "configure RHDH deployment", "add dynamic plugins to CR", "configure Backstage database", "set up Backstage route", "configure app-config for RHDH", "create rhdh.redhat.com/v1alpha Backstage", or mentions creating or modifying a Backstage Custom Resource for the rhdh-operator.
10worktree feature development
This skill should be used when the user asks to "start a new feature", "create feature branch in worktree", "set up isolated feature development", "work on feature in separate directory", or mentions git worktree for feature isolation.
10generate frontend wiring
This skill should be used when the user asks to "generate frontend wiring", "show frontend wiring", "create RHDH binding", "generate dynamic plugin config", "show plugin wiring for RHDH", "create app-config for frontend plugin", or wants to generate the RHDH dynamic plugin wiring configuration for an existing Backstage frontend plugin. The skill analyzes the plugin's source code and generates the appropriate configuration.
9rhdh frontend dynamic plugin bootstrap
This skill should be used when the user asks to "create RHDH frontend plugin", "bootstrap frontend dynamic plugin", "create UI plugin for RHDH", "new frontend plugin for Red Hat Developer Hub", "add entity card to RHDH", "create dynamic route", "add sidebar menu item", "configure mount points", "create theme plugin", or mentions creating frontend components, UI pages, entity cards, or visual customizations for Red Hat Developer Hub or RHDH. This skill is specifically for frontend plugins - for backend plugins, use the separate backend plugin skill.
9rhdh backend dynamic plugin bootstrap
This skill should be used when the user asks to "create RHDH backend plugin", "bootstrap backend dynamic plugin", "create backstage backend plugin for RHDH", "new backend plugin for Red Hat Developer Hub", "create dynamic backend plugin", "scaffold RHDH backend plugin", "new scaffolder action", "create catalog processor", or mentions creating a new backend plugin, backend module, or server-side functionality for Red Hat Developer Hub or RHDH. This skill is specifically for backend plugins - for frontend plugins, use the separate frontend plugin skill.
9