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/materialized-viewWrote 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/materialized-view)<a href="https://agentmods.dev/skills/apache/doris-skills/materialized-view"><img src="https://agentmods.dev/badge/skills/apache/doris-skills/materialized-view/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/materialized-view"><img src="https://agentmods.dev/badge/skills/apache/doris-skills/materialized-view.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.00048 | $0.00728 |
| Opus 5.5 | $0.00019 | $0.00291 |
| Sonnet 5.5 | $0.00010 | $0.00146 |
| Haiku 4.5 | $0.00005 | $0.00073 |
Grade A, and why
doris-debug-materialized-view 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Materialized View
Kind comparison
| Kind | Code area | Check | Rewrite mechanism |
|---|---|---|---|
| Sync | MaterializedViewHandler / rollup |
SHOW ALTER TABLE MATERIALIZED VIEW |
Transparent — planner auto-selects |
| Async MTMV | fe/.../mtmv/ |
mv_infos() RefreshState |
CBO-based — EXPLAIN shows if matched |
Causes
| ID | Cause | Evidence | Kind |
|---|---|---|---|
| A | Sync MV build pending/stuck | SHOW ALTER TABLE MATERIALIZED VIEW State≠FINISHED |
Sync |
| B | MTMV refresh failed | mv_infos() RefreshState=FAIL |
Async |
| C | MTMV rewrite miss | EXPLAIN shows no MATERIALIZED_REWRITE | Async |
| D | MTMV data stale | mv_infos() LastRefreshTime old |
Async |
| E | MV not selected by planner | EXPLAIN shows TABLE SCAN not MATERIALIZED | Either |
10 min triage
-- Sync MV status
SHOW ALTER TABLE MATERIALIZED VIEW FROM db;
-- Async MTMV status
SELECT * FROM mv_infos('database'='db') WHERE Name='mv'\G
-- Check rewrite eligibility
EXPLAIN VERBOSE SELECT ...;
-- Force refresh
REFRESH MATERIALIZED VIEW mv;
-- Enable external MV rewrite (for catalog queries)
SET materialized_view_rewrite_enable_contain_external_table = true;
Cause C — MTMV rewrite miss
Common reasons (see fe/.../mtmv/MTMVService.java rewrite matcher):
- Partition misalignment: MV has
partition_sync=falseand query partition doesn't match →ALTER MATERIALIZED VIEW mv SET ("partition_sync" = "true") - Aggregation granularity: MV groups by
(a, b)but query groups by(a)only → MV is not a valid rewrite target - Filter mismatch: MV WHERE clause doesn't cover query WHERE clause → check MV definition
- Session var off:
SET enable_materialized_view_rewrite = true
-- Debug: force the optimizer to log MV matching
SET enable_materialized_view_rewrite_debug_log = true;
EXPLAIN VERBOSE SELECT ...; -- check fe/log/fe.audit.log for MV match details
Cause A — Sync MV stuck
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 · 79 lines · 48 tokens per session scan A 6a9033b26093
doris-debug-materialized-view is a skill published in the GitHub repository apache/doris-skills (47 stars, last pushed 17d ago), licensed Apache-2.0. It adds 48 tokens to every session and 728 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
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…