query-writing

langchain-ai/deepagents · updated Apr 8, 2026

$npx skills add https://github.com/langchain-ai/deepagents --skill query-writing
0 commentsdiscussion
summary

For straightforward questions about a single table:

skill.md

Query Writing Skill

Workflow for Simple Queries

For straightforward questions about a single table:

  1. Identify the table - Which table has the data?
  2. Get the schema - Use sql_db_schema to see columns
  3. Write the query - SELECT relevant columns with WHERE/LIMIT/ORDER BY
  4. Execute - Run with sql_db_query
  5. Format answer - Present results clearly

Workflow for Complex Queries

For questions requiring multiple tables:

1. Plan Your Approach

Use write_todos to break down the task:

  • Identify all tables needed
  • Map relationships (foreign keys)
  • Plan JOIN structure
  • Determine aggregations

2. Examine Schemas

Use sql_db_schema for EACH table to find join columns and needed fields.

3. Construct Query

  • SELECT - Columns and aggregates
  • FROM/JOIN - Connect tables on FK = PK
  • WHERE - Filters before aggregation
  • GROUP BY - All non-aggregate columns
  • ORDER BY - Sort meaningfully
  • LIMIT - Default 5 rows

4. Validate and Execute

Check all JOINs have conditions, GROUP BY is correct, then run query.

Example: Revenue by Country

SELECT
    c.Country,
    ROUND(SUM(i.Total), 2) as TotalRevenue
FROM Invoice i
INNER JOIN Customer c ON i.CustomerId = c.CustomerId
GROUP BY c.Country
ORDER BY TotalRevenue DESC
LIMIT 5;

Error Recovery

If a query fails or returns unexpected results:

  1. Empty results — Verify column names and WHERE conditions against the schema; check for case sensitivity or NULL values
  2. Syntax error — Re-examine JOINs, GROUP BY completeness, and alias references
  3. Timeout — Add stricter WHERE filters or LIMIT to reduce result set, then refine

Quality Guidelines

  • Query only relevant columns (not SELECT *)
  • Always apply LIMIT (5 default)
  • Use table aliases for clarity
  • For complex queries: use write_todos to plan
  • Never use DML statements (INSERT, UPDATE, DELETE, DROP)

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.767 reviews
  • Dhruvi Jain· Dec 28, 2024

    Useful defaults in query-writing — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Arjun Brown· Dec 24, 2024

    query-writing fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Aarav Singh· Dec 8, 2024

    query-writing has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Sophia Tandon· Dec 4, 2024

    I recommend query-writing for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Min Okafor· Nov 27, 2024

    query-writing fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Zara Sethi· Nov 23, 2024

    Keeps context tight: query-writing is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Oshnikdeep· Nov 19, 2024

    query-writing is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Anika Ndlovu· Nov 15, 2024

    query-writing has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Amelia Harris· Oct 18, 2024

    We added query-writing from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Charlotte Mensah· Oct 14, 2024

    query-writing is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

showing 1-10 of 67

1 / 7