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 agentmods add skills/apache/doris-skills/doris-profile-readernpx skills add apache/doris-skills --skill doris-profile-readergit clone --depth 1 https://github.com/apache/doris-skillsWhat 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 | $0.00067 | $0.02660 |
| Opus 5 | $0.00034 | $0.01330 |
| Sonnet 5 | $0.00013 | $0.00532 |
| Haiku 4.5 | $0.00007 | $0.00266 |
Grade A, and why
doris-profile-reader 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 3d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Doris Profile Reader
Purpose
Use this skill to identify the real bottleneck in an Apache Doris query runtime profile. The core rule is to separate active work from dependency, queue, and backpressure waits before naming an operator as expensive. When the plan contains joins, also separate the immediate runtime bottleneck from the plan-shape cause, especially bad join order and runtime-filter direction.
Required Reading Order
- Read
references/reading-workflow.mdfor the analysis workflow and output contract. - Read
references/counter-semantics.mdfor counter meaning and priority, especially wait counters. - Read
references/operator-guide.mdfor the relevant operator family. - Read
references/failure-patterns.mdwhen the profile shows skew, bad join/distribution choices, weak pruning, sort/spill/resource pressure, external scans/catalogs, lifecycle waits, or when the user expects an issue-level root cause from profile-only evidence. - Read
references/join-order-diagnosis.mdwhen the profile or plan has multiple joins, a large hash/nested-loop build, a large scan that might have been pruned by a join, paired fast/slow plans, hints/reordered SQL, or a request about join shape/reorder. - Read
references/runtime-filters.mdwhen a profile or plan includesRuntimeFilterInfo,RF... <-,RF... ->,JRFs,WaitForRuntimeFilter, orAcquireRuntimeFilter. - Use
references/source-profile-inventory.mdas the source-backed operator/counter inventory. If a counter or operator is not in the narrative docs, do not ignore it; look it up in this inventory and classify it by the rules incounter-semantics.md. - Read
references/solution-playbook.mdwhen the user asks for a fix, workaround, mitigation, tuning, SQL rewrite, or when the requested output schema includes solution fields. - Read
references/known-issues-solutions.mdafter the root-cause layer is established and a solution is requested. Use it as historical evidence, not as a replacement for profile diagnosis.
What ships with it
11 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.
- agents/openai.yaml 1.1 KB
- references/counter-semantics.md 18 KB
- references/failure-patterns.md 21 KB
- references/join-order-diagnosis.md 14 KB
- references/known-issues-solutions.md 19 KB
- references/operator-guide.md 21 KB
- references/reading-workflow.md 19 KB
- references/runtime-filters.md 7.6 KB
- references/solution-playbook.md 11 KB
- references/source-profile-inventory.md 65 KB
- scripts/extract_source_profile_inventory.py 5.9 KB runs code
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.
- 3d ago First seen · 74 lines · 67 tokens per session scan A 80e7a9ceff90
doris-profile-reader is a skill published in the GitHub repository apache/doris-skills (37 stars, last pushed 13d ago), licensed Apache-2.0. It adds 67 tokens to every session and 2,660 once invoked, about $0.0003 per session on Opus 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
mongodb-natural-language-querying
Generate read-only MongoDB queries (find) or aggregation pipelines using natural language, with collection schema context and sample documents. Use this skill whenever the user asks to write, create, or generate MongoDB queries, wants to filter/query/aggregate data in MongoDB, asks "how do I query...", needs help with…
yida-data-management
宜搭数据管理。表单实例/子表/流程实例/任务中心的查询、新增、更新。表单走 /v1/form/,流程走 /v1/process/,不能混用。.
yida-business-rule
宜搭表单业务关联规则与高级函数配置。用于在表单设置中配置业务关联规则,或使用 INSERT、UPDATE、DELETE、UPSERT 高级函数实现跨表增删改。适用于需要表单间数据联动的场景。.
yida-aggregate-table
宜搭聚合表(virtualView)管理。用于列出、创建空聚合表、读取/预览设计配置、保存草稿、发布配置和查询构建状态;严格区分 stash 与 live revision,并在写入前校验固定前端已确认的六数组契约。.
yida-db-seq-fix
PostgreSQL Sequence 自动修复工具。检测并修复宜搭环境检测自动建表时 Sequence 起始值问题,避免主键冲突。当用户提到"Sequence"、"主键冲突"、"自增ID错误"、"db-seq-fix"时触发。.
mongodb-connection
Optimize MongoDB client connection configuration (pools, timeouts, patterns) for any supported driver language. Use this skill when working/updating/reviewing on functions that instantiate or configure a MongoDB client (eg, when calling connect()), configuring connection pools, troubleshooting connection errors…