Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

Começar

jb-tuna-script

Estrelas0

Forks0

Atualizado2 de junho de 2026 às 20:30

Use when adding, writing, fixing, or exposing a script for the Tuna macOS launcher.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

bjesuiter

bjesuiter/skills

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

name	jb-tuna-script
description	Use when adding, writing, fixing, or exposing a script for the Tuna macOS launcher.

JB Tuna Script

Use this skill when creating small scripts that should appear in Tuna.

Key facts

Tuna scans executable scripts in ~/Library/Scripts even in free mode.
Custom script directories may be disabled unless Tuna Pro is active.
Prefer creating the script directly in ~/Library/Scripts/<command-name>.
Do not research Tuna script locations again unless this path fails.

Minimal script template

#!/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

Workflow

Choose a concise filename and Tuna name, usually the command name the user asked for.
Write the script at ~/Library/Scripts/<name>.
Include Tuna metadata comments only as needed:
- @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.
Make it executable: chmod +x ~/Library/Scripts/<name>.
Verify by running ~/Library/Scripts/<name> directly.

Example: PinchTab dashboard

#!/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.

Guardrails

Keep wrappers minimal; avoid inspecting unrelated existing scripts unless the requested behavior is complex.
Use absolute/user-specific PATH entries when needed for Homebrew-installed CLIs.
Prefer exec <command> so the script exits with the wrapped command's status.

Mais deste repositório

mesmo repositório

jb-dev-env

bjesuiter/skills

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.

2026-06-290

jb-beans

bjesuiter/skills

Use when the repo has .beans or the user mentions beans, beans-prime, flat-file issues, task tracking, or issue status changes.

2026-06-230

jb-gh-release-with-attempts

bjesuiter/skills

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.

2026-06-200

jb-local-release

bjesuiter/skills

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.

2026-06-200

jb-mdn

bjesuiter/skills

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.

2026-06-160

jb-chrome-mcp

bjesuiter/skills

Use when the user asks for Chrome MCP/DevTools MCP via mcporter, existing Chrome tabs, console/network inspection, screenshots, or performance traces.

2026-06-110

JB Tuna Script

Use this skill when creating small scripts that should appear in Tuna.

Key facts

Tuna scans executable scripts in ~/Library/Scripts even in free mode.

Custom script directories may be disabled unless Tuna Pro is active.

Prefer creating the script directly in ~/Library/Scripts/<command-name>.

Do not research Tuna script locations again unless this path fails.

Minimal script template

#!/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

Workflow

Choose a concise filename and Tuna name, usually the command name the user asked for.

Write the script at ~/Library/Scripts/<name>.

Include Tuna metadata comments only as needed:

@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.

Make it executable: chmod +x ~/Library/Scripts/<name>.

Verify by running ~/Library/Scripts/<name> directly.

Example: PinchTab dashboard

#!/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.

Guardrails

Keep wrappers minimal; avoid inspecting unrelated existing scripts unless the requested behavior is complex.

Use absolute/user-specific PATH entries when needed for Homebrew-installed CLIs.

Prefer exec <command> so the script exits with the wrapped command's status.