Analyzing Windows Shellbag Artifacts
Structure Windows Shellbag forensic findings into folder, USB, and network-share access reports during incident response or malware triage.
Overview
analyzing-windows-shellbag-artifacts is an agent skill for the Ship phase that structures Windows Shellbag forensic results into folder, USB, and network-share access reports.
Install
npx skills add https://github.com/mukul975/anthropic-cybersecurity-skills --skill analyzing-windows-shellbag-artifactsWhat is this skill?
- Shellbag analysis report template with case metadata fields
- Folder access summary table (path, shell type, created, modified)
- USB device access timeline section
- Network share UNC path access section
- Apache License 2.0 reference material in bundled documentation
- 3 report sections: folder access, USB device access, network share access
Adoption & trust: 1 installs on skills.sh; 14.9k GitHub stars; 3/3 security scanners passed (skills.sh audits); trending (+100% hot-view momentum).
What problem does it solve?
You parsed Shellbag artifacts but lack a consistent case report layout for folder, USB, and UNC access timelines stakeholders can review.
Who is it for?
Solo security practitioners or indie SaaS operators doing light endpoint forensics after suspected compromise or insider-risk review.
Skip if: Greenfield app feature development, cloud-only threats with no Windows endpoint artifacts, or teams without forensic extraction already performed.
When should I use this skill?
When analyzing or summarizing Windows Shellbag artifacts for a security case after extraction.
What do I get? / Deliverables
You deliver a filled Shellbag analysis report with case info and access tables suitable for security review or incident documentation.
- Shellbag analysis report with access tables
- Documented USB and UNC access timelines
Recommended Skills
Journey fit
Shellbag analysis is a defensive security and integrity check activity before or after release when investigating endpoints, not feature implementation. The skill centers artifact examination and reporting templates for user activity on Windows—classic security review and forensic workflow.
How it compares
Use as a DFIR report scaffold for Shellbags, not as a generic debugging skill for application stack traces.
Common Questions / FAQ
Who is analyzing-windows-shellbag-artifacts for?
Builders and consultants investigating Windows endpoints who need structured Shellbag reporting while working with Claude Code or similar agents.
When should I use analyzing-windows-shellbag-artifacts?
During Ship security reviews or Operate incident response after Shellbag parsing, when you must document folder, USB, and share access for a case file.
Is analyzing-windows-shellbag-artifacts safe to install?
Review the Security Audits panel on this Prism page; forensic skills may reference case data—never pipe live victim PII into untrusted environments without policy review.
SKILL.md
READMESKILL.md - Analyzing Windows Shellbag Artifacts
# Shellbag Analysis Report ## Case Info | Field | Value | |-------|-------| | Case Number | | | Examiner | | ## Folder Access Summary | Path | Shell Type | Created | Modified | |------|-----------|---------|----------| | | | | | ## USB Device Access | Path | First Access | Last Access | |------|-------------|------------| | | | | ## Network Share Access | UNC Path | Access Time | |----------|------------| | | | Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to the Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by the Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of