Clickhouse Logs Queries
supabase/supabase
Write, review, and migrate Supabase logs queries against the ClickHouse-backed logs table (the logs.all.otel analytics endpoint).
Expert knowledge for developing the SRTD codebase itself. An agent skill from t1mmen/srtd.
$ npx skills add t1mmen/srtd --skill srtd-dev -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install t1mmen/srtd srtd-dev --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/t1mmen/srtd.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/srtd-dev .claude/skills/srtd-dev && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "srtd-dev" agent skill from https://github.com/t1mmen/srtd/tree/main/.claude/skills/srtd-dev into .claude/skills/srtd-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "srtd-dev", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/t1mmen/srtd/tree/main/.claude/skills/srtd-devType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add t1mmen/srtd --skill srtd-dev -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install t1mmen/srtd srtd-dev --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/t1mmen/srtd.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/srtd-dev .agents/skills/srtd-dev && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "srtd-dev" agent skill from https://github.com/t1mmen/srtd/tree/main/.claude/skills/srtd-dev into .agents/skills/srtd-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "srtd-dev", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add t1mmen/srtd --skill srtd-dev -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install t1mmen/srtd srtd-dev --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/t1mmen/srtd.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/srtd-dev .cursor/skills/srtd-dev && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "srtd-dev" agent skill from https://github.com/t1mmen/srtd/tree/main/.claude/skills/srtd-dev into .cursor/skills/srtd-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "srtd-dev", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/t1mmen/srtd.git --path .claude/skills/srtd-dev--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add t1mmen/srtd --skill srtd-dev -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install t1mmen/srtd srtd-dev --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/t1mmen/srtd.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/srtd-dev .gemini/skills/srtd-dev && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "srtd-dev" agent skill from https://github.com/t1mmen/srtd/tree/main/.claude/skills/srtd-dev into .gemini/skills/srtd-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "srtd-dev", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install t1mmen/srtd srtd-devInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add t1mmen/srtd --skill srtd-dev -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/t1mmen/srtd.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/srtd-dev .github/skills/srtd-dev && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "srtd-dev" agent skill from https://github.com/t1mmen/srtd/tree/main/.claude/skills/srtd-dev into .github/skills/srtd-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "srtd-dev", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add t1mmen/srtd --skill srtd-dev -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install t1mmen/srtd srtd-dev --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/t1mmen/srtd.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/srtd-dev .opencode/skills/srtd-dev && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "srtd-dev" agent skill from https://github.com/t1mmen/srtd/tree/main/.claude/skills/srtd-dev into .opencode/skills/srtd-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "srtd-dev", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
srtd-devExpert knowledge for developing the SRTD codebase itself. An agent skill from t1mmen/srtd.
Srtd Dev is an agent skill from t1mmen/srtd. Expert knowledge for developing the SRTD codebase itself. Use when implementing features, fixing bugs, understanding architecture, or writing tests for SRTD internals. NOT for end users of srtd CLI.
Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Databases. It works with Supabase, SQL and PostgreSQL. The repository describes itself as: 🪄 Supabase migrations made magical: Live-reloading SQL + Sane, reviewable diffs + Maintainable templates = Delightful DX. The licence is MIT.
5 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 271b138. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
npmnpxFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use npm and npx, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Srtd Dev loads about 2.3k tokens when it runs. Until then it costs about 52 tokens; SKILL.md has 419 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from t1mmen/srtd at commit 271b138, republished under its MIT licence (© t1mmen). 419 words, ~2,296 tokens.
.claude/skills/srtd-dev/SKILL.md (or your agent's skills folder).Expert guidance for working with the SRTD codebase - a CLI tool for live-reloading SQL templates into Supabase local databases.
npm test # Run all tests
npx vitest run -t "pattern" # Run specific test
npm run typecheck # Type check
npm run lint # Biome lint + fix
npm start -- watch # Run watch command
npm run supabase:start # Start test database| Task | Primary Files |
|---|---|
| Add CLI option | src/commands/{command}.ts, src/cli.ts |
| Modify template processing | src/services/Orchestrator.ts |
| Change state tracking | src/services/StateService.ts |
| Fix database issues | src/services/DatabaseService.ts |
| Modify migration output | src/services/MigrationBuilder.ts |
| Change file watching | src/services/FileSystemService.ts |
| Update config | src/utils/config.ts, src/types.ts |
Unidirectional flow - data flows one direction through the system:
File Change → FileSystemService → Orchestrator → StateService
↓
DatabaseService / MigrationBuilder
↓
StateService (update) → Event EmissionFileSystemService owns:
StateService owns:
.buildlog.json, .buildlog.local.json)DatabaseService owns:
MigrationBuilder owns:
Orchestrator owns:
.buildlog.json (what was built, commit) + .buildlog.local.json (what was applied, gitignore)currentHash !== lastAppliedHash && currentHash !== lastBuiltHashawait using for automatic cleanup// Check 1: Is template being found?
// FileSystemService.findTemplates() uses glob pattern from config.filter
// Check 2: Is hash comparison returning false?
// StateService.hasTemplateChanged() compares against BOTH build logs
// Check 3: Is it a WIP template?
// isWipTemplate() checks for config.wipIndicator suffix (.wip.sql)
// Debugging: Add to Orchestrator.processTemplate():
console.log({
path,
hash: currentHash,
state: this.stateService.getTemplateStatus(path)
});// DatabaseService categorizes errors via DatabaseErrorType:
// - CONNECTION_ERROR: ECONNREFUSED, ENOTFOUND, ECONNRESET
// - POOL_EXHAUSTED: "pool is exhausted", "too many clients"
// - TIMEOUT_ERROR: ETIMEOUT or timeout in message
// Check pool status:
console.log({
total: pool.totalCount,
idle: pool.idleCount,
waiting: pool.waitingCount
});// Valid transitions in StateService:
// UNSEEN → CHANGED
// CHANGED → APPLIED, BUILT, ERROR
// APPLIED → CHANGED, SYNCED
// BUILT → CHANGED, SYNCED
// SYNCED → CHANGED
// ERROR → CHANGED
// Check current state:
const info = stateService.templateStates.get(absolutePath);
console.log({ state: info?.state, lastAppliedHash, lastBuiltHash });import { setupCommandTestSpies, createMockUiModule } from '../helpers/testUtils.js';
beforeEach(() => {
vi.clearAllMocks();
vi.resetModules(); // Critical: reload modules
spies = setupCommandTestSpies();
});
afterEach(() => spies.cleanup());
it('handles success', async () => {
const { buildCommand } = await import('../commands/build.js');
mockOrchestrator.build.mockResolvedValue({ built: ['file.sql'], errors: [] });
await buildCommand.parseAsync(['node', 'test']);
spies.assertNoStderr(); // Catch Commander parse errors
expect(spies.exitSpy).toHaveBeenCalledWith(0);
});import { createTestResource } from '../helpers/index.js';
it('applies template to database', async () => {
using resources = await createTestResource({ prefix: 'apply' });
await resources.setup();
// Create template with unique function name
const templatePath = await resources.createTemplateWithFunc('test', '_v1');
// Execute within transaction for isolation
const result = await resources.withTransaction(async (client) => {
// ... test logic
return client.query('SELECT ...');
});
// Verify function exists
expect(await resources.verifyFunctionExists()).toBe(true);
// Auto-cleanup via Symbol.asyncDispose
});// Mock Orchestrator (most common)
vi.mock('../services/Orchestrator.js', () => ({
Orchestrator: {
create: vi.fn().mockResolvedValue({
apply: vi.fn().mockResolvedValue({ applied: [], errors: [], skipped: [] }),
build: vi.fn().mockResolvedValue({ built: [], errors: [], skipped: [] }),
watch: vi.fn().mockResolvedValue(undefined),
[Symbol.asyncDispose]: vi.fn(),
}),
},
}));
// Mock config
vi.mock('../utils/config.js', () => ({
getConfig: vi.fn().mockResolvedValue({
templateDir: '/tmp/templates',
migrationDir: '/tmp/migrations',
// ... other config
}),
}));src/commands/{command}.ts:.option('-x, --example', 'Description')const result = await orchestrator.apply({ force, example: options.example });async apply(options: ApplyOptions & { example?: boolean }) {
if (options.example) { /* ... */ }
}it('respects --example flag', async () => {
await command.parseAsync(['node', 'test', '--example']);
expect(mockOrchestrator.apply).toHaveBeenCalledWith(
expect.objectContaining({ example: true })
);
});src/types.tstype OrchestratorEvents = {
newEvent: [payload: NewEventPayload];
// ... existing events
};this.emit('newEvent', payload);orchestrator.on('newEvent', (payload) => {
// Update UI
});// Categorize and wrap errors
try {
await pool.query(sql);
} catch (error) {
const dbError = this.categorizeError(error);
this.emit('sql:error', { error: dbError });
throw dbError;
}try {
const result = await orchestrator.apply();
process.exit(result.errors.length > 0 ? 1 : 0);
} catch (error) {
console.log(chalk.red(getErrorMessage(error)));
process.exit(1);
}try {
const answer = await select({ /* ... */ });
} catch (error) {
if (isPromptExit(error)) {
process.exit(0); // Ctrl+C is clean exit
}
throw error;
}using pattern or explicit disposenpm run typecheck && npm run lint && npm testAll three must pass. CI runs on Node 20.x and 22.x with PostgreSQL 15.
© t1mmen, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .claude/skills/srtd-dev of t1mmen/srtd.
Open the folder on GitHubat commit 271b138
Srtd Dev next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Srtd Dev this skillt1mmen/srtd | 105 | — | ~2.3k | Automated safety check: Pass | MIT | |
| Clickhouse Logs Queriessupabase/supabase | 111k | — | ~2.4k | Automated safety check: Pass | Apache-2.0 | |
| Safe SQL Executionsupabase/supabase | 111k | — | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Take Doc Screenshotspgplex/pgconsole | 155 | — | ~841 | Automated safety check: Pass | Apache-2.0 | |
| Expert DatabaseReJeCtAll/ExpertTeam-Codex | 113 | — | ~692 | Automated safety check: Pass | MIT | |
| DB Migratealexeykrol/claude-code-starter | 194 | — | ~405 | Automated safety check: Notes | None |
supabase/supabase
Write, review, and migrate Supabase logs queries against the ClickHouse-backed logs table (the logs.all.otel analytics endpoint).
supabase/supabase
A skill your agent uses whenever code will build, return, fetch, or execute SQL that runs against a user's real Postgres database — even when the request reads like an ordinary feature or bug fix…
pgplex/pgconsole
Take screenshots of the running pgconsole app for documentation.
ReJeCtAll/ExpertTeam-Codex
数据库优化专家入口。用于 Codex CLI 的 $expert-database 调用. An agent skill from ReJeCtAll/ExpertTeam-Codex.
alexeykrol/claude-code-starter
Миграция схемы базы данных: SQLite → PostgreSQL/Supabase. An agent skill from alexeykrol/claude-code-starter.
anolilab/lunora
Connects an existing, externally owned Postgres/MySQL database to a Lunora app through Cloudflare Hyperdrive.
t1mmen/srtd
This skill should be used when the user mentions "srtd", "sql templates", "migrations-templates", "live reload sql", "supabase functions", when working with files in supabase/migrations-templates/…
t1mmen/srtd
Structured code review workflow for SRTD development. An agent skill from t1mmen/srtd.
Works with
Categories
Expert knowledge for developing the SRTD codebase itself. An agent skill from t1mmen/srtd. Srtd Dev is an agent skill from t1mmen/srtd. Expert knowledge for developing the SRTD codebase itself.
Srtd Dev fits situations like: implementing features; understanding architecture; writing tests for SRTD internals.
Run `npx skills add t1mmen/srtd --skill srtd-dev -a claude-code`. Or copy the skill folder (.claude/skills/srtd-dev in t1mmen/srtd) into .claude/skills/srtd-dev in your project. Claude Code loads it when a task matches its description.
Run `npx skills add t1mmen/srtd --skill srtd-dev -a codex`. Or copy the skill folder (.claude/skills/srtd-dev in t1mmen/srtd) into .agents/skills/srtd-dev in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add t1mmen/srtd --skill srtd-dev -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/srtd-dev, .gemini/skills/srtd-dev, .github/skills/srtd-dev and .opencode/skills/srtd-dev in your project.
Going by SKILL.md and its folder, Srtd Dev needs the command-line tools its instructions call (npm and npx). Our summary lists: Node.js.
SKILL.md contains no URLs. Its commands use npm and npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Srtd Dev is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.3k tokens (SKILL.md is roughly 9.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Srtd Dev: Clickhouse Logs Queries (supabase/supabase, 111k stars), Safe SQL Execution (supabase/supabase, 111k stars), Take Doc Screenshots (pgplex/pgconsole, 155 stars) and Expert Database (ReJeCtAll/ExpertTeam-Codex, 113 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
t1mmen (a GitHub user) maintains it in t1mmen/srtd, which has 105 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on September 5, 2026.
Source: t1mmen/srtd on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.