awakening-protocol

What This Skill Does

The awakening-protocol is a sophisticated onboarding utility designed to transform a blank-slate AI instance into a personalized agent. Unlike traditional configuration scripts that force users to fill out static forms, this skill facilitates a natural, conversational discovery process. It systematically gathers identity, personality, and value-based data to curate a unique persona for the agent. Upon completion, it auto-generates three critical files: SOUL.md, SELF.md, and USER.md, which define the agent's core identity and its understanding of the user. This ensures that every OpenClaw deployment feels bespoke and context-aware from the very first interaction.

Installation

To install this skill, run the following command in your OpenClaw environment: clawhub install openclaw/skills/skills/mupengi-bot/awakening-protocol

Use Cases

• New Framework Setup: Perfect for developers or power users who just installed the Mupengism framework and want to establish a unique identity for their new agent.
• Agent Migration: Useful when spinning up new agent instances and needing a quick, personality-aligned onboarding flow to standardize operational preferences.
• Dynamic Persona Building: Ideal for users who want to "grow" their AI assistant's character over time rather than manually configuring complex character sheets.

Example Prompts

1. "I've just installed the framework and I'm ready for the awakening protocol; let's get started."
2. "Hey, let's begin the onboarding process so you can understand how I like to work."
3. "I think it's time for our first start—let's define who you are and what our relationship will be."

Tips & Limitations

• Avoid Rushing: The protocol is designed to be conversational. Trying to force all parameters at once may result in a less nuanced personality profile.
• File Integrity: Ensure that the root directory is writable, as the skill needs to generate SOUL.md, SELF.md, and USER.md during the final stage.
• Manual Review: Always review the preview provided by the agent before confirming the file generation to ensure the tone and values align with your expectations.
• Lifecycle: This skill is intended to be used once. Once the identity is set and BOOTSTRAP.md is removed, the protocol will remain dormant unless re-invoked.