bash-tools

Enforce safe Bash and file-tool usage in shell automation.

13|Updated Apr 2, 2025
One-click install
npx skills add https://github.com/kettleofketchup/DraftForge --skill bash-tools
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bash-tools
Source: https://github.com/kettleofketchup/DraftForge/tree/main/.claude/skills/bash-tools
Command: npx skills add https://github.com/kettleofketchup/DraftForge --skill bash-tools

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill codifies best practices for using Bash and file operation tools, preventing unsafe workarounds that bypass permission controls.

Core Features & Use Cases

  • Enforces using Write, Edit, and Read tools for file creation, modification, and reading.
  • Guides safe shell automation to avoid common circumvention patterns in scripts.
  • Provides a clear decision framework for when to use Bash vs specialized file tools in automation tasks.

Quick Start

Describe your task and specify the target file and content. For example, to safely write a config file at /etc/app.conf with specific content, instruct the assistant to use the Write tool.

Frequently Asked Questions about bash-tools

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

FAQPage Schema
When should I use Bash instead of Write or Edit tools for file operations?

Use Bash for shell automation tasks like scripts and deployment pipelines, but use Write, Edit, and Read tools for file creation, modification, and reading to enforce safe automation and avoid bypassing permission controls.

How do I safely write a config file during shell automation?

To safely write a config file during shell automation, describe your task, specify the target file path and content, and instruct the assistant to use the Write tool instead of unsafe shell shortcuts.

What are common unsafe Bash shortcuts for file modification?

Unsafe Bash shortcuts are shell scripting patterns that bypass permission controls during file operations, which can be prevented by using dedicated Write, Edit, and Read tools for those specific tasks.

Does this approach work for deployment pipelines and dev setups?

Yes, this safe shell automation approach applies to deployment pipelines and dev setups, guiding when to use Bash versus specialized file operation tools to prevent unsafe circumvention patterns.

Why avoid using Bash for file reading and editing?

Avoid using Bash for file reading and editing to prevent unsafe workarounds that bypass permission controls, ensuring safe automation by using dedicated Read and Edit tools instead.