원클릭으로 Manus에서 모든 스킬 실행

diagnose-slow-query

스타8

포크2

업데이트2026년 7월 9일 00:00

Diagnose a slow SQL query using iris_sql_analyze (explain, indexUsage, stats) and recommend a fix — never auto-applies one.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

jbrandtmse

jbrandtmse/iris-execute-mcp-v2

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Diagnose Slow Query

Query to diagnose:

<query>

No namespace specified — omit namespace to use the server's configured default on every call below.

Call iris_sql_analyze action 'explain' with query: "<query>" to get the query plan text.
Call iris_sql_analyze action 'indexUsage' with the SAME query to see which maps/indexes the plan actually reads.
Call iris_sql_analyze action 'stats' (optionally with a 'filter' matching this query's statement text) to see cumulative runtime statistics — StatCount, StatTotal, StatAverage, StatRowCount — if this query has run before.
Interpretation checklist:
- Full-scan markers: plan text mentioning "Read master map" scanning the WHOLE table (no index map named) on a large table is a red flag — the query is likely not using an index it should.
- Missing-index reasoning: if 'indexUsage' shows only the master map (no index map) for a WHERE/JOIN/ORDER BY column, an index on that column may help.
- High StatAverage relative to StatRowCount: many statement executions each touching few rows but taking long individually suggests a plan inefficiency, not a data-volume issue.
- StatCount very high: a hot query — even a small per-execution improvement compounds; prioritize it.
Summarize findings and RECOMMEND a fix (e.g. "add an index on Table.Column", or "rewrite the WHERE clause to avoid a function on an indexed column"). Do NOT create the index or modify the class yourself — present the recommendation and let the user decide whether to apply it (e.g. via a class edit + iris_doc_load).

이 저장소의 다른 Skills

같은 저장소

promote-environment-change

jbrandtmse/iris-execute-mcp-v2

Review and promote configuration/code drift from a source IRIS environment to a target using the review-before-write iris_env_diff -> iris_env_promote workflow (scoped diff, plan, an explicit user-selected step allowlist, confirmed execute, re-diff verify). Never acts on onlyInTarget warnings -- never deletes a target-only item, in any action.

2026-07-118

resend-failed-messages

jbrandtmse/iris-execute-mcp-v2

Resend failed Interoperability messages for a config item using the dry-run-first iris_message_resend workflow — preview the match count before executing, then verify the new headers via iris_production_messages. States the duplication hazard and that resend/resendFiltered are governance-default-disabled writes.

2026-07-098

audit-security-posture

jbrandtmse/iris-execute-mcp-v2

Audit the IRIS instance's security posture: users (default passwords, %All holders), roles, service authentication settings, SSL/TLS configs, and instance auditing status.

2026-07-098

check-system-health

jbrandtmse/iris-execute-mcp-v2

Run a full IRIS instance health check (iris_health_check) and interpret every non-ok finding, naming the fixing tool for each one.

2026-07-098

deploy-and-test-class

jbrandtmse/iris-execute-mcp-v2

Deploy an ObjectScript class or package to IRIS (iris_doc_load, glob-path form), fix compile errors, then run its unit tests (iris_execute_tests) with a total-count check.

2026-07-098

objectscript-review

jbrandtmse/iris-execute-mcp-v2

A concise (<=300 word) pre-write checklist distilling the project's ObjectScript conventions ($$$ macros, Quit-in-try/catch, %OnNew/initvalue, no-underscore names, storage sections untouchable, deploy/test discipline).

2026-07-098

name	diagnose-slow-query
description	Diagnose a slow SQL query using iris_sql_analyze (explain, indexUsage, stats) and recommend a fix — never auto-applies one.

Diagnose Slow Query

Query to diagnose:

<query>

No namespace specified — omit namespace to use the server's configured default on every call below.

Call iris_sql_analyze action 'explain' with query: "<query>" to get the query plan text.
Call iris_sql_analyze action 'indexUsage' with the SAME query to see which maps/indexes the plan actually reads.
Call iris_sql_analyze action 'stats' (optionally with a 'filter' matching this query's statement text) to see cumulative runtime statistics — StatCount, StatTotal, StatAverage, StatRowCount — if this query has run before.
Interpretation checklist:
- Full-scan markers: plan text mentioning "Read master map" scanning the WHOLE table (no index map named) on a large table is a red flag — the query is likely not using an index it should.
- Missing-index reasoning: if 'indexUsage' shows only the master map (no index map) for a WHERE/JOIN/ORDER BY column, an index on that column may help.
- High StatAverage relative to StatRowCount: many statement executions each touching few rows but taking long individually suggests a plan inefficiency, not a data-volume issue.
- StatCount very high: a hot query — even a small per-execution improvement compounds; prioritize it.
Summarize findings and RECOMMEND a fix (e.g. "add an index on Table.Column", or "rewrite the WHERE clause to avoid a function on an indexed column"). Do NOT create the index or modify the class yourself — present the recommendation and let the user decide whether to apply it (e.g. via a class edit + iris_doc_load).