Menu
Use when adding, writing, fixing, or exposing a script for the Tuna macOS launcher.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | jb-tuna-script |
| description | Use when adding, writing, fixing, or exposing a script for the Tuna macOS launcher. |
Use this skill when creating small scripts that should appear in Tuna.
~/Library/Scripts even in free mode.~/Library/Scripts/<command-name>.#!/usr/bin/env bash
# @tuna.name command-name
# @tuna.subtitle Short human-readable description
# @tuna.icon symbol:terminal
# @tuna.mode background
# @tuna.input none
# @tuna.output text
set -euo pipefail
export PATH="$HOME/.homebrew/bin:/opt/homebrew/bin:/usr/local/bin:/usr/bin:/bin:$PATH"
exec command arg1 arg2
~/Library/Scripts/<name>.@tuna.name for display/search name.@tuna.subtitle for a short explanation.@tuna.icon optional; use an SF Symbol when obvious.@tuna.mode background for wrappers that should just run.@tuna.input none for no-argument scripts.@tuna.output text when command output is useful.chmod +x ~/Library/Scripts/<name>.~/Library/Scripts/<name> directly.#!/usr/bin/env bash
# @tuna.name pinchtab
# @tuna.subtitle Open the PinchTab dashboard
# @tuna.icon symbol:rectangle.connected.to.line.below
# @tuna.mode background
# @tuna.input none
# @tuna.output text
set -euo pipefail
export PATH="$HOME/.homebrew/bin:/opt/homebrew/bin:/usr/local/bin:/usr/bin:/bin:$PATH"
exec pinchtab dashboard
Expected path:
~/Library/Scripts/pinchtab
Expected verification output:
Dashboard: http://127.0.0.1:9867
Token copied to clipboard — paste it on the login page.
Opened in your browser.
exec <command> so the script exits with the wrapped command's status.Use when setting up or reviewing a development environment, especially Varlock env schemas, gitignored env files, macOS Keychain/local secret storage, SOPS/age optional GitOps secrets, CI secret access, dotenv bootstrapping, or secure local dev onboarding.
Use when the repo has .beans or the user mentions beans, beans-prime, flat-file issues, task tracking, or issue status changes.
Opinionated JB GitHub Actions release-attempt workflow. Use only when the repo already has .github/workflows/jb-release-v1.yaml (or equivalent JB release-attempt workflow) or the user explicitly asks to set it up. Do not use for ordinary local releases; use jb-local-release instead.
Use when the user asks to run a local release flow: prepare version/changelog changes, run local checks, commit, tag, and optionally publish only when explicitly requested.
Query MDN Web Docs through the official MDN MCP server using a persistent mcporter config, avoiding a direct MCP connection in the agent harness. Use when checking current web platform docs, CSS/HTML/JavaScript/Web API behavior, MDN browser compatibility data, Baseline support, or when the user asks whether a browser feature is supported.
Use when the user asks for Chrome MCP/DevTools MCP via mcporter, existing Chrome tabs, console/network inspection, screenshots, or performance traces.