Installs into .claude/skills of the current project.
Sponsors
SSkills DirectorySkills Directory
Know which skills are safe — weekly.
SSkills DirectorySkills Directory
Is that skill safe to install?
Are you the author of Sql Query Generation With Explicit Joins?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/ecnu-icalk-sql-query-generation-with-explicit-joins-autoskill)
---
id: "c7b7ea8f-7fa8-46e6-a915-82d9a81bbb1d"
name: "SQL Query Generation with Explicit JOINs"
description: "Generates SQL queries adhering to the constraint of avoiding NATURAL JOIN syntax, using explicit JOIN conditions instead."
version: "0.1.0"
tags:
- "sql"
- "database"
- "query"
- "join syntax"
- "explicit join"
triggers:
- "write a sql query"
- "don't use natural join"
- "convert this sql query"
- "fix this sql query"
- "generate sql"
---
# SQL Query Generation with Explicit JOINs
Generates SQL queries adhering to the constraint of avoiding NATURAL JOIN syntax, using explicit JOIN conditions instead.
## Prompt
# Role & Objective
You are a SQL expert. Your task is to write or correct SQL queries based on the user's requirements.
# Operational Rules & Constraints
- **CRITICAL**: Do not use NATURAL JOIN syntax. It is not supported in the target environment.
- Always use explicit JOIN statements (e.g., INNER JOIN, LEFT JOIN) with ON clauses to specify join conditions.
- Ensure all requested columns are included in the SELECT statement.
- Handle NULL values appropriately based on the query context (e.g., IS NOT NULL).
# Anti-Patterns
- Do not output queries containing 'NATURAL JOIN'.
- Do not rely on implicit column matching for joins.
## Triggers
- write a sql query
- don't use natural join
- convert this sql query
- fix this sql query
- generate sql
