Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

Comenzar

db-browser

Estrellas353

Forks72

Actualizado3 de julio de 2026 a las 02:18

Install DB Browser for SQLite (if not already installed) and open a .sqlite file in it. macOS only.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

sonichi

sonichi/sutando

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·SOC 15-1252

Explorador de archivos

2 archivos

SKILL.md

readonly

name	db-browser
description	Install DB Browser for SQLite (if not already installed) and open a .sqlite file in it. macOS only.
user-invocable	true

DB Browser

Install DB Browser for SQLite via Homebrew if it isn't already installed, then open a given .sqlite file in it. Macos only — uses brew --cask + open -a.

Usage: /db-browser <path-to.sqlite>

ARGUMENTS: $ARGUMENTS

Steps

Resolve the path argument. If empty, default to $(bash scripts/sutando-config.sh workspace)/data/conversation.sqlite (the M0 helper — reads sutando.config.local.json, defaulting to <repo>/workspace/data/conversation.sqlite; $SUTANDO_WORKSPACE no longer honored as of v0.8 / #1440). Bail with an error if the file doesn't exist.
Check whether DB Browser for SQLite is installed: mdfind "kMDItemKind == 'Application'" 2>/dev/null | grep -qi 'DB Browser for SQLite' (or [ -d /Applications/DB\ Browser\ for\ SQLite.app ]). If installed, skip step 3.
Install via Homebrew: brew install --cask db-browser-for-sqlite. Requires brew. If brew is missing, stop and ask the user to install brew first.
If DB Browser is already running on a DIFFERENT db file (its cached snapshot of THAT db won't auto-refresh when you switch files), quit it first: osascript -e 'tell application "DB Browser for SQLite" to quit'; sleep 2. Skip if not running.
Open the file: open -a "DB Browser for SQLite" "<resolved-path>". Sleep ~2s so the window is up before reporting back.
Confirm: print the resolved path + verify DB Browser has the file open via lsof -c "DB Browser" 2>/dev/null | grep "<resolved-path>".

Notes

DB Browser caches the schema + first page of data at open time. If the on-disk db file changes underneath (e.g. a migration drops tables, a writer adds rows), the open DB Browser window keeps showing the stale view until you re-open it. That's why step 4 quits first when re-opening — same-file re-open is also a valid refresh trigger.
WAL flush: if the db is in WAL mode and recent writes haven't merged into the main file, the .sqlite-wal sidecar holds them. DB Browser reads both — no checkpoint needed. (Run sqlite3 <db> 'PRAGMA wal_checkpoint(TRUNCATE);' only if you want a single-file dump.)
This skill does NOT screenshot, query, or modify the db. Just install + open. Anything else (screenshot for a PR, run a SQL via Execute SQL, export CSV) is the operator's job in the GUI.

Más de este repositorio

mismo repositorio

morning-briefing

sonichi/sutando

Generate a daily morning briefing: email, calendar, Discord, and news — delivered via voice or Discord DM.

2026-07-14353

phone-conversation

sonichi/sutando

Make conversational phone calls and join Zoom meetings via Twilio + Gemini. Multi-turn AI conversations on the phone on behalf of the user.

2026-07-13353

self-diagnose

sonichi/sutando

Sutando introspection — read logs + git + memory + build log for a chosen time window and produce a concise narrative of what the agent has been doing, what's broken, and what to prioritize next.

2026-07-13353

report-feedback

sonichi/sutando

File a bug report, feature request, or feedback about Sutando to the team from any surface (chat, Discord, Telegram, or a voice-delegated task). Reuses the cloud /api/feedback API and auto-attaches diagnostic context. Use when the user says "report a bug", "something's broken, file it", "I have a feature request", etc.

2026-07-09353

quota-tracker

sonichi/sutando

Track Claude Code quota usage via Anthropic API rate limit headers. Shows 5h and 7d utilization, reset times, and quota status. Works with both subscription and API key auth.

2026-07-09353

zoom

sonichi/sutando

Zoom meeting control for Sutando's voice and phone agents — contributes the summon (join + screen share), dismiss (leave meeting), and join_zoom (join with computer audio, no share) inline tools.

2026-07-08353

DB Browser

Install DB Browser for SQLite via Homebrew if it isn't already installed, then open a given .sqlite file in it. Macos only — uses brew --cask + open -a.

Usage: /db-browser <path-to.sqlite>

ARGUMENTS: $ARGUMENTS

Steps

Resolve the path argument. If empty, default to $(bash scripts/sutando-config.sh workspace)/data/conversation.sqlite (the M0 helper — reads sutando.config.local.json, defaulting to <repo>/workspace/data/conversation.sqlite; $SUTANDO_WORKSPACE no longer honored as of v0.8 / #1440). Bail with an error if the file doesn't exist.

Check whether DB Browser for SQLite is installed: mdfind "kMDItemKind == 'Application'" 2>/dev/null | grep -qi 'DB Browser for SQLite' (or [ -d /Applications/DB\ Browser\ for\ SQLite.app ]). If installed, skip step 3.

Install via Homebrew: brew install --cask db-browser-for-sqlite. Requires brew. If brew is missing, stop and ask the user to install brew first.

If DB Browser is already running on a DIFFERENT db file (its cached snapshot of THAT db won't auto-refresh when you switch files), quit it first: osascript -e 'tell application "DB Browser for SQLite" to quit'; sleep 2. Skip if not running.

Open the file: open -a "DB Browser for SQLite" "<resolved-path>". Sleep ~2s so the window is up before reporting back.

Confirm: print the resolved path + verify DB Browser has the file open via lsof -c "DB Browser" 2>/dev/null | grep "<resolved-path>".

Notes

DB Browser caches the schema + first page of data at open time. If the on-disk db file changes underneath (e.g. a migration drops tables, a writer adds rows), the open DB Browser window keeps showing the stale view until you re-open it. That's why step 4 quits first when re-opening — same-file re-open is also a valid refresh trigger.

WAL flush: if the db is in WAL mode and recent writes haven't merged into the main file, the .sqlite-wal sidecar holds them. DB Browser reads both — no checkpoint needed. (Run sqlite3 <db> 'PRAGMA wal_checkpoint(TRUNCATE);' only if you want a single-file dump.)

This skill does NOT screenshot, query, or modify the db. Just install + open. Anything else (screenshot for a PR, run a SQL via Execute SQL, export CSV) is the operator's job in the GUI.