Tidewave Integration
oliver-kriska/claude-elixir-phoenix
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs.
Specialized skill for working in the fdb-relational-core SQL processing layer — parser, plan generator, and Cascades planner.
Install Relational Query Processor
$ npx skills add FoundationDB/fdb-record-layer --skill relational-query-processor -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install FoundationDB/fdb-record-layer relational-query-processor --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/FoundationDB/fdb-record-layer.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/relational-query-processor .claude/skills/relational-query-processor && 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 "relational-query-processor" agent skill from https://github.com/FoundationDB/fdb-record-layer/tree/main/.claude/skills/relational-query-processor into .claude/skills/relational-query-processor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "relational-query-processor", 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/FoundationDB/fdb-record-layer/tree/main/.claude/skills/relational-query-processorType 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 FoundationDB/fdb-record-layer --skill relational-query-processor -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install FoundationDB/fdb-record-layer relational-query-processor --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FoundationDB/fdb-record-layer.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/relational-query-processor .agents/skills/relational-query-processor && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "relational-query-processor" agent skill from https://github.com/FoundationDB/fdb-record-layer/tree/main/.claude/skills/relational-query-processor into .agents/skills/relational-query-processor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "relational-query-processor", 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 FoundationDB/fdb-record-layer --skill relational-query-processor -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install FoundationDB/fdb-record-layer relational-query-processor --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FoundationDB/fdb-record-layer.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/relational-query-processor .cursor/skills/relational-query-processor && 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 "relational-query-processor" agent skill from https://github.com/FoundationDB/fdb-record-layer/tree/main/.claude/skills/relational-query-processor into .cursor/skills/relational-query-processor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "relational-query-processor", 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/FoundationDB/fdb-record-layer.git --path .claude/skills/relational-query-processor--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 FoundationDB/fdb-record-layer --skill relational-query-processor -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install FoundationDB/fdb-record-layer relational-query-processor --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FoundationDB/fdb-record-layer.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/relational-query-processor .gemini/skills/relational-query-processor && 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 "relational-query-processor" agent skill from https://github.com/FoundationDB/fdb-record-layer/tree/main/.claude/skills/relational-query-processor into .gemini/skills/relational-query-processor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "relational-query-processor", 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 FoundationDB/fdb-record-layer relational-query-processorInstalls 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 FoundationDB/fdb-record-layer --skill relational-query-processor -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/FoundationDB/fdb-record-layer.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/relational-query-processor .github/skills/relational-query-processor && 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 "relational-query-processor" agent skill from https://github.com/FoundationDB/fdb-record-layer/tree/main/.claude/skills/relational-query-processor into .github/skills/relational-query-processor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "relational-query-processor", 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 FoundationDB/fdb-record-layer --skill relational-query-processor -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install FoundationDB/fdb-record-layer relational-query-processor --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FoundationDB/fdb-record-layer.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/relational-query-processor .opencode/skills/relational-query-processor && 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 "relational-query-processor" agent skill from https://github.com/FoundationDB/fdb-record-layer/tree/main/.claude/skills/relational-query-processor into .opencode/skills/relational-query-processor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "relational-query-processor", 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.
Facts
- Skill name
relational-query-processor- GitHub stars
- 675
- Token cost
- ~1k tokens
- SKILL.md length
- 397 words
- Files
- 1
- Skills in repo
- 10
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Specialized skill for working in the fdb-relational-core SQL processing layer — parser, plan generator, and Cascades planner.
- Works in 4 steps: Logical rules transform the logical plan… → Physical rules convert logical operators… → Match candidates (e.g.,… → …
- Debugging query plans
- SKILL.md covers Key entry points, SQL execution path (normal case), Reading EXPLAIN output and Writing a yaml test that…, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Relational Query Processor is an agent skill from FoundationDB/fdb-record-layer. Specialized skill for working in the fdb-relational-core SQL processing layer — parser, plan generator, and Cascades planner. Use when debugging query plans, writing planner rules, or understanding the SQL execution path. Some example usages: "Why is this query doing a full table scan?" "Explain this EXPLAIN output" "How do I write a new Cascades rule?" "Why is my query not using the index?"
Its SKILL.md is about 1k 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, covering SQL, Query optimization and Debugging. It works with SQL. The repository describes itself as: A relational database with SQL support built on FoundationDB. The licence is Apache-2.0.
When your agent uses it
- Debugging query plans
- Writing planner rules
- Understanding the SQL execution path
Example prompts
- “Why is this query doing a full table scan?”
- “Explain this EXPLAIN output”
- “How do I write a new Cascades rule?”
- “/relational-query-processor”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Logical rules transform the logical plan (e.g., push predicates into index scans).
- Physical rules convert logical operators to physical plans (e.g., select index vs. scan).
- Match candidates (e.g., PrimaryScanMatchCandidate, ValueIndexScanMatchCandidate)
- Simplification runs Derivations.simplifyLocalValues() — only on cold cache misses.
What it can do on your machine
Read from SKILL.md and the folder at commit 20a2376. It shows what the files ask for, not the result of running them.
Tool permissions
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.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are sql and yaml).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Relational Query Processor loads about 1k tokens when it runs. Until then it costs about 105 tokens; SKILL.md has 397 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.
Safety
Auto-check passed
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.
SKILL.md
The full file from FoundationDB/fdb-record-layer at commit 20a2376, republished under its Apache-2.0 licence (© FoundationDB). 397 words, ~1,026 tokens.
Download SKILL.mdSave it as
.claude/skills/relational-query-processor/SKILL.md (or your agent's skills folder).- name
- relational-query-processor
- description
- Specialized skill for working in the fdb-relational-core SQL processing layer — parser, plan generator, and Cascades planner. Use when debugging query plans, writing planner rules, or understanding the SQL execution path. Some example usages: "Why is this query doing a full table scan?" "Explain this EXPLAIN output" "How do I write a new Cascades rule?" "Why is my query not using the index?"
This skill provides context for working in fdb-relational-core, the SQL processing layer
of the Record Layer — covering the parser, plan generator, and Cascades planner.
Key entry points
| Class | Role |
|---|---|
EmbeddedRelationalStatement | Main SQL statement implementation. executeGet → point read via source.get(); executeScan → range scan via source.openScan(). |
RelationalDirectAccessStatement | Bypasses the SQL planner entirely — goes directly to FDB. |
RecordLayerEngine | Engine setup; manages the connection between JDBC and the record layer. |
RelationalPlanCache | Caches compiled query plans. Must be initialized for SQL performance — RelationalPlanCache.buildWithDefaults(). Without it, every query runs the full Cascades planner. |
SQL execution path (normal case)
JDBC call
→ EmbeddedRelationalStatement
→ SQL parse + Cascades planner (on cache miss)
→ LogicalQueryPlan.optimize()
→ Simplification.executeRuleSetIteratively() ← only on cold miss
→ RelationalPlanCache (warm hit: wraps existing plan)
→ PhysicalQueryPlan.withExecutionContext()
→ executePhysicalPlan()
→ FDB readOn a warm cache hit, simplification is skipped entirely. The planner overhead is ~0.3–0.5 ms per call.
Reading EXPLAIN output
Run EXPLAIN <query> via JDBC or in a yaml test:
EXPLAIN SELECT * FROM t WHERE id = 1Common plan shapes:
COVERING(idx_name [EQUALS ?] → [...])— index-only scan, no fetch needed.FETCH(COVERING(...))— index scan followed by a record fetch.SCAN(<,>) | FILTER ...— full table scan with a post-scan filter. This usually means the planner could not match a primary key or index scan candidate.MAP (_.col AS col)— projection step.
Writing a yaml test that checks the plan
- query: explain select * from t where id = 1
explain: "COVERING(idx_id [EQUALS ?] → [id: KEY[0], name: VALUE[0]])"Use @MaintainYamlTestConfig(YamlTestConfigFilters.CORRECT_EXPECTATIONS) on the test method
to have the framework fill in the explain: value automatically on first run.
Debugging a plan interactively
Add @DebugPlanner to the @YamlTest method to launch PlannerRepl, which lets you step
through the Cascades optimization phases.
Show full SKILL.md (178 more words)Show less
Cascades planner overview
The planner is a Cascades-style rule-based optimizer:
- Logical rules transform the logical plan (e.g., push predicates into index scans).
- Physical rules convert logical operators to physical plans (e.g., select index vs. scan).
- Match candidates (e.g.,
PrimaryScanMatchCandidate,ValueIndexScanMatchCandidate) determine which access paths are available for a given predicate. - Simplification runs
Derivations.simplifyLocalValues()— only on cold cache misses.
If a query is doing a full table scan when you expect an index scan, common causes:
- The predicate is on a non-indexed column.
- The index exists but the match candidate is not recognizing the predicate shape (check that the column names and types match exactly).
- The
RelationalPlanCacheis not initialized (every call looks like a cold miss).
Transaction lifecycle in tests
With autoCommit=true, ensureTransactionActive() rolls back and restarts the transaction
on every statement, clearing per-transaction caches. Both SQL and direct-access paths share
this overhead in benchmarks.
Schema templates
Schema templates persist in FDB across JVM runs. If you see unexpected state in tests, the template may be stale. Creation code should be idempotent (drop-then-create pattern).
© FoundationDB, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/relational-query-processor of FoundationDB/fdb-record-layer.
Open the folder on GitHubat commit 20a2376
Compare with similar skills
Relational Query Processor 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 |
|---|---|---|---|---|---|---|
| Relational Query Processor this skillFoundationDB/fdb-record-layer | 675 | — | ~1k | Automated safety check: Pass | Apache-2.0 | |
| Tidewave Integrationoliver-kriska/claude-elixir-phoenix | 564 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Code Nest Project Specxiaou61/Code-Nest | 770 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Kolokoloai/kolo | 525 | — | ~1.2k | Automated safety check: Pass | None | |
| SQL Optimization Patternsynulihao/AgentSkillOS | 617 | 10 repos | ~3.3k | Automated safety check: Pass | None | |
| PostgreSQL Documentation Reference2025Emma/vibe-coding-cn | 23k | 1 repos | ~19k | Automated safety check: Pass | MIT |
Similar skills
Code Nest Project Spec
xiaou61/Code-Nest
Code-Nest 多模块全栈项目协作规范与落点导航。Use when modifying this repository for feature development, bug fixing, refactor, API change, SQL migration, or frontend-backend联调 so changes land in the correct module…
Kolo
koloai/kolo
Kolo is a text-based Python debugger that captures every executed function, return value, local variable, HTTP request, and SQL query into greppable trace files.
SQL Optimization Patterns
ynulihao/AgentSkillOS
Master SQL query optimization, indexing strategies, and EXPLAIN analysis to dramatically improve database performance and eliminate slow queries.
PostgreSQL Documentation Reference
2025Emma/vibe-coding-cn
PostgreSQL database documentation - SQL queries, database design, administration, performance tuning, and advanced features. Use when working with PostgreSQL…
Golang Database
unxed/f4
Comprehensive guide for Go database access — parameterized queries, struct scanning, NULLable columns, transactions, isolation levels, SELECT FOR UPDATE, connection pool, batch processing, context…
More from FoundationDB/fdb-record-layer
All 10 skills in this repoUsing Gradle
FoundationDB/fdb-record-layer
A skill your agent uses when you need to build the project, compile code, or run tests.
Context Resumption
FoundationDB/fdb-record-layer
Rebuild working context after a session restart. An agent skill from FoundationDB/fdb-record-layer.
Docs Writer
FoundationDB/fdb-record-layer
Write or update documentation in docs/sphinx/source/. An agent skill from FoundationDB/fdb-record-layer.
Frl Coding Standard
FoundationDB/fdb-record-layer
Coding standards for all Java code in fdb-record-layer. An agent skill from FoundationDB/fdb-record-layer.
Frl Test Coding Standard
FoundationDB/fdb-record-layer
Standards for writing tests in fdb-record-layer. An agent skill from FoundationDB/fdb-record-layer.
Stacked PRs
FoundationDB/fdb-record-layer
Create and manage stacked pull requests on FoundationDB/fdb-record-layer using the gh stack CLI extension.
Related
Works with
Categories
Questions about Relational Query Processor
What does Relational Query Processor do?
Specialized skill for working in the fdb-relational-core SQL processing layer — parser, plan generator, and Cascades planner. Relational Query Processor is an agent skill from FoundationDB/fdb-record-layer. Specialized skill for working in the fdb-relational-core SQL processing layer — parser, plan generator, and Cascades planner.
When should I use Relational Query Processor?
Relational Query Processor fits situations like: debugging query plans; writing planner rules; understanding the SQL execution path.
How do I install Relational Query Processor in Claude Code?
Run `npx skills add FoundationDB/fdb-record-layer --skill relational-query-processor -a claude-code`. Or copy the skill folder (.claude/skills/relational-query-processor in FoundationDB/fdb-record-layer) into .claude/skills/relational-query-processor in your project. Claude Code loads it when a task matches its description.
How do I install Relational Query Processor in Codex?
Run `npx skills add FoundationDB/fdb-record-layer --skill relational-query-processor -a codex`. Or copy the skill folder (.claude/skills/relational-query-processor in FoundationDB/fdb-record-layer) into .agents/skills/relational-query-processor in your project. Codex loads it when a task matches its description.
Can I use Relational Query Processor in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add FoundationDB/fdb-record-layer --skill relational-query-processor -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/relational-query-processor, .gemini/skills/relational-query-processor, .github/skills/relational-query-processor and .opencode/skills/relational-query-processor in your project.
What does Relational Query Processor need to run?
SKILL.md names no scripts, command-line tools or credentials: Relational Query Processor is instructions for the agent only.
Does Relational Query Processor access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Relational Query Processor safe to install?
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.
What licence does Relational Query Processor use?
Relational Query Processor is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Relational Query Processor use?
About 1k tokens (SKILL.md is roughly 4.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Relational Query Processor?
Skills that share tags, products or a category with Relational Query Processor: Tidewave Integration (oliver-kriska/claude-elixir-phoenix, 564 stars), Code Nest Project Spec (xiaou61/Code-Nest, 770 stars), Kolo (koloai/kolo, 525 stars) and SQL Optimization Patterns (ynulihao/AgentSkillOS, 617 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Relational Query Processor?
FoundationDB (a GitHub organization) maintains it in FoundationDB/fdb-record-layer, which has 675 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 6, 2026.
Source: FoundationDB/fdb-record-layer on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.