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
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add apache/doris-skills --skill deploymentgit clone --depth 1 https://github.com/apache/doris-skillsWrote 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/deployment)<a href="https://agentmods.dev/skills/apache/doris-skills/deployment"><img src="https://agentmods.dev/badge/skills/apache/doris-skills/deployment/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/deployment"><img src="https://agentmods.dev/badge/skills/apache/doris-skills/deployment.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.00036 | $0.00839 |
| Opus 5.5 | $0.00014 | $0.00336 |
| Sonnet 5.5 | $0.00007 | $0.00168 |
| Haiku 4.5 | $0.00004 | $0.00084 |
Grade A, and why
doris-debug-deployment 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/bootstrap" How it starts
The opening of the file, as written. The whole thing — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deployment & Startup
Causes
| ID | Cause | Evidence | Source anchor |
|---|---|---|---|
| A | Port conflict | BE/FE fail to bind; Address already in use |
brpc/server.cpp, doris_main.cpp |
| B | priority_networks misconfig |
brpc connection refused / wrong interface | config.cpp |
| C | meta_dir / storage_root_path not writable | Permission denied / No such file at startup |
olap/olap_meta.cpp |
| D | FE metadata corruption | FE fails to start after crash; meta/image.* errors |
Image.java, BDBJEJournal.java |
| E | Mixed version cluster | Protocol mismatch in thrift/brpc between FE-BE | be/src/agent/, heartbeat |
| F | DNS / hostname resolution | UnknownHostException, BE heartbeat to wrong address |
Env.java frontend host check |
10 min triage
# FE status
curl -s "http://$FE:8030/api/bootstrap"
curl -s "http://$FE:8030/api/health"
# BE status
curl -s "http://$BE:8040/api/health"
# Port check
ss -tlnp | grep -E "8030|8040|8060|9030"
-- Cluster membership
SHOW FRONTENDS\G
SHOW BACKENDS\G
Cause A — Port conflict
Default ports (from fe/conf/fe.conf and be/conf/be.conf):
| Service | Port | Config key |
|---|---|---|
| FE HTTP | 8030 | http_port |
| BE HTTP | 8040 | webserver_port |
| BE brpc | 8060 | brpc_port |
| FE MySQL | 9030 | query_port |
| FE Edit log | 9010 | edit_log_port |
# Kill stale process on target port
fuser -k 8060/tcp # BE brpc
# Then restart BE
Cause B — priority_networks
The most common cause of "BE shows Alive=true but brpc fails." priority_networks tells BE which network interface to bind brpc to.
# be.conf — match ONE subnet exactly
priority_networks = 10.0.0.0/24
Check what interface BE actually bound:
curl -s "http://$BE:8040/api/health" | grep -o '"ip":"[^"]*"'
Validation: the IP in SHOW BACKENDS must be reachable from every FE and every other BE on port 8060.
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 · 99 lines · 36 tokens per session scan A e49d19a5b872
doris-debug-deployment is a skill published in the GitHub repository apache/doris-skills (47 stars, last pushed 17d ago), licensed Apache-2.0. It adds 36 tokens to every session and 839 once invoked, about $0.0001 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
yida-data-management
A tool for querying, adding, and updating Yida form records, child tables, process records, and task-center data. It keeps ordinary forms and approval workflows on their separate data interfaces.
azure-data-api-builder
Expert knowledge for Azure Data Api Builder development including troubleshooting, best practices, decision making, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when exposing DB objects via REST/GraphQL, tuning paging/timeouts, securing auth/RLS, or deploying DAB to…
supabase
Skill "supabase" from dhaupin/vant, covering supabase, when to use, what to do, 1. connect and supabase-js.
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…