promote

Promote reusable patterns from downstream projects to the upstream agent-kit template.

2|1|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/lucidlabs-hq/agent-kit --skill promote
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: promote
Source: https://github.com/lucidlabs-hq/agent-kit/tree/main/.claude/skills/promote
Command: npx skills add https://github.com/lucidlabs-hq/agent-kit --skill promote

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps downstream projects share reusable, pattern-based work with the upstream agent-kit, reducing duplication and ensuring consistency across templates.

Core Features & Use Cases

  • Promote .claude/skills/* and related artifacts from a downstream project to the upstream template to standardize patterns.
  • Enforce PR-based merging and upstream alignment to maintain code review discipline.
  • Document and track promoted items to improve maintainability and knowledge sharing.

Quick Start

Run the promote script to push reusable patterns from this project to the upstream agent-kit.

Frequently Asked Questions about promote

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

FAQPage Schema
How do I promote reusable patterns from a downstream project to an upstream template repository?

To promote reusable patterns from a downstream project to an upstream template, you run the promotion script to identify portable artifacts like UI components or CLI scripts, filter out domain-specific items, and push the changes via a feature branch and pull request.

What is the best way to share generic CLI scripts and documentation across multiple projects?

Sharing generic CLI scripts and documentation across projects is best handled by promoting them to a shared upstream agent-kit, which standardizes reusable patterns and reduces duplication through a reviewed pull request workflow.

How does the pull request workflow work when pushing reusable code upstream?

The pull request workflow for pushing reusable code upstream works by staging your generic patterns on a feature branch, filtering out project-specific logic, and submitting a PR to the upstream template to ensure code review discipline and alignment.

Should I include domain-specific components when standardizing patterns to an upstream agent-kit?

You should not include domain-specific components when standardizing patterns to an upstream agent-kit. The promotion process explicitly filters out project-specific items to ensure only generic, portable artifacts are shared across templates.

Can I use git feature branches to track promoted patterns back to the upstream template?

Yes, you can use git feature branches to track promoted patterns back to the upstream template. The process enforces PR-based merging and documents the promotion steps to improve maintainability and knowledge sharing.