kits

Manage local Pulp-native artifact lifecycles with filesystem safety and trust boundaries.

13|1|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/Generous-Corp/pulp --skill kits-generous-corp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kits
Source: https://github.com/Generous-Corp/pulp/tree/main/.agents/skills/kits
Command: npx skills add https://github.com/Generous-Corp/pulp --skill kits-generous-corp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill provides a secure, structured way to handle local Pulp-native artifacts like source kits, UI components, and templates, ensuring they are inspected and verified before they mutate your project.

Core Features & Use Cases

  • Safe Inspection: Validate and plan project changes from local kits without executing untrusted code.
  • Project Scaffolding: Initialize new kits or create projects from existing templates with full validation.
  • Lifecycle Management: Securely apply, remove, and publish local packages with explicit trust boundaries and hash-based verification.

Quick Start

Use the kits skill to validate the local package located in the my-kit directory before applying it to your current project.

Frequently Asked Questions about kits

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

FAQPage Schema
How do I validate local Pulp packages before applying them to a project?

Validating local Pulp packages requires inspecting package manifests and verifying file integrity through hash-based checks before any project mutation occurs. This enforces strict filesystem safety and trust boundaries without executing untrusted code.

What is a source kit and when do I need to inspect one?

A source kit is a Pulp-native artifact containing source code, UI components, or project templates. You need to inspect one when applying local packages to ensure package schemas are verified and secure before mutating your project directory.

Can I scaffold a new project from existing local templates securely?

Scaffolding new projects from existing local templates is supported with full validation. The process initializes new kits by enforcing explicit trust boundaries and verifying package manifests before applying any filesystem changes.

How do I manage the lifecycle of local packages including removal and publishing?

Managing the lifecycle of local packages involves securely applying, removing, and publishing artifacts with explicit trust boundaries. Hash-based verification and strict filesystem safety are enforced throughout every lifecycle mutation.

Does local directory access need special permissions for Pulp package validation?

Local directory access is required to validate package schemas and verify file integrity. The process enforces strict filesystem safety boundaries, ensuring only explicitly trusted local Pulp-native artifacts are permitted to mutate the project.