Edisyl CLI
First, check the CLI is installed and authenticated:
edisyl --version
edisyl whoami
If the command is missing, install it:
curl -fsSL https://raw.githubusercontent.com/FlipsideCrypto/edisyl-tools/main/install.sh | sh
Then run the in-CLI navigation guide:
edisyl llm onboard
In-CLI reference (use these for deep reference)
The CLI ships embedded docs that stay in sync with the deployed version. Prefer these over guessing — they're offline, auth-free, and exhaustive.
| Topic |
Run |
| Agents — author, validate, push, pull, run YAML-defined agents |
edisyl llm agents |
| Skills — package reusable knowledge + tools for agents |
edisyl llm skills |
| Data sources — connect a warehouse, kick the introspect/enrich pipeline |
edisyl llm data-sources |
| Stratum — natural-language → SQL resolve, indexing, cascade debugging, curation |
edisyl llm stratum |
| Queries — direct SQL (rare — agents/Stratum handle this) |
edisyl llm queries |
Reports — visualizations and the data_visualization skill |
edisyl llm reports |
The three surfaces
| Surface |
What you do |
Where to learn more |
| Agents & skills |
Author YAML, validate, push, pull, run |
edisyl llm agents · edisyl llm skills |
| Fleets, teams, missions |
Compose agents into fleets, run missions, chat |
edisyl llm onboard |
| Data sources & Stratum |
Connect a warehouse, then resolve NL questions to SQL |
edisyl llm data-sources · edisyl llm stratum |
Global flags worth knowing: -j/--json (every command), -p/--profile, -e local|staging|prod (endpoint override), -v (verbose request/response logging).
Common one-liners
# Agents & skills
edisyl agent init <name> && edisyl agent push <file>
edisyl skills init <name> && edisyl skills push <file>
# Fleets + missions
edisyl fleet list
edisyl mission create <fleet> "<prompt>" --follow
edisyl mission tree <id>
edisyl chat <fleet> # @<agent-slug> to target one agent
# Data source onboarding
edisyl data-sources test-connection --type postgres --config-file db.json
edisyl data-sources create --name "Demo" --type postgres --config-file db.json
edisyl stratum status -d <data-source-id>
# Stratum resolve + diagnose
edisyl stratum resolve "<question>" -d <ds> --wait --rows 5
edisyl stratum trace <resolution-id>
edisyl stratum candidates list
When in doubt, run the matching edisyl llm <topic> for the exhaustive reference.
1---2name: edisyl3description: Build and run AI agent fleets on the Flipside platform, connect data warehouses, and resolve natural-language analytics questions through Stratum. Use when authoring agents and skills from YAML, composing them into fleets and teams, starting missions, connecting a data source (Snowflake, Postgres, BigQuery, Databricks, Redshift, MySQL), or driving Stratum NL→SQL resolve and indexing. Requires the Edisyl CLI (https://github.com/FlipsideCrypto/edisyl-tools).4---56# Edisyl CLI78First, check the CLI is installed and authenticated:910```bash11edisyl --version12edisyl whoami13```1415If the command is missing, install it:1617```bash18curl -fsSL https://raw.githubusercontent.com/FlipsideCrypto/edisyl-tools/main/install.sh | sh19```2021Then run the in-CLI navigation guide:2223```bash24edisyl llm onboard25```2627## In-CLI reference (use these for deep reference)2829The CLI ships embedded docs that stay in sync with the deployed version. Prefer these over guessing — they're offline, auth-free, and exhaustive.3031| Topic | Run |32|---|---|33| **Agents** — author, validate, push, pull, run YAML-defined agents | `edisyl llm agents` |34| **Skills** — package reusable knowledge + tools for agents | `edisyl llm skills` |35| **Data sources** — connect a warehouse, kick the introspect/enrich pipeline | `edisyl llm data-sources` |36| **Stratum** — natural-language → SQL resolve, indexing, cascade debugging, curation | `edisyl llm stratum` |37| **Queries** — direct SQL (rare — agents/Stratum handle this) | `edisyl llm queries` |38| **Reports** — visualizations and the `data_visualization` skill | `edisyl llm reports` |3940## The three surfaces4142| Surface | What you do | Where to learn more |43|---|---|---|44| **Agents & skills** | Author YAML, validate, push, pull, run | `edisyl llm agents` · `edisyl llm skills` |45| **Fleets, teams, missions** | Compose agents into fleets, run missions, chat | `edisyl llm onboard` |46| **Data sources & Stratum** | Connect a warehouse, then resolve NL questions to SQL | `edisyl llm data-sources` · `edisyl llm stratum` |4748Global flags worth knowing: `-j/--json` (every command), `-p/--profile`, `-e local|staging|prod` (endpoint override), `-v` (verbose request/response logging).4950## Common one-liners5152```bash53# Agents & skills54edisyl agent init <name> && edisyl agent push <file>55edisyl skills init <name> && edisyl skills push <file>5657# Fleets + missions58edisyl fleet list59edisyl mission create <fleet> "<prompt>" --follow60edisyl mission tree <id>61edisyl chat <fleet> # @<agent-slug> to target one agent6263# Data source onboarding64edisyl data-sources test-connection --type postgres --config-file db.json65edisyl data-sources create --name "Demo" --type postgres --config-file db.json66edisyl stratum status -d <data-source-id>6768# Stratum resolve + diagnose69edisyl stratum resolve "<question>" -d <ds> --wait --rows 570edisyl stratum trace <resolution-id>71edisyl stratum candidates list72```7374When in doubt, run the matching `edisyl llm <topic>` for the exhaustive reference.
flipsidecrypto