update-demos

Automate updating and rebuilding Pulp demo repositories to a specified SDK version.

1|Updated Jul 11, 2026
One-click install
npx skills add https://github.com/danielraffel/burl --skill update-demos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-demos
Source: https://github.com/danielraffel/burl/tree/main/.agents/skills/update-demos
Command: npx skills add https://github.com/danielraffel/burl --skill update-demos

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pulp, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of updating, rebuilding, and republishing Pulp's downstream demo/example repositories against a new or latest SDK version, saving time and reducing the risk of errors.

Core Features & Use Cases

  • Automated Updates: Rebuild and re-pin demo/example repositories against a new SDK version.
  • Natural Language Routing: Handles user requests for updates in various natural language phrases.
  • Multi-step Workflow: Coordinates steps including sweep, update, and publish-runbook operations.
  • Use Case: Ideal for developers who need to ensure that the demo/example repositories are up-to-date with the latest SDK changes.

Quick Start

Update the demo repositories to the latest SDK by running 'update-demos to latest'.

Frequently Asked Questions about update-demos

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

FAQPage Schema
How do I update Pulp demo repositories to a new SDK version?

To update Pulp demo repositories to a new SDK version, you can use a natural language command like 'update-demos to latest'. This automates the process of re-pinning, rebuilding, and republishing the downstream example repositories against the specified SDK.

What is the best way to automate Pulp SDK example republishing?

Automating Pulp SDK example republishing is best handled by the update-demos Skill, which coordinates sweep, update, and publish-runbook operations. This streamlines the process of rebuilding and re-pinning demo repositories against the latest SDK changes, saving time and reducing errors.

Do I need the Pulp Managed SDK Consumer Sweep to rebuild demo repositories?

Yes, you need the Pulp Managed SDK Consumer Sweep to rebuild and update consumer repositories. The update-demos Skill requires interaction with this sweep to successfully execute the multi-step workflow for updating and republishing downstream example repositories.

Why should I automate updating downstream example repositories against a new SDK?

Automating the update of downstream example repositories against a new SDK saves time and reduces the risk of errors. It ensures that your Pulp demo repositories are consistently up-to-date with the latest SDK changes without requiring manual rebuild and republish steps.