cmajor-external

Integrate an external Cmajor toolchain with Pulp for patch validation and artifact generation.

13|1|Updated Apr 6, 2026

Search Tags:#workflow #patch #artifact-generation #cmajor #external-toolchain #pulp #mit-safe

Ready to run

npx skills add https://github.com/danielraffel/pulp --skill cmajor-external

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pulp's MIT-safe Cmajor external lane provides a structured approach to using Cmajor patches without embedding the engine, ensuring a clean separation between the core and user-supplied toolchains.

Core Features & Use Cases

External toolchain: leverage an outside Cmajor runtime while keeping Pulp's core sandbox intact.
Patch validation: verify patch layouts and manifests before generating artifacts.
Artifact workflows: manage generated artifacts from patches and integrate with CI/docker pipelines.

Quick Start

Run the patch validation and artifact generation workflow using the provided cmajor_external.py script to begin integrating Cmajor patches.

Frequently Asked Questions about cmajor-external

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

FAQPage Schema

How do I validate Cmajor patch layouts and manifests before generating artifacts?▼

To validate Cmajor patch layouts, you can use an external toolchain integration that verifies patch manifests and structures before artifact generation. This ensures patches conform to required layouts before processing them further.

What does an MIT-safe Cmajor external toolchain do for patch-based development?▼

An MIT-safe Cmajor external toolchain enables using Cmajor patches without embedding the engine, ensuring a clean separation between the core sandbox and user-supplied toolchains during artifact workflows.

Can I integrate generated Cmajor patch artifacts with CI and Docker pipelines?▼

Yes, you can integrate generated Cmajor patch artifacts with CI and Docker pipelines. The external toolchain manages artifact generation from validated patches, allowing seamless incorporation into automated build and deployment workflows.

Do I need to supply my own cmaj executable to use the Cmajor external toolchain?▼

Yes, you need to supply a user-provided cmaj executable, patch manifests, and supporting scripts to validate layouts and generate artifacts. The toolchain leverages an outside Cmajor runtime while keeping the core sandbox intact.

What is the best way to manage MIT-safe patches without embedding the Cmajor engine?▼

The best way to manage MIT-safe patches without embedding the engine is using Pulp's external lane, which provides a structured approach to validate patches and manage artifact workflows while maintaining strict separation from the core.