microsoft / microsoft/sql-ai-promptathon

Mission: SQL + AI Promptathon Submission- Principal Data Analyst: Product Quality Risk Investigation

Open
#13 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Shell
Stars
49
Forks
132
PR merge metrics
No merged PRs in 30d

Description

Mission/open goal Description

Principal Data Analyst
Investigate a hidden product-quality issue by analyzing sales, support tickets, customer chat conversations, and product-related documents in the Promptathon database. Using GitHub Copilot Agent and SQL, the objective was to identify products with strong sales but unusually high support burden and low customer satisfaction, determine the root causes through evidence-based analysis, and provide actionable business recommendations.

Harness and model

GitHub Copilot Agent with GPT-5.5

Turn-by-turn journey
1. Prompt

Prompt: Read the Promptathon repository, explain the available missions, and recommend the best mission for a beginner.

Agent response/action: Reviewed the README and mission files, compared all available missions, and recommended the Principal Data Analyst mission.

Result: Selected the Data Analyst mission and understood the investigation workflow.


2. Prompt

Prompt: Guide me through the Data Analyst mission and inspect the available SQL database.

Agent response/action: Connected to the Promptathon SQL database using SQL MCP tools, listed available tables, and inspected the schema.

Result: Identified core tables including Products, SalesOrders, SalesOrderLines, SupportTickets, SupportChats, Docs, Customers, and Employees.


3. Prompt

Prompt: Identify the top-selling products based on revenue and quantity sold, then compare them with support tickets and customer satisfaction.

Agent response/action: Generated and executed SQL queries to aggregate sales data and correlate it with support ticket volume and satisfaction scores.

Result: Identified the Premium Short Sleeve Men's Top (SKU: ZCPTM-SS-M-BW) as the strongest product-quality risk candidate.


4. Prompt

Prompt: Investigate the root cause using support chats and customer documents.

Agent response/action: Analyzed support chat conversations and customer documents to identify recurring complaint themes.

Result: Found repeated complaints related to connectivity failures, wash durability, sensor issues, and customer returns.


5. Prompt

Prompt: Prepare a complete Promptathon submission with findings, SQL evidence, recommendations, architecture, and reflections.

Agent response/action: Generated a structured Markdown report summarizing the investigation, evidence, business recommendations, and lessons learned.

Result: Produced a complete GitHub Issue submission ready for review.

Completion
  • Yes, the agent completed the mission or goal.
  • No, the agent did not complete the mission or goal.
Bonus work

Beyond the core mission, I validated the AI-generated insights by reviewing SQL query outputs before drawing conclusions. I combined structured SQL analysis with qualitative evidence from support chats and customer documents to strengthen the investigation. I also documented the complete analytical workflow, business recommendations, and a Mermaid architecture diagram to produce a professional, evidence-based submission.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the repository README and mission files, then review the SQL schema and outputs for Products, SalesOrders, SalesOrderLines, SupportTickets, SupportChats, Docs, Customers, and Employees. Verify that the reported product-quality findings, supporting evidence, recommendations, and Mermaid architecture diagram are complete and consistent; the submission is done when the evidence-based report is ready for review.

Written by the indexing model from the issue text.

Assessment

Tech stack
github, sql
Domain
analytics, data, databases, documentation
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.