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/resource-isolationWrote 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/resource-isolation)<a href="https://agentmods.dev/skills/apache/doris-skills/resource-isolation"><img src="https://agentmods.dev/badge/skills/apache/doris-skills/resource-isolation/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/resource-isolation"><img src="https://agentmods.dev/badge/skills/apache/doris-skills/resource-isolation.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.00043 | $0.00887 |
| Opus 5.5 | $0.00017 | $0.00355 |
| Sonnet 5.5 | $0.00009 | $0.00177 |
| Haiku 4.5 | $0.00004 | $0.00089 |
Grade A, and why
doris-debug-resource-isolation scanned grade A with 0 findings 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resource Isolation (Workload Group)
Causes
| ID | Cause | Evidence | Source anchor |
|---|---|---|---|
| A | Queue starvation | Queries queued in SHOW WORKLOAD GROUPS; QueueTime growing |
WorkloadGroupMgr.java |
| B | CPU oversubscription | One WG consuming >90% CPU despite limits | CgroupCpuCtl.cpp |
| C | Memory leak across groups | MemTracker shows one WG exceeding memory_limit |
WorkloadGroupMemMgr.cpp |
| D | Tag routing wrong | Query hits wrong BE set; ResourceTag mismatch | ResourceTag.java, Tag.java |
| E | WG not active / cgroup missing | CREATE WORKLOAD GROUP had no effect |
WorkloadGroupMgr.cpp cgroup init |
10 min triage
-- Workload group status
SHOW WORKLOAD GROUPS\G
-- Check columns: Id, Name, ActiveQueries, QueuedQueries, CpuShares, MemoryLimit
-- Which WG is my query in?
SELECT * FROM information_schema.workload_group_resource_usage;
-- Workload policies (routing rules)
SHOW WORKLOAD POLICY\G
# BE cgroup inspection
cat /sys/fs/cgroup/cpu/doris/<wg_id>/cpu.shares
cat /sys/fs/cgroup/memory/doris/<wg_id>/memory.limit_in_bytes
./scripts/doris-debug be-metrics --be http://$BE:8040 --grep "workload_group"
Cause A — Queue starvation
-- See who's queued
SHOW WORKLOAD GROUPS\G
-- Raise queue concurrency
ALTER WORKLOAD GROUP etl_wg SET (
"max_concurrency" = "8",
"max_queue_size" = "100",
"queue_timeout" = "300"
);
Check be/src/pipeline/task_scheduler.cpp — the pipeline scheduler respects cgroup shares; if a high-share WG starves a low-share one, the low-share WG's queue backs up.
Cause B — CPU oversubscription
-- Create a hard CPU cap
ALTER WORKLOAD GROUP report_wg SET (
"cpu_share" = "1024",
"cpu_hard_limit" = "200%" -- 2 cores max
);
-- Force query into specific WG
SET workload_group = 'report_wg';
cgroup v1 vs v2 behavior differs. Confirm which is active on BE hosts:
mount | grep cgroup
ls /sys/fs/cgroup/cpu/doris/ # cgroup v1
ls /sys/fs/cgroup/doris/ # cgroup v2
What ships with it
1 file 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 · 112 lines · 43 tokens per session scan A 524439745037
doris-debug-resource-isolation is a skill published in the GitHub repository apache/doris-skills (47 stars, last pushed 18d ago), licensed Apache-2.0. It adds 43 tokens to every session and 887 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
sivtr-memory
Retrieve shared local work memory: terminal activity, AI conversation history, prior decisions, validation evidence, debugging trails, recaps, and handoff context. Use before asking the user to repeat local work context.
cf-learn
Extract educational notes for the human from the conversation (unlike /cf-remember, which stores project memory for AI recall). TRIGGER — substantial new technical knowledge, a debugging breakthrough, an architecture decision explained, or a complex explanation worth keeping; the user says "explain what we learned"…
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-remember
Save project knowledge to docs/memory for AI recall (unlike /cf-learn, which writes educational notes for the human). TRIGGER — "remember this", "save this to memory", "document what we did", "capture this decision", "write this down", "note this", "record this convention"; after a non-obvious bug fix → bugs/, an…
cf-scan
Scan the project and populate memory (architecture, conventions, stack, features). Triggers: "scan the project", "scan the codebase", "bootstrap memory", "populate memory", "analyze the project". Token-heavy — always warn before proceeding.
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…