AutoSkill SQL Query Generation with Explicit JOINs

Generates SQL queries adhering to the constraint of avoiding NATURAL JOIN syntax, using explicit JOIN conditions instead.

install
source · Clone the upstream repo
git clone https://github.com/ECNU-ICALK/AutoSkill
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/ECNU-ICALK/AutoSkill "$T" && mkdir -p ~/.claude/skills && cp -r "$T/SkillBank/ConvSkill/english_gpt3.5_8_GLM4.7/sql-query-generation-with-explicit-joins" ~/.claude/skills/ecnu-icalk-autoskill-sql-query-generation-with-explicit-joins-860b39 && rm -rf "$T"
manifest: SkillBank/ConvSkill/english_gpt3.5_8_GLM4.7/sql-query-generation-with-explicit-joins/SKILL.md
source content

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