Jarvis Migration Risk Radar 01

Assess migration risk and design staged rollouts. Use when handling development work that needs repeatable steps, quality gates, and practical outputs.

Security Scan

This is an instruction-only skill that describes a risk-focused migration/playbook workflow; its requirements and instructions are coherent with its stated purpose and it does not request additional access or install anything.

Purpose & Capability

The name, description, and SKILL.md all describe creating repeatable migration/rollout playbooks. There are no requested binaries, env vars, or installs that would be inconsistent with that purpose.

Instruction Scope

The runtime instructions are limited to process steps, quality gates, and output format. They do not direct the agent to read unrelated files, access credentials, or call external endpoints.

Install Mechanism

No install spec or code files are provided (instruction-only), so nothing is written to disk or fetched at install time.

Credentials

The skill declares no environment variables, credentials, or config paths — consistent with an advice/playbook skill.

Persistence & Privilege

always is false and disable-model-invocation is false (normal). The skill does not request elevated or persistent privileges or changes to other skills.

Assessment

This skill is low-risk and appears internally consistent, but note the published source/homepage are unknown. Before installing or using it: (1) review the SKILL.md content yourself to confirm the proposed workflow matches your policies; (2) do not provide secrets, credentials, or sensitive system artifacts as inputs—this skill is intended to produce plans and checklists, not to perform changes; (3) test its recommendations manually in a safe environment before executing any commands it suggests; and (4) if you need higher trust, ask the publisher for provenance or a homepage/source repository.

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."