Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

scope-investigation-report

Étoiles53

Forks12

Mis à jour27 mai 2026 à 03:24

Use when scope-investigate completes an investigation and needs a facts-only analyst summary, evidence timeline, query appendix, investigation gaps, and optional saved investigation artifact.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

tayontech

tayontech/SCOPE

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Analystes en sécurité de l'informationProfessions informatiques et mathématiques·SOC 15-1212

SKILL.md

readonly

name	scope-investigation-report
description	Use when scope-investigate completes an investigation and needs a facts-only analyst summary, evidence timeline, query appendix, investigation gaps, and optional saved investigation artifact.

SCOPE Investigation Report

Use this skill after the analyst chooses done in scope-investigate, before the save prompt and before durable knowledge updates.

The top-level investigation agent provides:

MODE: INVESTIGATION, RUN, or INTEL
active_hypothesis
investigation_context
investigation_findings
KNOWLEDGE_CONTEXT
skipped steps and analyst pivots
saved artifact path when persistence was approved

Rules

Present facts only. Do not assign severity, risk, suspicion, compromise, maliciousness, or confidence.
Do not infer events that no query returned.
Do not hide skipped steps or telemetry gaps.
Prefix every follow-up option with Consider:.
Cite KNOWLEDGE_CONTEXT entries only when they influenced reasoning.
Use UTC timestamps.
Deduplicate events that appeared in overlapping query windows.

Required Sections

Return this structure:

## Investigation Summary

[2-5 sentences. State what the data showed, what the data did not show, and what remains unknown.]

## Evidence Timeline

| Timestamp (UTC) | Event | Principal | Source IP | Details |
|-----------------|-------|-----------|-----------|---------|

## Key Indicators Found

- [Observable fact]

## Investigation Gaps

- [Skipped step, missing telemetry, or unanswered question]

## Environment Context Used

| Entity | Knowledge Entry | How It Informed Investigation |
|--------|-----------------|-------------------------------|

## Suggested Follow-Up Actions

- Consider: [optional next step]

Omit Environment Context Used when no knowledge entry influenced the investigation.

Saved Artifact Appendix

When the analyst approves save, append:

## Queries Run

| Step | Purpose | SPL | Result Summary |
|------|---------|-----|----------------|

## Skipped Or Pivoted Steps

| Step | Status | Reason |
|------|--------|--------|

Output Contract

Return:

INVESTIGATION_REPORT
  status: complete|skipped|error
  sections:
    - Investigation Summary
    - Evidence Timeline
    - Key Indicators Found
    - Investigation Gaps
    - Suggested Follow-Up Actions
  save_ready: true|false
  knowledge_update_candidates:
    - ...

Plus depuis ce dépôt

même dépôt

scope-attack-path-analysis

tayontech/SCOPE

Use when constructing SCOPE attack candidate chains from audit artifacts and rejecting facts that do not form attacker progressions.

2026-05-2753

scope-detection-format

tayontech/SCOPE

Use when formatting SCOPE controls detection candidates into detections.md, detections.json, dashboard-readable SPL sections, or controls-schema detection records.

2026-05-2753

scope-evidence-logging

tayontech/SCOPE

Use when attaching schema-valid SCOPE evidence handles to attack candidates, hops, observations, assumptions, and caveats.

2026-05-2753

scope-exploit-playbook

tayontech/SCOPE

Use when scope-exploit has operator-approved attack paths and needs to generate the narrative red team playbook, execution steps, persistence, post-exploitation, and IAM policy JSON without detection or SOC guidance.

2026-05-2753

scope-knowledge-load

tayontech/SCOPE

Use when a SCOPE top-level agent starts a run and needs bounded environment knowledge, durable observations, reasoning notes, coverage gaps, and Splunk patterns before planning.

2026-05-2753

scope-knowledge-update

tayontech/SCOPE

Use after SCOPE evidence review, final disposition, or operator-approved save to update durable environment knowledge, observations, coverage gaps, or proposed reasoning-note improvements.

2026-05-2753

SCOPE Investigation Report

Use this skill after the analyst chooses done in scope-investigate, before the save prompt and before durable knowledge updates.

The top-level investigation agent provides:

MODE: INVESTIGATION, RUN, or INTEL

active_hypothesis

investigation_context

investigation_findings

KNOWLEDGE_CONTEXT

skipped steps and analyst pivots

saved artifact path when persistence was approved

Rules

Present facts only. Do not assign severity, risk, suspicion, compromise, maliciousness, or confidence.

Do not infer events that no query returned.

Do not hide skipped steps or telemetry gaps.

Prefix every follow-up option with Consider:.

Cite KNOWLEDGE_CONTEXT entries only when they influenced reasoning.

Use UTC timestamps.

Deduplicate events that appeared in overlapping query windows.

Required Sections

Return this structure:

## Investigation Summary [2-5 sentences. State what the data showed, what the data did not show, and what remains unknown.] ## Evidence Timeline | Timestamp (UTC) | Event | Principal | Source IP | Details | |-----------------|-------|-----------|-----------|---------| ## Key Indicators Found - [Observable fact] ## Investigation Gaps - [Skipped step, missing telemetry, or unanswered question] ## Environment Context Used | Entity | Knowledge Entry | How It Informed Investigation | |--------|-----------------|-------------------------------| ## Suggested Follow-Up Actions - Consider: [optional next step]

Omit Environment Context Used when no knowledge entry influenced the investigation.

Saved Artifact Appendix

When the analyst approves save, append:

## Queries Run | Step | Purpose | SPL | Result Summary | |------|---------|-----|----------------| ## Skipped Or Pivoted Steps | Step | Status | Reason | |------|--------|--------|

Output Contract

Return:

INVESTIGATION_REPORT status: complete|skipped|error sections: - Investigation Summary - Evidence Timeline - Key Indicators Found - Investigation Gaps - Suggested Follow-Up Actions save_ready: true|false knowledge_update_candidates: - ...