better-walkthrough

Name: better-walkthrough
Author: AlanChen4

FSecurity

Use D2 diagrams to walk through code logic step-by-step.

0 votes
0 copies
9 views
Added October 29, 2026

researchgit

Security analysis

F0/100

highUses base64 encoding which could hide malicious payloadsin assets/d2/diagram.js
highConstructs strings from character codes to evade detectionin assets/d2/diagram.js
lowMakes HTTP requests (common but worth tracking)in assets/web/index.js
highContains path traversal sequences that could access files outside intended directoriesin assets/web/index.js
highContains path traversal sequences that could access files outside intended directoriesin assets/web/model.js
highContains path traversal sequences that could access files outside intended directoriesin assets/web/validate.js
criticalUses os.system(), subprocess, or similar Python execution methodsin scripts/cli.py
highUses base64 encoding which could hide malicious payloadsin scripts/cli.py

Pro scans all 17 files and shows the line behind each finding

Scanned October 29, 2026

npx -y skills add AlanChen4/skills --skill better-walkthrough --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of better-walkthrough?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for better-walkthrough

[![Security: F — Skills Directory](https://www.skillsdirectory.com/api/skills/alanchen4-better-walkthrough/badge)](https://www.skillsdirectory.com/skills/alanchen4-better-walkthrough)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro

SKILL.md

---
name: better-walkthrough
license: MIT
description: Use D2 diagrams to walk through code logic step-by-step.
---

# Better walkthrough

Explain one workflow from the current checkout with an interactive D2 diagram. Let the reader advance manually and choose concrete scenarios.

## Investigate

Read [authoring.md](references/authoring.md) to trace the implementation and explain its decisions. Include relevant uncommitted changes. Clarify the workflow's boundaries when needed, and flag behavior the source does not establish.

## Create

Follow [workspaces.md](references/workspaces.md) to create a local `.better-walkthrough/` folder with a self-ignoring `.gitignore`. Keep product code and tracked configuration unchanged.

Use [content-format.md](references/content-format.md) to write content.js and diagram.d2. Reuse the bundled interface.

## Validate

Follow [runtime.md](references/runtime.md) to check or serve the walkthrough. Resolve reported errors.

## Deliver

Return the viewer URL and artifact directory, with validation results and material uncertainties.