tbls
tbls is a CI-Friendly tool to document a database, written in Go.
Runs with mockssource: GitHubGoMITcommit 188868990583
Go, MIT licensed. The project labels itself: bigquery, continuous integration, database document, database schema, documentation tool, dynamodb, er diagram and excel.
tbls runs, with stand-ins for the services it depends on. An Argusic agent installed it in 44 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The tbls Go project builds and runs: the binary outputs version 1.96.0, documents a SQLite database producing markdown docs, SVG ER diagrams, and JSON/YAML/Mermaid schema exports, and all non-DB-dependent test packages pass.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 92 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Go 1.27.1 compiler not found in container8 minutes
- First build without -tags sqlite_fts5 hit 'no such module: fts5'8 minutes
- Datasource test requires MySQL/Postgres/MSSQL servers (connection refused)
- sqlite3 CLI binary not installed
- Install time
- 44 minutes
- Cold machine to finish
- 44 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- go test ./cmd/... ./cmdutil/... ./config/... ./coverage/... ./ddl/... ./dict/... ./output/... ./schema/... -tags sqlite_fts5 exited 0 (all passed); tbls doc sq://... generated 17 table docs + SVG diagrams + schema.json; tbls out -t mermaid produced ER diagram; tbls out -t json/yaml returned valid structured output; tbls diff produced no output (matching); tbls help listed all commands; tbls version returned 1.96.0
- Model tokens used
- 165,373
- Exact commit tested
- 188868990583
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
succeeded in 112ms: Let me calculate the total elapsed exec /bin/sh -lc 'echo "Started at: 10:18 UTC"; echo "Current time:"; date -u "+%H:%M UTC"' in /work/repo succeeded in 0ms: Started at: 10:18 UTC Current time: 11:02 UTC Now I have all the data. Let me produce the final report. tokens used 165,373 Now I have all the data. Let me produce the final report.
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Installed in 44 minutes.
- Recovered from all 4 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.15 |
Topics (from GitHub)
bigquerycontinuous-integrationdatabase-documentdatabase-schemadocumentation-tooldynamodber-diagramexcelhacktoberfestmariadbmarkdownmermaidmysqlplantumlpostgresqlredshiftsnowflakespannersqlitesqlserver
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/tbls)Questions
- Does tbls run?
- tbls runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 44 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test tbls?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 188868990583. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test tbls?
- The run that produced this verdict cost $0.15: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does tbls take to install?
- 44 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does tbls need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing tbls?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for tbls?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.