installable-tools

Validate installability and uninstallability of Pulp tools and packages from outside the source checkout.

1|Updated Jul 11, 2026

Search Tags:#software development #tool validation #security checks #lifecycle testing #uninstall validation

Ready to run

npx skills add https://github.com/danielraffel/burl --skill installable-tools

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: installable-tools
Source: https://github.com/danielraffel/burl/tree/main/.agents/skills/installable-tools
Command: npx skills add https://github.com/danielraffel/burl --skill installable-tools

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures that tools and packages can be successfully installed and uninstalled from outside a Pulp checkout, providing a full lifecycle test before documentation.

Core Features & Use Cases

Full Lifecycle Validation: Validates installation and uninstallation from the user's perspective.
Outside Checkout Testing: Tests outside of the Pulp source tree to catch issues not visible from within the checkout.
Security and Safety Checks: Ensures that the uninstall process is safe and only removes what it should.

Quick Start

Use the installable-tools skill to validate the installation and uninstallation of a tool named 'trace-processor'.

Frequently Asked Questions about installable-tools

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

FAQPage Schema

How do I validate tool installation and uninstallation from outside a source repository?▼

To validate tool installation and uninstallation from outside a source repository, you need lifecycle testing that executes user-facing commands externally. This ensures packages install and uninstall reliably while verifying data integrity and safe removal.

What is outside checkout testing for software packages?▼

Outside checkout testing for software packages validates installation and uninstallation from outside the source tree. This process catches user-facing command failures and security issues not visible when testing within the repository checkout.

How do I ensure uninstalling a package safely removes only the intended files?▼

To ensure uninstalling a package safely removes only intended files, apply security checks during uninstall validation. This verifies the uninstall process does not compromise data integrity and strictly removes what it should.

Can I test Pulp tool installability before generating documentation?▼

Yes, you can test Pulp tool installability before documentation by running full lifecycle validation. This tests installation and uninstallation from the user's perspective to ensure reliable operation before publishing.

Why does tool installation succeed inside the checkout but fail for end users?▼

Tool installation can succeed inside the checkout but fail for end users because internal source tree dependencies are unavailable externally. Testing outside the source repository validates user-facing commands and catches these hidden issues.

What's the best way to perform full lifecycle validation for command line tools?▼

The best way to perform full lifecycle validation for command line tools is testing installation and uninstallation from an external perspective. This approach verifies user-facing commands, security checks, and data integrity outside the source code.