workflow-client-bootstrap

Alias deprecated skill names to updated versions for workflow continuity.

2|3|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/ulises-jeremias/agentic-workstation --skill workflow-client-bootstrap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow-client-bootstrap
Source: https://github.com/ulises-jeremias/agentic-workstation/tree/main/home/dot_local/share/agentic-workstation/skills/workflow-client-bootstrap
Command: npx skills add https://github.com/ulises-jeremias/agentic-workstation --skill workflow-client-bootstrap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides backward compatibility by aliasing an older skill name to the updated version.

Core Features & Use Cases

  • Backward Compatibility: Facilitates the usage of a deprecated skill name through aliasing.
  • Skill Alias: Ensures that scripts and configurations using the old skill name still function.
  • Use Case: For users who have scripts or configurations referencing the deprecated skill, this alias ensures their existing workflow continues to work without modification.

Quick Start

To use the workflow-client-bootstrap skill, run dots-workstation-workflow-client-bootstrap in your terminal.

Frequently Asked Questions about workflow-client-bootstrap

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

FAQPage Schema
How do I maintain backward compatibility for deprecated workflow skills in my scripts?

Skill aliasing provides backward compatibility by mapping the deprecated 'workflow-client-bootstrap' name to the updated 'dots-workstation-workflow-client-bootstrap'. This ensures existing scripts and configurations continue functioning without requiring any code modifications.

What is skill aliasing and when do I need it for workflow continuity?

Skill aliasing is a backward compatibility mechanism that maps a deprecated skill name to its updated replacement. You need it for workflow continuity when existing scripts reference old skill names and must operate without modification.

Do I need to update my configurations to run the updated workflow client bootstrap?

No, you do not need to update your configurations to run the updated workflow client bootstrap. The alias automatically routes the deprecated skill name to the updated version, ensuring your current setup operates seamlessly.

Can I use the old workflow-client-bootstrap skill name in my current automation setup?

Yes, you can use the old workflow-client-bootstrap skill name in your current automation setup. The alias intercepts the deprecated name and redirects it to the dots-workstation-workflow-client-bootstrap skill, preserving your automation logic.

What is the best way to transition from a deprecated skill name to an updated workflow client?

The best way to transition from a deprecated skill name to an updated workflow client is by applying a skill alias. This bridges the old and new names, allowing workflows to run the updated bootstrap logic while referencing the old identifier.

Why does my workflow still reference the old skill name after updating the client bootstrap?

Your workflow still references the old skill name because the alias is designed to maintain backward compatibility. It intentionally accepts the deprecated name to prevent breaking existing scripts while executing the updated bootstrap logic underneath.