Apache Doris Skills is a collection of agent instructions containing Apache Doris database knowledge for designing, sizing, operating, diagnosing, and contributing to Doris clusters. It serves developers and operators using Claude Code, Cursor, Codex, Cline, Amp, and other agent tools, with the skills providing decision logic and evidence-based workflows.
Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/apache/doris-skillsnpx agentmods add skills/apache/doris-skills/queryWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/apache/doris-skills/query)<a href="https://agentmods.dev/skills/apache/doris-skills/query"><img src="https://agentmods.dev/badge/skills/apache/doris-skills/query/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/apache/doris-skills/query"><img src="https://agentmods.dev/badge/skills/apache/doris-skills/query.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00062 | $0.00845 |
| Opus 5.5 | $0.00025 | $0.00338 |
| Sonnet 5.5 | $0.00012 | $0.00169 |
| Haiku 4.5 | $0.00006 | $0.00085 |
Grade A, and why
doris-debug-query scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s "http://$FE:8030/api/query_profile?query_id=$QID" How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Query Troubleshooting
Causes
| ID | Cause | Evidence |
|---|---|---|
| A | Client timeout too small | query_timeout vs Profile wall |
| B | Planner | Nereids cost too much time / nereids_timeout_second |
| C | BE compute (scan/join/spill) | Profile active ExecTime |
| D | Exchange / brpc | WaitForData ≈ timeout; failed to send brpc when exchange; [E1008] on :8060 |
10 min
SET enable_profile = true;
-- reproduce
./scripts/doris-debug log-grep fe/log be/log --query-id "$QID" --pack planner
./scripts/doris-debug log-grep be/log --query-id "$QID" --pack exchange
./scripts/doris-debug audit-topk fe/log/fe.audit.log -k 20 --min-ms 5000
Planner mitigation (session only): SET disable_join_reorder=true; for fat ETL joins; fix stats with ANALYZE.
Cause C — BE compute (scan/join/spill)
When Profile shows high active ExecTime (not Wait*), route to doris-profile-reader for deep Profile analysis:
Skill routing: If
doris-profile-readeris available, invoke it with the query's Profile to identify which operator (scan/join/agg/spill) dominates. Key indicators to pass:
ActiveTimeper operatorRowsRead/ScanBytesfor scan operatorsSpillDataSizeif disk spill occurredJoinType+JoinRowsfor join operators
Without profile-reader, check directly:
# Get the Profile text
curl -s "http://$FE:8030/api/query_profile?query_id=$QID"
Key Profile counters for Cause C:
| Counter | Meaning | Threshold |
|---|---|---|
ScannerGetBlockTime |
Time reading from storage | > 50% of ExecTime → IO bound |
SpillDataSize |
Data spilled to disk | > 0 → memory pressure, check enable_spill |
JoinProbeTime |
Hash join probe wall time | > 30% → check join order / type |
RowsRead / ScanBytes |
Scan volume | > 1B rows → check partition pruning |
Profile interpretation: prefer active time over Wait*.
Cause D — Exchange / brpc
Code facts (apache/doris):
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 88 lines · 62 tokens per session scan A 675cd25e2b20
doris-debug-query is a skill published in the GitHub repository apache/doris-skills (47 stars, last pushed 17d ago), licensed Apache-2.0. It adds 62 tokens to every session and 845 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
cf-fix
Quick bug-fix workflow — reproduce, find the root cause, fix via cf-implementer, verify, auto-review. TRIGGER — the user reports a bug or broken behavior: "fix this", "it's broken", "not working", "there's a bug", "this crashes", "debug this", "it throws", "failing test", "regression", "unexpected behavior"; a pasted…
cf-optimize
Structured performance work — baseline, analyze, optimize, measure, compare. TRIGGER — "this is slow", "make it faster", "optimize", "performance", "bottleneck", "too many queries", "high latency", "memory leak", "speed up", "timeout", "N+1", or any request to reduce time, memory, or query count with numbers to prove…
cf-sys-debug
Systematic 4-phase debugging — root cause, hypothesis testing, regression-guarded fix, mandatory bug doc. TRIGGER — non-trivial or recurring bugs: "still broken", "same error again", "came back", flaky/intermittent/race, "used to work, now broken", hard-to-reproduce, works locally but fails in CI, "find the root…
ladybugdb
Expert guide for LadybugDB — an embedded, in-process property graph database using openCypher. Use this skill whenever the user is working with LadybugDB, writing Cypher queries for LadybugDB, using the lbug CLI, importing realladybug in Python, using @ladybugdb/core in Node.js, or building any application with…
reproduce-bug
Reproduce a reported bug in googleapis/mcp-toolbox and decide whether it is real, delivering an evidence-backed verdict: confirmed, already fixed, misconfiguration, client-side, works as intended, not reproducible, or blocked. Use whenever a maintainer asks you to reproduce, verify, confirm, or investigate a bug…
triage-issues
Triage GitHub issues in the googleapis/mcp-toolbox repo: propose the correct labels (type / priority / product / status), check for duplicates, verify a bug has enough info to act on, and draft a triage comment. Use whenever a maintainer asks you to triage, label, categorize, prioritize, or "look at" an issue (or a…