stackql-docs
Skill0 starsChanged 8 months agoMITView on GitHub
Search StackQL documentation, provider registry docs, and blog posts. Fetches content from stackql.io/docs, registry.stackql.io, and provider-specific doc sites.
In this repository10 other files it gives its agents.
- auth-setupSkill
- exploreSkill
- install-stackqlSkill
- notebook-cellSkill
- notebookSkill
- pull-providerSkill
- querySkill
- read-memoriesSkill
- scaffold-stackSkill
- setup-ciSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Follow these steps in order.
- Distinctive: line 47
Use web search to find relevant documentation pages:
- Very specific: line 49
Search for: site:stackql.io <query terms> or the appropriate provider site.
- Very specific: line 51
If the query is provider-specific, also search: site:<provider>.stackql.io <query terms>
- Distinctive: line 57
Use the WebFetch tool to retrieve the documentation page content.
- Distinctive: line 96
After presenting the sources, synthesize a concise answer to the user's original question.
- Distinctive: line 98
If no relevant documentation was found, suggest:
≈ “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.
Files
You are helping the user find relevant StackQL documentation.
Query: $@
Follow these steps in order.
Step 1 - Classify the query
Determine what kind of documentation the user needs:
- StackQL core (SQL syntax, CLI flags, commands, general usage) -> search stackql.io/docs
- Provider-specific (how to query a specific provider, resource schemas, auth for a provider) -> search the provider docs site
- Registry (available providers, versions) -> search registry.stackql.io
- Blog/tutorials (how-to guides, examples, use cases) -> search stackql.io/blog
- stackql-deploy (IaC workflows, manifests, deployment) -> search stackql-deploy.io
Step 2 - Determine the documentation URLs
| Topic | Primary URL |
| Core docs | https://stackql.io/docs |
| CLI reference | https://stackql.io/docs/command-line-usage/global-flags |
| Registry commands | https://stackql.io/docs/command-line-usage/registry |
| Provider registry | https://registry.stackql.io/ |
| Google provider | https://google.stackql.io/ |
| AWS provider | https://awscc.stackql.io/ |
| Azure provider | https://azure.stackql.io/ |
| GitHub provider | https://github.stackql.io/ |
| Okta provider | https://okta.stackql.io/ |
| Databricks provider | https://databricks-workspace.stackql.io/ |
| Snowflake provider | https://snowflake.stackql.io/ |
| stackql-deploy | https://stackql-deploy.io/docs |
| Blog | https://stackql.io/blog |
Step 3 - Search for documentation
Use web search to find relevant documentation pages:
Search for: site:stackql.io <query terms> or the appropriate provider site.
If the query is provider-specific, also search: site:<provider>.stackql.io <query terms>
Step 4 - Fetch and extract relevant content
For the most relevant search results (up to 3-4 pages), fetch the page content:
Use the WebFetch tool to retrieve the documentation page content.
Extract the relevant sections that answer the user's question.
Step 5 - Handle common topics directly
For frequently asked topics, you can provide answers from your knowledge:
StackQL SQL syntax basics
SELECTreads cloud resources (maps to GET/LIST API calls)INSERT INTO ... SELECTcreates resources (maps to POST/PUT)UPDATE ... SET ... WHEREmodifies resources (maps to PATCH/PUT)DELETE FROM ... WHEREremoves resources (maps to DELETE)EXEC <resource>.<method>runs lifecycle operations (start, stop, etc.)
Provider hierarchy
SHOW PROVIDERS;- list installed providersSHOW SERVICES IN <provider>;- list servicesSHOW RESOURCES IN <provider>.<service>;- list resourcesDESCRIBE <provider>.<service>.<resource>;- show fieldsSHOW METHODS IN <provider>.<service>.<resource>;- show methods
CLI usage
- Interactive:
stackql shell --auth="${AUTH}" - Non-interactive:
stackql exec --auth="${AUTH}" "<SQL>" - From file:
stackql exec --auth="${AUTH}" -i script.iql - Output formats:
--output json|csv|table|text
Step 6 - Present results
For each relevant documentation section found, format as:
### <Section title>
<URL>
<Relevant content>After presenting the sources, synthesize a concise answer to the user's original question. If the documentation directly answers the question, lead with the answer before showing the sources.
If no relevant documentation was found, suggest:
- Visiting https://stackql.io/docs directly
- Checking the provider-specific docs site
- Using
/stackql-skills:explore <provider>to discover resources interactively
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
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.

