Skip to content
Diagnosis · Writing

tachi-threat-reporting

Domain knowledge for narrative threat report generation — executive summary structure, architecture overview patterns, per-category…

Checking the letterforms and the sentence

Works with
ClaudeChatGPTGeminiClaude CodeCodexCursorCopilotGemini CLI
Setup
Upload one file
About a minute in Claude. One command in coding tools.
Contains
Instructions only
Text files — no scripts or programs.
Maintained
Last change 28 Sept 2026
On the repository’s main branch.

What it does

Narrative threat report domain knowledge extracted from the tachi threat-report agent. This skill provides the templates, construction rules, and reference examples that the threat-report agent uses to transform structured threat model output into comprehensive narrative reports with Mermaid attack trees.

What it can touch

  • No script files in its folder

    Its folder holds text, not programs. It changes how your AI works; it does not bring code of its own.

    How we know

    Listed the 4 files in the skill’s folder on GitHub; none is a script or program.

  • 1 smaller thing worth knowing

    Tells your AI to ignore its other instructions. Usually legitimate — listed so nothing is hidden.

    How we know

    Tells your AI to ignore its other instructions — references/attack-tree-examples.md line 77. Read 2026-10-05, commit 63438d7.

    references/attack-tree-examples.md, line 77 ↗
  • No serious risk pattern found

    Launch7’s automated check read all 4 text files in this skill and matched none of its serious risk patterns. This is not a guarantee: a check like this can miss new or disguised tricks, and the author can change the files after the check.

    How we know

    Read 2026-10-05, commit 63438d7 by pipeline/trust/analyze.py — 40+ patterns for hidden text, prompt injection, downloads that run, credential access and more. It reads; it never runs the skill.

  • Recently maintained

    Its repository has had changes recently.

    How we know

    Last push to davidmatousek/tachi: 2026-09-28 (7 days before the scan).

Read automatically from the skill’s own files on GitHub on 5 Oct 2026. Launch7 does not run or manually review skills: this lists what the check saw, and nothing here means “safe”. How we check

Add it to your AI

Supported. Upload it once in Claude’s settings. Works on every plan, including Free.

  1. Built in your browser from the SKILL.md on GitHub — nothing passes through Launch7.

  2. In Claude, open Customize → Skills, press +, then Create skill → Upload a skill, and choose the .zip.

  3. Make sure code execution is switched on (Settings → Capabilities). Skills need it.

  4. Start a new chat and ask for the job in your own words — Claude picks the skill up when it fits.

How Claude does this: support.claude.com · checked 28 Sep 2026 · “Supported” means documented by the vendor; Launch7 has not run it end to end

More from davidmatousek

All from this publisher →
  • ~aod-build

    Generate standardized checkpoint reports for multi-phase implementation projects.

    davidmatousekIncludes 3 scripts
  • ~aod-deliver

    Structured delivery retrospective for the AOD Lifecycle's Deliver stage.

    davidmatousekRuns terminal commands
  • ~aod-run

    Full lifecycle orchestrator that chains all 6 AOD stages (Discover, Define, Plan, Build, Deliver, Document) with disk-persisted state for session…

    davidmatousekReview before installing
  • code-execution-helper

    Guide for using code execution capabilities to perform parallel batch processing, conditional filtering, and data aggregation.

    davidmatousekInstructions only
  • tachi-control-analysis

    Domain knowledge for compensating controls analysis — control category definitions with detection patterns, evidence criteria with…

    davidmatousekInstructions only