kits

Validate, inspect, and apply local Pulp package manifests.

1|Updated Jul 11, 2026

Search Tags:#pulp #package manifest #kit management #local artifact integration #project dependency management

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

The kits skill addresses the complexities of managing and integrating Pulp package manifests, allowing users to safely apply and remove Pulp-native artifacts while providing clear and actionable guidance for their projects.

Core Features & Use Cases

Package Manifest Management: Securely inspect, validate, and manage local Pulp package manifests.
Artifact Application and Removal: Apply local or external Pulp-native artifacts to a project or remove them with confidence.
Kit Scaffolding: Scaffold local Pulp package manifests efficiently for various kit types (source/UI/template).
Use Case: Suppose you have a complex project with multiple dependent packages and need to ensure that only curated dependencies are integrated. The kits skill enables you to validate package manifests against strict criteria, reducing integration risks and ensuring a smooth development process.

Quick Start

Use the kits skill to validate a Pulp kit with 'build/pulp kit validate path/to/kit'.

Frequently Asked Questions about kits

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

FAQPage Schema

How do I validate a local Pulp package manifest before integrating dependencies?▼

To validate a local Pulp package manifest, you can use the command 'build/pulp kit validate path/to/kit'. This inspects the manifest against defined schema requirements to ensure curated dependencies are safely structured for project integration.

What is the best way to manage Pulp-native artifacts and remove them safely from a project?▼

Managing Pulp-native artifacts involves inspecting structured metadata and generating automated plans for conditional execution. This allows you to apply or remove local and external artifacts confidently without risking unintended project transformations.

How do I scaffold a Pulp package manifest efficiently for different kit types?▼

You can scaffold local Pulp package manifests efficiently for various kit types such as source, UI, or template kits. This process structures your initial metadata to streamline subsequent artifact application and dependency management.

Does kit management support automated plan generation for secure project transformation?▼

Yes, secure project transformation is supported through automated plan generation and conditional execution. This ensures that applying or removing Pulp-native artifacts follows strict criteria to reduce integration risks.

Why should I use a structured manifest for complex project dependency management?▼

Using a structured manifest for complex project dependency management ensures only curated dependencies are integrated. Validating package manifests against strict criteria reduces integration risks and ensures a smooth development process.