agentleFS
stackqlstackql/stackql-skills/skills/notebook-cell/SKILL.md

notebook-cell

Skill0 starsChanged 8 months agoMITView on GitHub

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.

The file

Show its rules and text

We split this skill into the rules it gives an agent

17 rules. About 0 are common, 10 are distinctive, and 7 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈10

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 7

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Follow these steps in order.

    line 15
  2. Very specific:

    Look for open or recently modified .ipynb files:

    line 19
  3. Distinctive:

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

    line 25
  4. Distinctive:

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

    line 31
  5. Very specific:

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

    line 33
  6. Distinctive:

    Read the notebook to understand:

    line 37
  7. Distinctive:

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

    line 52
  8. Distinctive:

    Follow these rules for all notebook cells:

    line 62
  9. Very specific:

    No horizontal rules (---, *, ___) or <hr/> tags

    line 64
  10. Distinctive:

    Use spacing and headings to separate sections, not horizontal rules

    line 65
  11. Distinctive:

    Create 2-3 cells to insert:

    line 67
  12. Very specific:

    Add --no-display to the %%stackql line if the flag was passed

    line 94
  13. Very specific:

    Add --csv-download if the user wants export capability

    line 95
  14. Very specific:

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

    line 97
  15. Very specific:

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

    line 99
  16. Distinctive:

    Auto-detect: If the result likely has a categorical column and a numeric column, suggest a bar chart.

    line 118
  17. Distinctive:

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

    line 122

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.