agentsclimarketplace

Notebook cell

Skill stackql/stackql-skills/skills/notebook-cell

Claude Code plugin for querying cloud infrastructure and SaaS APIs using SQL with StackQL

Install
npx -y skills add stackql/stackql-skills --skill notebook-cell

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Generate and insert StackQL query cells into an existing Jupyter notebook. Creates a markdown heading cell and a %%stackql query cell, with optional visualization. Works with the pystackql magic extension.

SKILL.md

3.7 KB, as published. Nobody here has run it

You are helping the user add StackQL query cells to an existing Jupyter notebook that uses the pystackql magic extension.

Input: $@

Follow these steps in order.

Step 1 - Find the target notebook

Look for open or recently modified .ipynb files:

find . -name "*.ipynb" -not -path '*/.git/*' -not -path '*/.ipynb_checkpoints/*' 2>/dev/null

If multiple notebooks exist, check which ones already use pystackql:

grep -l "pystackql" *.ipynb 2>/dev/null

If there are multiple candidates, ask the user which notebook to add cells to.

If no notebook exists, suggest using /stackql-skills:notebook to create one first.

Step 2 - Read the existing notebook

Read the notebook to understand:

  • Which magic extension is loaded (pystackql.magic or pystackql.magics)
  • What providers have been pulled
  • What Python variables are defined (these can be used in queries via $variable)
  • How many cells exist (to determine insert position)
  • What queries already exist (to avoid duplication)

Step 3 - Parse the request

Determine what the user wants:

  • Raw SQL: the user provided a StackQL query directly
  • Natural language: the user described what they want to query - generate the SQL
  • --viz flag: what visualization to add (bar, line, table, or auto-detect)
  • --no-display: suppress query output display

If the input is natural language, use the existing notebook context (pulled providers, variables) to generate the appropriate query. If needed, discover the schema:

stackql exec "DESCRIBE <provider>.<service>.<resource>;" --output json

Step 4 - Generate the cells

Cell conventions

Follow these rules for all notebook cells:

  • One heading per cell, placed at the top
  • No horizontal rules (---, ***, ___) or <hr/> tags
  • Use spacing and headings to separate sections, not horizontal rules

Create 2-3 cells to insert:

Markdown cell

## <Section Title>

<Brief description of what this query does.>

Query cell

For single-line queries:

%stackql <QUERY>

For multi-line queries:

%%stackql
SELECT
    <fields>
FROM <provider>.<service>.<resource>
WHERE <params>

Options:

  • Add --no-display to the %%stackql line if the flag was passed
  • Add --csv-download if the user wants export capability

Use $variable substitution for any values that match Python variables already defined in the notebook.

Use $$ to escape literal dollar signs in JSON path expressions.

Visualization cell (if --viz or auto-detected)

Bar chart (--viz bar):

stackql_df.plot(kind='bar', x='<x_col>', y='<y_col>', title='<Title>');

Line chart (--viz line):

stackql_df.plot(kind='line', x='<x_col>', y='<y_col>', title='<Title>');

Table (--viz table):

stackql_df

Auto-detect: If the result likely has a categorical column and a numeric column, suggest a bar chart. If it has a date/time column and a numeric column, suggest a line chart. Otherwise, just display as a table.

Step 5 - Insert the cells

Use the NotebookEdit tool to insert the cells at the end of the notebook (or at a user-specified position).

Step 6 - Report

Briefly confirm what was added:

  • The query that was inserted
  • The visualization type (if any)
  • Remind the user to run the cells in order
  • Note that stackql_df will contain the query results as a pandas DataFrame

Gives 0 of the 12 instructions most data analysis skills give

Counted across 286 of the 286 authors here whose files we hold, read 2026-08-06

  • use excel formulas instead of hardcoded calculated valuesin 35 of 286, across 7 files
  • match existing template conventions when modifying filesin 35 of 286, across 7 files
  • document sources for all hardcoded valuesin 35 of 286, across 7 files
  • write minimal concise python codein 35 of 286, across 7 files
  • place all assumptions in separate assumption cellsin 32 of 286, across 5 files
  • apply industry-standard color coding to financial modelsin 31 of 286, across 5 files
  • format years as text stringsin 30 of 286, across 3 files
  • recalculate formulas using recalc.py after modificationsin 30 of 286, across 3 files
  • format negative numbers using parenthesesin 30 of 286, across 3 files
  • fix all identified formula errors before finishingin 27 of 286, across 1 file
  • use colorblind-safe palettesin 19 of 286, across 12 files
  • Name tests after the prevented bugin 13 of 286, across 8 files

Said here and by no other author read

  • Find open or recently modified notebooks
  • Ask the user if multiple notebooks exist
  • Read the existing notebook
  • Generate a markdown heading cell
  • Generate a StackQL query cell
  • Generate a visualization cell if requested

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.