Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    SQL Report Builder for Non-Technical Managers

    2

    Turns plain-English business questions into safe read-only SQL reporting plans, required table/field maps, readable SQL drafts, validation checks, and manager-friendly summaries.

    $50

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    SQL Report Builder for Non-Technical Managers

    SQL Report Builder for Non-Technical Managers

    Example session with this skill installed

    How many customers churned last month by plan? I want a safe read-only SQL draft, plain-English explanation, assumptions, validation checks, and a manager-friendly summary. Assume PostgreSQL if no dialect is provided.

    • Read your context and instructions
    • Compiled the sql report builder

    === SQL REPORTING PLAN FOR NON-TECHNICAL MANAGERS ===

    Business question
    How many customers churned last month by plan?

    Plain-English interpretation
    The user wants a count of customers whose subscription ended during the previous calendar month, grouped by subscription plan.

    Decision supported
    Understand which plans had the highest customer churn last month.

    Metric definition

    Metric name
    Customer churn count by plan

    Business definition
    Number of customers whose subscription ended during the reporting period and should be counted as churned.

    Numerator
    Count of distinct customers with a subscription status of canceled or ended during last month.

    Denominator
    Not required for churn count. If churn rate is needed, denominator should be active customers at the start of the month.

    Date logic
    Use subscription ended/canceled date, not signup date.

    Inclusions
    Paid customer subscriptions that ended during the period.

    Exclusions
    Trial users, test accounts, internal accounts, and customers who reactivated within the defined grace period if the business uses one.

    Grouping dimensions
    Plan name.

    Expected grain
    One row per plan.

    Required tables and fields
    subscriptions.subscription_id — identify subscription
    subscriptions.customer_id — identify customer
    subscriptions.plan_id — connect to plan
    subscriptions.status — identify canceled/ended subscriptions
    subscriptions.ended_at or canceled_at — churn date
    plans.plan_id — join to subscriptions
    plans.plan_name — group by plan
    customers.customer_id — identify customer
    customers.is_test — exclude test accounts if available

    Assumptions

    1. subscriptions.ended_at represents the churn date.
    2. subscriptions.status = 'canceled' indicates churn.
    3. customers.is_test can identify test accounts.
    4. Plans are stored in a plans table.
    5. SQL dialect is PostgreSQL. Adjust date functions if using another database.

    Safety check

    • Query type: read-only SELECT
    • Sensitive fields avoided: Yes
    • Destructive operations: None
    • Date range included: Yes
    • Row limit recommended: Not required because output is aggregated

    SQL reporting plan

    1. Start from subscriptions.
    2. Join plans to get plan names.
    3. Join customers to exclude test accounts.
    4. Filter subscriptions that ended last month.
    5. Count distinct customers.
    6. Group by plan name.
    7. Sort by churn count descending.

    Readable SQL draft
    [The skill returns a read-only SELECT query using CTEs, date filtering, grouping by plan, and no destructive operations.]

    Plain-English explanation
    This query looks for subscriptions marked as canceled during the previous calendar month. It excludes test customers, connects each subscription to its plan, counts unique customers, and shows the result grouped by plan.

    Validation queries

    1. Check total churn count before grouping.
    2. Check whether ended_at has null values for canceled subscriptions.
    3. Check whether test accounts are correctly excluded.
    4. Compare the total with the existing churn dashboard if available.

    Data quality risks

    • Some churn may be stored as status = 'ended' instead of 'canceled'.
    • Reactivated customers may need to be excluded depending on business definition.
    • Trial cancellations may be mixed with paid churn.
    • Timezone may affect month boundaries.

    Privacy/sensitivity notes
    The report uses aggregate customer counts and does not expose names, emails, or account details.

    Manager-friendly report summary
    For last month, the report shows how many customers churned in each plan. The highest churn plan should be reviewed for onboarding, pricing, product fit, or support issues. This result depends on the chosen churn definition and whether reactivations or trials are excluded.

    Analyst handoff notes
    Confirm the correct churn date field, churn status values, plan table name, and test-account flag before running in production reporting.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    SQL Report Builder for Non-Technical Managers helps managers, operations teams, analysts, founders, SaaS operators, and small business teams turn business questions into safe analytics workflows. It defines metrics, identifies required tables and fields, maps joins, drafts readable read-only SQL, explains the logic in plain English, validates assumptions, creates data quality checks, audits SQL for safety, and produces manager-friendly report summaries or analyst handoff briefs. The skill supports common reporting needs such as revenue, churn, retention, active users, sales pipeline, support backlog, product funnels, cohort analysis, subscriptions, invoices, and operational KPIs. It defaults to safe read-only reporting and avoids destructive SQL.

    This skill creates safe SQL reporting plans and draft read-only SQL, but it does not guarantee that a query is correct without the actual schema, metric definitions, data quality checks, business rules, and analyst review. Table names, column names, date logic, joins, and metric definitions may vary across organizations. For production analytics, queries should be reviewed and tested in approved read-only environments. The skill should not be used for destructive SQL, unauthorized data extraction, privacy-invasive reporting, or database administration.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 5 months ago

    Permissions

    Write Files
    Read Files

    File Scopes

    *.md
    *.txt
    *.csv
    *.xlsx
    *.json
    *.yaml
    *.yml
    *.sql
    *.docx
    *.pdf
    README.md
    schemas/**
    data-dictionaries/**
    metrics/**
    reports/**
    dashboards/**
    sql/**
    queries/**
    analytics/**
    bi/**
    exports/**
    requirements/**
    docs/**

    This skill uses file access to read user-provided schemas, table lists, metric definitions, SQL drafts, report notes, dashboard requirements, CSV exports, data dictionaries, and analytics documentation. It uses write access to create structured Markdown/text outputs such as SQL reporting plans, metric definitions, table/field maps, readable SQL drafts, validation checklists, SQL safety audits, dashboard specifications, manager-friendly summaries, analyst handoff briefs, and SKILL.md files. Optional schema access should be limited to metadata in approved read-only analytics environments. The default safe setup does not require network access, shell access, environment variable access, production write access, or destructive database permissions.

    Listed5 months ago

    What's inside

    Frequently Asked Questions

    This skill bridges the gap between natural language and database queries. It takes your business questions and converts them into structured reporting plans, including field mapping, join logic, and safe, read-only SQL drafts that you can either run yourself or hand off to a developer.

    For security and data integrity, the skill is designed to generate read-only SELECT statements exclusively. It explicitly avoids and audits against destructive commands like DROP, DELETE, or UPDATE, making it a safe choice for generating reporting logic.

    The skill is optimized for all major AI agents and LLMs that support markdown and text-based reasoning. Simply import the skill into your preferred agent platform to start generating report drafts immediately.

    No direct database connection is required. You provide the context—such as table names or general business requirements—and the skill provides the logic, schema maps, and SQL drafts for you to use in your preferred data environment.

    You receive the full skill logic designed for non-technical reporting, a framework for data validation checks, and a template for creating analyst handoff briefs. This ensures that even if you aren't running the SQL yourself, you have a professional document ready for your technical team.

    The skill is highly versatile and handles standard reporting for SaaS, e-commerce, and general operations, including complex metrics like churn, cohort analysis, retention, and multi-table sales funnels.

    New in Data & Databases