Jarvis Db Query Doctor 01

Diagnose slow SQL and rewrite queries for safer performance. Use when handling development work that needs repeatable steps, quality gates, and practical out...

Security Scan

An instruction-only workflow for diagnosing and rewriting SQL that does not request credentials, install software, or perform I/O — its requirements and instructions are coherent with its stated purpose.

Purpose & Capability

Name and description claim advisory/analysis work; SKILL.md provides a playbook and output templates rather than automated DB access. No extra binaries, env vars, or config paths are requested, which is appropriate for a guidance/consulting skill.

Instruction Scope

Instructions are limited to producing workflows, checkpoints, quality gates, and concrete recommendations. The playbook does not instruct the agent to read system files, access databases, or transmit data to external endpoints.

Install Mechanism

No install spec and no code files — lowest-risk model (instruction-only). Nothing will be written to disk or downloaded during install.

Credentials

The skill requests no environment variables, credentials, or config paths. This is proportionate for a purely advisory SQL diagnosis/playbook skill.

Persistence & Privilege

always is false and default autonomy is allowed (normal). The skill does not request persistent presence or modify other skill/system configs.

Scan Findings in Context

[no_regex_findings] expected: The static scanner found no matches because this is an instruction-only skill with no code files—this is expected and consistent with the skill being a playbook rather than executable code.

Assessment

This skill is a reusable playbook for diagnosing and rewriting SQL and appears internally consistent. Before using: avoid pasting production credentials, connection strings, or sensitive dumps into prompts; if you want the agent to run queries automatically later, be aware that supplying DB credentials would increase risk and should be limited to short-lived, least-privilege accounts. If you need automatic execution/patching, require an explicit, auditable approval step and review any outputs before applying changes to production.

Deliver a concrete, reusable workflow for development tasks.

Inputs

• Desired outcome and deadline
• Constraints (time, tools, risk tolerance)
• Available artifacts (code, docs, screenshots, logs)

Playbook

1. Define success and failure criteria in measurable terms.
2. Build a smallest-valid execution path before scaling effort.
3. Execute in checkpoints; record evidence at each checkpoint.
4. Apply quality gates before finalizing recommendations.
5. Return implementation-ready outputs and next actions.

Quality Gates

• Evidence-backed claims only.
• Explicit assumptions and tradeoffs.
• Reversible changes preferred for risky operations.
• Clear owner + ETA for each next step.
• Include a fallback if the primary plan fails.

Output Format

• Situation summary (5 lines max)
• Top findings (ranked by impact)
• Action plan (today / this week)
• Risks + mitigations
• Exact checklist or commands where useful

Example prompts

• "Use this skill to turn my messy notes into a production-ready plan."
• "Run this skill and give me a risk-first action sequence with acceptance checks."