up-manager

Automate User Preferences lifecycle management across editing, versioning, QC, and reporting.

1|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/jasonnamii/up-manager --skill up-manager
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: up-manager
Source: https://github.com/jasonnamii/up-manager/tree/main
Command: npx skills add https://github.com/jasonnamii/up-manager --skill up-manager

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

UP-manager provides a unified workflow to manage all User Preferences (UP) settings across their lifecycle, including DSL editing, version bumps, path updates, QC validation, stability tracking, propagation, and reporting, reducing manual overhead and errors.

Core Features & Use Cases

  • Centralized UP lifecycle management across INIT, IG, EDIT, QC, TEAM_SYNC, and REPORT.
  • Automatic semantic version bumps and auto path updates, with QC validation and error handling.
  • Team synchronization and personal filter to prevent personal custom changes leaking into team.
  • One-turn Fast path for L1/L2 edits and full pipeline for complex changes.

Quick Start

Trigger to add, modify, or manage preferences; the skill will run through the pipeline in a single turn.

Frequently Asked Questions about up-manager

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

FAQPage Schema
How do I automate version bumps and path updates for User Preferences settings?

You can automate version bumps and path updates for User Preferences settings by running the INIT→IG→EDIT→QC→TEAM_SYNC→REPORT pipeline, which automatically handles semantic versioning and path corrections while enforcing invariant guards to prevent regressions.

What is the best way to prevent personal custom changes from leaking into team preferences?

The best way to prevent personal custom changes from leaking into team preferences is to use a personal filter during team synchronization, ensuring that only approved modifications propagate to the shared configuration.

How do I execute rapid L1 or L2 preference edits without running the full pipeline?

You can execute rapid L1 or L2 preference edits without running the full pipeline by triggering the one-turn fast path, which allows quick turnarounds while still maintaining strict file and code block handling.

Can I use DSL workflows for single-block preference management?

Yes, you can use KR single-block DSL workflows for preference management, which are fully supported across the entire editing, versioning, and reporting lifecycle to ensure reproducible results.

How does QC validation work during the preference management pipeline?

QC validation works during the preference management pipeline by automatically checking stability and enforcing invariant guards after edits are applied, catching errors and preventing regressions before team synchronization and reporting occur.

When should I use the full linear pipeline instead of fast-path edits for configuration changes?

You should use the full linear pipeline instead of fast-path edits when handling complex changes that require comprehensive stability tracking, team synchronization, and detailed reporting to ensure no regressions occur.