Install any skill in seconds. Free to start, no credit card required.
Get Started Free →microck/sql-translation
Guide for adding SQL function translations to dbplyr backends.
Passed 22 of 24 test cases with the skill, and 13 of 24 without it.
and 7 more in the full report
9 fixed13 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
We need to format R files before submitting a pull request to dbplyr. I usually run `styler::style_pkg()`. What specific CLI command should be executed for code formatting?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies running air format . to format the code | Missed | Passed |
The instructions your model reads when the skill loads.
Use this skill when adding new SQL function translations for a specific database backend.
This skill guides you through adding SQL translations to dbplyr. SQL translations convert R functions to their SQL equivalents for different database backends.
Before implementing any SQL translation, you MUST research the SQL syntax and behavior using the sql-research skill. See that skill for the complete research workflow.
Quick summary:
research/{dialect}-{function}.mdSQL translations are defined in backend-specific files:
R/backend-sqlite.R - SQLiteR/backend-postgres.R - PostgreSQLR/backend-mysql.R - MySQLR/backend-mssql.R - MS SQL ServerTranslations are added to the sql_translation() method for the connection class. This method returns a sql_variant() with three components:
Scalar translations (for mutate/filter):
sql_translator(.parent = base_scalar,
# Simple function name mapping
log10 = function(x) sql_expr(log(!!x)),
# Function with different arguments
test cases passed, vs 13 / 24 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.