index-optimization

AdvisoryAudited by Static analysis on Apr 30, 2026.

Overview

No suspicious patterns detected.

Findings (0)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

What this means

The agent could change database indexes during normal use, potentially causing locks, write overhead, or query regressions.

Why it was flagged

The default workflow permits high-impact database index creation or deletion without explicit user approval.

Skill content
不指定:`免确认模式`(默认,无需等待用户确认,可直接执行创建/删除索引) ... `免确认模式`:无需等待用户确认,直接进入下一步执行
Recommendation

Make confirmation required by default, require explicit approval of the target database and exact DDL, and keep no-confirm execution as an explicit opt-in.

ConcernHigh Confidence
ASI08: Cascading Failures
What this means

If pointed at a shared or production database, iterative index changes could affect application performance or availability beyond the immediate task.

Why it was flagged

The environment is only a preference, not a hard guard, while the workflow can iteratively apply database index changes.

Skill content
explain 执行环境(优先 dev/sit) ... 执行索引变更并运行 explain ... 重复执行,直到命中目标索引或达到 3 次重设计上限
Recommendation

Require an explicit non-production target by default; for production, require a maintenance-window confirmation, rollback plan, and separate approval for each DDL change.

What this means

A user may reasonably expect approval prompts while the main workflow authorizes automatic index changes.

Why it was flagged

The interface prompt implies confirmation in both modes, but the main skill instructions make no-confirm execution the default.

Skill content
agents/openai.yaml: "In both modes ... get user confirmation" vs SKILL.md: "免确认模式(默认,无需等待用户确认,可直接执行创建/删除索引)"
Recommendation

Align the agent prompt and SKILL.md so the default approval behavior is unambiguous and conservative.

ConcernMedium Confidence
ASI03: Identity and Privilege Abuse
What this means

The agent may use whatever database credentials are available in the environment, including credentials with production or broad schema-changing rights.

Why it was flagged

The workflow needs database access and likely DDL privileges, but the registry metadata does not declare what credentials or permission scope are required.

Skill content
metadata: "Primary credential: none" / "Required env vars: none"; SKILL.md: "SHOW INDEX" / "getIndexes()" and "执行创建/删除索引"
Recommendation

Declare required database credentials and scopes, prefer read-only access for discovery/explain, and require a separate least-privilege DDL credential only after approval.

What this means

The skill may fail or behave differently on systems without the undeclared local dependency.

Why it was flagged

The helper script depends on ripgrep, while the registry requirements list no required binaries.

Skill content
print("ERROR: `rg` is required but not found in PATH.", file=sys.stderr)
Recommendation

Declare required binaries such as python3 and ripgrep in metadata, or document a fallback path clearly.