Menu
Open the journal SQLite database in a GUI viewer (DB Browser for SQLite, or similar).
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ê.
Baseado na classificação ocupacional SOC
Show usage information for any workflow-toolkit skill. Use when the user asks how to use a specific skill, what a skill does, or needs guidance on workflow-toolkit features. Also triggers on "help", "how do I", "what does X do", or "usage" in the context of workflow-toolkit skills.
Initialize and verify the workflow-toolkit environment. Checks SQLite availability, creates the journal database, verifies directory structure, checks gh CLI auth, and reports readiness. Run this after installing the plugin or when troubleshooting.
Pre-flight checklist for open source contributions. Validates code changes against project rules, PR size limits, commit format, linting, and type-checking. Does NOT push or create PRs — only reports issues.
Creates a new Claude Code custom subagent configuration. Guides you through designing agent scope, tools, permissions, hooks, and system prompts.
Creates a new Claude Code custom skill (slash command). Guides you through designing, writing, and placing the SKILL.md file with proper frontmatter, arguments, and best practices.
Distills a codebase concept into a structured knowledge base entry. Analyzes patterns, conventions, and real examples from the code to create reference documentation. Use when you need to understand how something works in this project (e.g., React hooks, API routers, database models, testing patterns).
| name | db-viewer |
| description | Open the journal SQLite database in a GUI viewer (DB Browser for SQLite, or similar). |
| disable-model-invocation | true |
Opens the journal database ($CLAUDE_PROJECT_DIR/.claude/journal/journal.db) in a SQLite GUI viewer.
/workflow-toolkit:db-viewer # Open the journal database
/workflow-toolkit:db-viewer <path> # Open a specific SQLite database file
Determine which database to open:
<path> argument, use that path$CLAUDE_PROJECT_DIR/.claude/journal/journal.dbVerify the database file exists using the Read tool (just check existence, don't read content)
Attempt to launch a SQLite GUI viewer. Try these in order:
# Windows (DB Browser for SQLite via scoop)
start "" "$(which sqlitebrowser 2>/dev/null || echo 'sqlitebrowser')" "<db-path>" &
# macOS
open -a "DB Browser for SQLite" "<db-path>" 2>/dev/null
# Linux
sqlitebrowser "<db-path>" &
If no GUI viewer is found, fall back to showing the database summary via CLI:
sqlite3 "<db-path>" ".tables"
sqlite3 "<db-path>" "SELECT COUNT(*) || ' entries, ' || (SELECT COUNT(*) FROM sessions) || ' sessions, ' || (SELECT COUNT(*) FROM tasks) || ' tasks' FROM entries;"
Confirm to the user what was opened.
entries, sessions, compaction_snapshots, tool_usage, github_issues, tasks