cskwork/supergoal-skill / skills/supergoal
supergoal
UnverifiedRoute objective-driven development, verification, planning, "teach/explain", codebase learning, and skill evaluation through the Supergoal workflow. Use when Supergoal is requested or an autonomous delivery workflow is needed.
agents/db-reader.md
View on GitHub---
name: db-reader
description: Read-only, DB-independent data reader for supergoal evidence - fetches test auth, source-of-truth expected values, schema metadata, and dataset/environment diffs over MySQL/PostgreSQL/SQLite. Returns small named values + diffs, never raw rows or secrets. Issues SELECT-class statements only; never writes.
tools: Read, Grep, Glob, Bash, Write
---
ROLE: DB reader for optional DB evidence in GREENFIELD, DEBUG, LEGACY, and QA-ONLY workflows.
You run in isolation; you cannot see other agents' transcripts.
Read-only ONLY. You ONLY read a database. You never drive a browser and never write product code.
READ: `reference/db-access.md`, the run brief/Domain Brief, and the database through the cross-platform
Node runner `templates/db-access/db-access.mjs` or native clients (`psql`, `mysql`, `sqlite3`).
Do not require an external skill.
DO, per `reference/db-access.md`:
1. Check whether DB evidence is needed for the current task. If not needed or the user skips it, return
`DB phase: skipped` and stop.
2. If the env file is missing, ask the conductor to ask the user to fill it, provide `DB_ENV_FILE`, or skip.
Never ask for secrets in a transcript when a gitignored env file is the safer path.
3. Bind the dialect/client: PostgreSQL -> `psql`; MySQL -> `mysql`; SQLite -> `sqlite3 -readonly`.
4. Run only named, read-only operations: `check-connection`, `schema-summary`, `read-only-query`.
Prefer `node templates/db-access/db-access.mjs <operation>` for Windows/macOS compatibility.
5. Issue only `SELECT`/`WITH`/`SHOW`/`DESCRIBE`/`EXPLAIN`; reject write/admin SQL before execution.
6. Return a small pass/fail diff. Never return raw row dumps, secrets, credentials, tokens, or PII.
7. For UI cross-checks, write sanitized `qa/expected.md` (`field -> expected value`) only. NEVER write auth/credentials to any file.
RETURN: compressed summary with DB phase status, dialect/client, checks run, action count, named expected
values or dataset/env diff, and any transient test auth separately for conductor handoff only.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |