Source profileQuality 78/100

sonichi/sutando/skills/db-browser/SKILL.md

db-browser

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

Source repository stars
359
Declared platforms
0
Static risk flags
1
Last source update
2026-07-28
Source checked
2026-07-28
DecisionCompatibilityInstallWorkflowPermissionsEvidenceSource

Decision brief

What it does—and where it fits

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.

Best for

    Not for

    • Tasks that require unconfirmed production actions or broad system permissions.
    • Environments where the pinned source and install steps cannot be inspected.

    Compatibility matrix

    Platform support, with evidence labels

    PlatformStatusEvidenceWhat to check
    CodexNot declaredNo explicit evidencePortability before use
    Claude CodeNot declaredNo explicit evidencePortability before use
    CursorNot declaredNo explicit evidencePortability before use
    Gemini CLINot declaredNo explicit evidencePortability before use
    Open the compatibility checker

    Installation

    Inspect first. Install second.

    The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

    Source-detected install commandSource
    npx skills add https://github.com/sonichi/sutando --skill "skills/db-browser"
    Safe inspection promptEditorial

    Inspect the Agent Skill "db-browser" from https://github.com/sonichi/sutando/blob/6a8f0fccd32e5aa620a3572c8885544f144bb6fe/skills/db-browser/SKILL.md at commit 6a8f0fccd32e5aa620a3572c8885544f144bb6fe. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

    Workflow

    What the source asks the agent to do

    1. 01

      Steps

      1. 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 /workspace/data/conversation.sqlite; $SUTANDOWORKSPACE no longer honored as of v0.8 / 1440). Ba…

      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 /workspace/data/conversation.sqlite; $…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.
    2. 02

      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 unti…

      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 unti…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 'PRAGMA walcheckpoint(TRUNCATE);' o…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.

    Permission review

    Static risk signals and limitations

    Reads files

    low · line 3

    The documentation asks the agent to read local files, directories, or repositories.

    Install [DB Browser for SQLite](https://sqlitebrowser.org/) via Homebrew if it isn't already installed, then open a given `.sqlite` file in it. Macos only — uses `brew --cask` + `open -a`.

    Reads files

    low · line 15

    The documentation asks the agent to read local files, directories, or repositories.

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

    Evidence record

    Why each signal appears

    EvidenceSourceComputedTestedEditorial
    SignalValueEvidence typeMeaning
    Quality score78/100ComputedDocumentation, specificity, maintenance, and trust rules
    Repository stars359SourceRepository attention, not individual Skill quality
    Compatibility0 platformsSourceDeclared in the catalog source record
    Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

    Pinned source

    Provenance and original SKILL.md

    Repository
    sonichi/sutando
    Skill path
    skills/db-browser/SKILL.md
    Commit
    6a8f0fccd32e5aa620a3572c8885544f144bb6fe
    License
    MIT
    Collected
    2026-07-28
    Default branch
    main
    View the original SKILL.md

    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

    1. 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.
    2. 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.
    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.
    4. 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.
    5. Open the file: open -a "DB Browser for SQLite" "<resolved-path>". Sleep ~2s so the window is up before reporting back.
    6. 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.