Automated summary
This skill helps create, modify, and manage shizuku app configurations, including scaffolding, adding template files, and implementing install logic.
Strengths
- Fully automates scaffolding of shizuku apps with an interface-based architecture.
- Built-in support for Homebrew installation (formulae, casks, taps).
- Handles Go template files (.tmpl) and template variables.
- Covers optional capabilities like file syncing and environment variables.
Limitations
- Limited to shizuku apps and their ecosystem.
- Does not handle non-Homebrew dependency management.
- Complex .tmpl file creation requires knowledge of Go templates.
Use this skill when you need to create a new shizuku app, add template files to an existing app, or modify an app's structure.
Do not use this skill for apps outside the shizuku framework or when you need a package manager other than Homebrew.
Security analysis
SafeThe skill provides instructions for generating Go code and directory structures. It does not instruct the agent to execute arbitrary commands, download and run remote scripts, or exfiltrate data. The templates for Homebrew installation are code snippets, not direct command execution, and no destructive operations are described.
No concerns found
How this analysis is madeExamples
Create a new shizuku app called tmux. It should be enabled by default, installed via Homebrew formula 'tmux', sync config files to ~/.config/tmux/, and have no template variables or remote files.Add Install() method to the existing 'alacritty' app that installs the Homebrew cask 'alacritty'.Scaffold a new shizuku app called 'starship' that is enabled by default and provides an environment variable STARSHIP_CONFIG pointing to ~/.config/starship.toml.name: app description: Create, modify, and manage shizuku app configurations. Use when the user wants to create a new app, add template files to an app, or modify existing app structure.
Shizuku App Manager
This skill helps create and manage shizuku application configurations.
What This Skill Does
When invoked, this skill helps you:
- Scaffold new apps - Create complete directory structure and registration
- Add template files - Create and manage .tmpl files in app contents
- Modify existing apps - Update app configurations and template data
- Add installer logic - Implement Install() method for Homebrew packages
App Structure Overview
Each shizuku app follows this pattern:
apps/{appName}/
├── {appName}.go # App struct with methods
└── contents/ # Template files and assets (optional)
├── file.conf # Regular files (copied as-is)
└── file.tmpl # Go templates (processed)
Modern App Architecture
Apps use an interface-based design with optional capabilities:
Core Interface (Required)
All apps must implement the App interface:
Name() string- Returns the app nameEnabled(config *shizukuconfig.Config) bool- Checks if app is enabled
Optional Interfaces
Apps can optionally implement:
FileSyncer- For apps that sync configuration filesSync(outDir string, config *shizukuconfig.Config) error
Installer- For apps that need installationInstall(config *shizukuconfig.Config) error
EnvProvider- For apps that provide environment variables/aliasesEnv() (*shizukuapp.EnvSetup, error)
Creating a New App
Step 1: Gather Requirements
Ask the user:
- App name - What is the name of the application? (e.g., "tmux", "alacritty")
- Default enabled - Should this app be enabled by default? (most apps: true, optional services: false)
- Installation - Does the app need installation via Homebrew? (y/n)
- If yes: package name, cask vs formula, any taps needed?
- File syncing - Does the app need to sync configuration files? (y/n)
- If yes: destination path (e.g., "~/.config/tmux/")
- Template data - Does the app need any template variables? (y/n)
- Remote files - Does the app need to download any remote resources like plugins? (y/n)
- Environment - Does the app need environment variables or aliases? (y/n)
Step 2: Create Directory Structure
mkdir -p apps/{appName}
# Only create contents/ if the app will sync files
mkdir -p apps/{appName}/contents
Step 3: Create the Go File
Create apps/{appName}/{appName}.go with the appropriate template:
Minimal App (No File Syncing)
package {appName}
import (
"github.com/eleonorayaya/shizuku/internal/shizukuconfig"
)
type App struct{}
func New() *App {
return &App{}
}
func (a *App) Name() string {
return "{appName}"
}
func (a *App) Enabled(config *shizukuconfig.Config) bool {
return config.GetAppConfigBool(a.Name(), "enabled", {defaultEnabled})
}
App with Installation
package {appName}
import (
"fmt"
"github.com/eleonorayaya/shizuku/internal/shizukuconfig"
"github.com/eleonorayaya/shizuku/internal/util"
)
type App struct{}
func New() *App {
return &App{}
}
func (a *App) Name() string {
return "{appName}"
}
func (a *App) Enabled(config *shizukuconfig.Config) bool {
return config.GetAppConfigBool(a.Name(), "enabled", {defaultEnabled})
}
func (a *App) Install(config *shizukuconfig.Config) error {
// For Homebrew formula
if err := util.InstallBrewPackage("{packageName}"); err != nil {
return fmt.Errorf("failed to install {packageName}: %w", err)
}
// For Homebrew cask
// if err := util.InstallCask("{caskName}"); err != nil {
// return fmt.Errorf("failed to install {caskName}: %w", err)
// }
// For custom tap
// if err := util.AddTap("{tapName}"); err != nil {
// return fmt.Errorf("failed to add tap: %w", err)
// }
return nil
}
App with File Syncing
package {appName}
import (
"fmt"
"github.com/eleonorayaya/shizuku/internal/shizukuapp"
"github.com/eleonorayaya/shizuku/internal/shizukuconfig"
)
type App struct{}
func New() *App {
return &App{}
}
func (a *App) Name() string {
return "{appName}"
}
func (a *App) Enabled(config *shizukuconfig.Config) bool {
return config.GetAppConfigBool(a.Name(), "enabled", {defaultEnabled})
}
func (a *App) Sync(outDir string, config *shizukuconfig.Config) error {
data := map[string]any{}
fileMap, err := shizukuapp.GenerateAppFiles("{appName}", data, outDir)
if err != nil {
return fmt.Errorf("failed to generate app files: %w", err)
}
if err := shizukuapp.SyncAppFiles(fileMap, "{destinationPath}"); err != nil {
return fmt.Errorf("failed to sync app files: %w", err)
}
return nil
}
App with Remote Files
func (a *App) Sync(outDir string, config *shizukuconfig.Config) error {
data := map[string]any{}
fileMap, err := shizukuapp.GenerateAppFiles("{appName}", data, outDir)
if err != nil {
return fmt.Errorf("failed to generate app files: %w", err)
}
remoteFiles := map[string]string{
"plugins/file.wasm": "https://example.com/file.wasm",
}
pluginMap, err := internal.FetchRemoteAppFiles(outDir, "{appName}", remoteFiles)
if err != nil {
return fmt.Errorf("failed to fetch remote files: %w", err)
}
maps.Copy(fileMap, pluginMap)
if err := shizukuapp.SyncAppFiles(fileMap, "{destinationPath}"); err != nil {
return fmt.Errorf("failed to sync app files: %w", err)
}
return nil
}
Note: If using maps.Copy, add import: "maps"
App with Environment Variables
func (a *App) Env() (*shizukuapp.EnvSetup, error) {
return &shizukuapp.EnvSetup{
Variables: []shizukuapp.EnvVar{
{Key: "EDITOR", Value: "nvim"},
},
Aliases: []shizukuapp.Alias{
{Name: "vim", Command: "nvim"},
},
}, nil
}
Step 4: Register the App
- Open
apps/app.go - Add import:
"github.com/eleonorayaya/shizuku/apps/{appName}" - Add to the return slice in
GetApps():{appName}.New(),
IMPORTANT: Apps are registered in apps/app.go, NOT in cmd/sync/sync.go or cmd/install/install.go. Those commands automatically load all apps via apps.GetApps().
Step 5: Build and Test
task build
task run -- list # Verify app appears
task run -- install # Test installation (if implemented)
task run -- sync # Test file syncing (if implemented)
Configuration System
Checking if App is Enabled
All apps implement Enabled() which checks the config:
func (a *App) Enabled(config *shizukuconfig.Config) bool {
return config.GetAppConfigBool(a.Name(), "enabled", true) // default: true
}
- Most apps default to
true(core functionality) - Optional services default to
false(protonpass, protonvpn, sfsymbols)
User Config Example
Users can control apps in ~/.config/shizuku/shizuku.yml:
apps:
nvim:
enabled: false
terraform:
enabled: false
protonpass:
enabled: true
Using Other Config Values
Use config.GetAppConfigBool() for boolean values:
useNerdFont := config.GetAppConfigBool(a.Name(), "nerd_font", true)
Use config.GetAppConfig() for other types:
theme, ok := config.GetAppConfig(a.Name(), "theme")
if ok {
themeStr, ok := theme.(string)
if ok {
data["Theme"] = themeStr
}
}
Adding Template Files
When the user wants to add configuration files to an app:
- Ask for file path - Relative to contents/ directory (e.g., "config.conf")
- Ask if it's a template - Does it need variable substitution? (y/n)
- Create the file - If template, use
.tmplextension - Update template data - If template, add necessary variables to the
datamap in the Sync method
Template Example
If creating contents/config.conf.tmpl:
# {{ .AppName }} Configuration
theme = "{{ .Theme }}"
Update the Sync method:
data := map[string]any{
"AppName": "MyApp",
"Theme": "monade",
}
Modifying Existing Apps
When modifying an app:
- Read the current Go file to understand existing structure
- List contents/ to see existing files (if applicable)
- Make requested changes while preserving the app pattern
- Ensure all required interfaces are still implemented
Important Notes
- No comments - Don't add comments unless explicitly requested (per CLAUDE.md)
- Error wrapping - Always use
fmt.Errorf("context: %w", err)pattern - Template extension -
.tmplfiles are processed, extension is removed in output - File syncing -
SyncAppFileshandles directory creation and file copying - App struct - Always use
type App struct{}withNew() *Appconstructor - Interface implementation - Implement only the interfaces the app needs
- Registration - Apps are registered in
apps/app.go, not in command files
Installation Utilities
Available Homebrew utilities in internal/util/homebrew.go:
InstallBrewPackage(packageName string) error- Install formula (auto-checks if exists)InstallCask(caskName string) error- Install cask (auto-checks if exists)AddTap(tapName string) error- Add Homebrew tap (auto-checks if exists)BrewPackageExists(packageName string) (bool, error)- Check if package is installed
All utilities are idempotent - safe to call multiple times.
Workflow
- Use TodoWrite to track the scaffolding steps
- Ask clarifying questions using AskUserQuestion
- Create all necessary files
- Update
apps/app.goregistration - Suggest running
task buildandtask run -- listto verify
Examples
Simple App (Installation Only)
- App: rust
- Default enabled: true
- Installation:
InstallBrewPackage("rustup") - No file syncing
App with File Syncing
- App: nvim
- Default enabled: true
- Installation:
InstallBrewPackage("neovim") - Syncs to: ~/.config/nvim/
- Provides: Environment variables (EDITOR=nvim, alias vim=nvim)
Optional Service App
- App: protonpass
- Default enabled: false
- Installation:
InstallCask("proton-pass") - No file syncing
App with Templates
- App: sketchybar
- Default enabled: true
- Installation: Tap + formula
- Syncs to: ~/.config/sketchybar/
- Templates: Uses {{ .Theme }} and other variables
App with Remote Files
- App: zellij
- Default enabled: true
- Installation:
InstallBrewPackage("zellij") - Syncs to: ~/.config/zellij/
- Remote: Downloads zjstatus.wasm plugin from GitHub
App with Custom Installer
- App: kitty
- Default enabled: true
- Installation: Uses curl installation script (not Homebrew)
- Syncs to: ~/.config/kitty/
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/shizuku-app-manager-mm78nmel/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/shizuku-app-manager-mm78nmel' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/shizuku-app-manager-mm78nmel/download' --output '.skill-downloads/shizuku-app-manager-mm78nmel/SKILL.md.part' && mv '.skill-downloads/shizuku-app-manager-mm78nmel/SKILL.md.part' '.skill-downloads/shizuku-app-manager-mm78nmel/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/shizuku-app-manager-mm78nmel/SKILL.md' && test -s '.skill-downloads/shizuku-app-manager-mm78nmel/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/app' && cp -R '.skill-downloads/shizuku-app-manager-mm78nmel' '.claude/skills/app'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/shizuku-app-manager-mm78nmel'openskills read 'shizuku-app-manager-mm78nmel'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/shizuku-app-manager-mm78nmel/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.