Talon CQL
approvedby Caio Lopes
Syntax highlighting for CrowdStrike CQL (LogScale Query Language) in code blocks. - This plugin has not been manually reviewed by Obsidian staff.
talon-cql
Obsidian plugin — syntax highlighting for CrowdStrike CQL (LogScale Query Language)
Threat hunters who document their work in Obsidian — playbooks, runbooks, DFIR notes — can now get proper syntax highlighting for embedded CQL queries. No equivalent plugin exists in the Obsidian community.

Usage
```cql
#event_simpleName=ProcessRollup2
ImageFileName=/powershell\.exe/i
| groupBy([ComputerName, CommandLine], function=count())
| sort(count, order=desc)
```
Also accepts ```logscale as an alias.
Works in both reading mode and editing mode.
Install
Community Plugin
Install from the Obsidian Community Plugins directory, or search for Talon CQL in Settings → Community Plugins.
Manual
- Download
main.js,manifest.json,styles.cssfrom the latest release - Create
.obsidian/plugins/talon-cql/in your vault - Copy the three files there
- Enable in Settings → Community Plugins
What gets highlighted
| Token | Example |
|---|---|
| Event fields | #event_simpleName, #aid, #cid |
| Built-in functions | groupBy, eval, timeChart, join |
| Namespaced functions | array:contains, math:abs, time:hour |
| Keywords | case, and, or, not, asc, desc |
| Operators | | := =~ != <= >= |
| Strings | "double" 'single' |
| Regex literals | /pattern/i |
| Numbers | 42, 3.14 |
| Comments | // and /* */ |
Query Templates
Ready-to-use hunting queries in templates/:
| File | Content |
|---|---|
process-hunting.cql | LOLBins, encoded PowerShell, parent-child chains |
network-hunting.cql | Beaconing, suspicious ports, geo anomalies |
identity-hunting.cql | Brute force, off-hours logons, LSASS access |
Build
npm install
npm run build # production → generates main.js
npm run dev # watch mode for development
References
- Talon CQL on Obsidian Community Plugins
- CQL Syntax Reference
- LogScale Functions
- CrowdStrike LogScale Community Content
License
MIT
For plugin developers
Search results and similarity scores are powered by semantic analysis of your plugin's README. If your plugin isn't appearing for searches you'd expect, try updating your README to clearly describe your plugin's purpose, features, and use cases.