skills.rest
theLightArchitect
theLightArchitectCOMMUNITY
Explore all skills by this author →
GitHub

initialize

Initialize CAPPY case directories, extract log bundles, and generate inv_context.json.

Updated Aug 27, 2026
Search Tags:#evidence#initialize#case-setup#cappy#envlog#inv_context
One-click install
npx skills add https://github.com/theLightArchitect/cappy-toolkit --skill initialize-thelightarchitect
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: initialize
Source: https://github.com/theLightArchitect/cappy-toolkit/tree/main/skills/initialize
Command: npx skills add https://github.com/theLightArchitect/cappy-toolkit --skill initialize-thelightarchitect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

TAC engineers need a reliable, repeatable way to set up a new investigation case, extract customer‑provided log bundles, detect the product environment, and catalog all evidence before any analysis can begin.

Core Features & Use Cases

  • Automated case directory creation with standardized subfolders for evidence, extracted data, analysis, and deliverables.
  • Bundle extraction and file type detection, including automatic parsing of env.log to identify product, version, and build.
  • Interactive evidence cataloguing, prompting the user to classify and select files for analysis, and generating a comprehensive inv_context.json that drives all subsequent CAPPY phases.

Quick Start

Run the initialize skill on case SF-03896040 with the evidence bundle located in the evidence folder.

Frequently Asked Questions about initialize

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up a case directory and extract log bundles for investigation analysis?▼

To set up a case directory, the skill automates extraction of log bundles and creates standardized subfolders for evidence, data, analysis, and deliverables to prepare your investigation environment.

How does parsing env.log detect product version and build details?▼

Parsing env.log automatically identifies product details, extracting version and build information directly from the log bundle to populate the investigation context.

What is the best way to catalog evidence files before starting TAC analysis?▼

The best way to catalog evidence is interactive file classification, which prompts you to select files for analysis and generates a structured inv_context.json file to drive subsequent phases.

Can I use this to detect product versions from customer-provided logs?▼

Yes, you can detect product versions by parsing the env.log file included in customer-provided log bundles during the initial case setup phase.

Do I need a specific file structure before initializing a CAPPY case?▼

No specific file structure is needed beforehand; the skill creates the required subdirectories automatically when you run it on a case with an evidence folder.

Why does my investigation workflow require an inv_context.json file?▼

An inv_context.json file is required because it stores the catalogued evidence and parsed product environment details, serving as the central configuration that drives all subsequent CAPPY analysis phases.

Related Skills

Explore More Software Engineering Skills→
lawless-mlawless-m
6

Logging

Create UTF-8 thread-safe daily rotating log files for C# RocsMiddleware services.

Community
Basic
BarisSozenBarisSozen
1

error-logger

Generate structured JSON logs with correlation IDs for distributed services.

Community
Basic
ben-mad-jlpben-mad-jlp

kodex-fix-incorrect

Validate Kodex topic claims against code and update inaccuracies.

Community
Intermediate
ray-manalotoray-manaloto
1

mise-migrate-from-nvm

Migrate Node version management from nvm to mise while preserving pinned versions.

Official
Intermediate