Jarvis Incident Timeline Writer 01

Create precise incident timelines from logs and notes. Use when handling development work that needs repeatable steps, quality gates, and practical outputs.

Security Scan

Instruction-only playbook that matches its stated purpose (creating incident timelines); it requests no credentials, installs nothing, and its runtime instructions stay on-task.

Purpose & Capability

The name/description (incident timelines, repeatable steps, quality gates) align closely with the SKILL.md playbook and output format. Nothing requested (no env vars, no binaries) is out of scope for this purpose.

Instruction Scope

SKILL.md contains a narrow, well-scoped checklist and output template. It does not instruct the agent to read system files, access credentials, call external endpoints, or collect unrelated data; inputs are limited to user-provided artifacts and constraints.

Install Mechanism

No install spec and no code files (lowest technical risk). However, the skill's source/homepage are unknown—while this doesn't raise a technical risk here (no downloads/execution), provenance is unknown and users may want to prefer skills with clear authorship.

Credentials

No environment variables, credentials, or config paths are required. The skill does not request sensitive tokens or system access.

Persistence & Privilege

always is false and the skill is user-invocable; it does not request elevated or persistent privileges and provides no instructions to modify other skills or global agent settings.

Assessment

This skill is a low-risk, instruction-only playbook that appears coherent with its stated purpose. Before using it with real data, avoid pasting secrets, PII, or raw logs containing credentials—test with sanitized examples first. If provenance matters to you, prefer skills with an identified author, homepage, or repo; because the source is unknown you may want to review outputs carefully and limit autonomous invocation when handling sensitive incidents.

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