download-guard

Gate external file downloads behind user confirmation via AskUserQuestion.

Updated Jun 3, 2026
One-click install
npx skills add https://github.com/alastor0325/fx-bug-toolkit --skill download-guard
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: download-guard
Source: https://github.com/alastor0325/fx-bug-toolkit/tree/main/skills/download-guard
Command: npx skills add https://github.com/alastor0325/fx-bug-toolkit --skill download-guard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The single approval gate for downloading any external file (bug attachment, media sample, test fixture, profile, screen recording, etc.). Never auto-download — surface a Yes/No AskUserQuestion, and on Yes fetch into the one shared transient folder ~/.fx-bug-toolkit/download-cache/. Invoke this whenever any skill or flow (/triage, /bug-start, the Process-queue drain, …) needs a file pulled to disk.

Core Features & Use Cases

  • Centralized consent gate for external files to prevent untrusted downloads.
  • Shared download cache at ~/.fx-bug-toolkit/download-cache/ with per-file tracking via manifest.jsonl.
  • Easy integration with flows like /triage and /bug-start to ensure files are pulled only after explicit approval.

Quick Start

Ask for user confirmation before downloading any file and store approved files in ~/.fx-bug-toolkit/download-cache/.

Frequently Asked Questions about download-guard

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

FAQPage Schema
How do I require explicit user permission before downloading external files?▼

To require user permission before downloading external files, route all file pulls through a central gate that surfaces a Yes/No confirmation prompt before fetching anything to disk. This prevents unauthorized downloads by enforcing per-file approval.

How does a centralized download cache with manifest tracking work?▼

A centralized download cache stores approved files in a shared directory like ~/.fx-bug-toolkit/download-cache, while a manifest.jsonl file tracks each file individually. This ensures all downloaded attachments and logs are monitored and gated.

Can I gate file downloads in workflows like bug triage without auto-fetching?▼

Yes, you can gate file downloads in workflows like bug triage by integrating a confirmation step that asks the user before pulling any file. This prevents untrusted files from being auto-downloaded during process execution.

What is the best way to prevent unauthorized downloads of bug attachments and logs?▼

The best way to prevent unauthorized downloads is to implement a single approval gate that intercepts all external file requests, such as bug attachments and logs, requiring explicit user consent before saving them to a local cache.

Do I need a specific directory structure to enforce download confirmation steps?▼

Yes, you need a deterministic cache directory, such as ~/.fx-bug-toolkit/download-cache/, to store approved files. This shared transient folder centralizes file storage and enables manifest tracking for all downloaded content.

Why does my workflow automatically download files without asking for confirmation?▼

Workflows auto-download files when they lack a central gate mechanism to pause execution and ask the user. Integrating a user confirmation step ensures workflows stop and request permission before pulling any external file to disk.