ad-hoc-profile-load

Name: ad-hoc-profile-load
Availability: InStock
Author: kimprobably

Load an agent profile by ID or intent for the current interactive session.

Updated May 13, 2026

Search Tags:#agent profile #session context #role switching #governance scope #doctrine directives #handoff boundaries #interactive operations

Ready to run

npx skills add https://github.com/kimprobably/maestro-os --skill ad-hoc-profile-load

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ad-hoc-profile-load
Source: https://github.com/kimprobably/maestro-os/tree/main/.claude/skills/ad-hoc-profile-load
Command: npx skills add https://github.com/kimprobably/maestro-os --skill ad-hoc-profile-load

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the need to rapidly change an agent’s persona, governance scope, and operating boundaries for a single interactive session without running the full mission loop.

Core Features & Use Cases

Interactive profile adoption: Load a role-scoped agent profile by explicit profile ID or by best-match from described intent.
Session-ready identity and boundaries: Apply the profile’s initialization declaration and specialization boundaries so the agent behaves appropriately immediately.
Scoped doctrine & charter context: Load only the directives relevant to the profile and pull charter context scoped to the inferred or requested action.

Quick Start

Ask: Load the reviewer profile for this session so you can review my proposed design for scope, risks, and quality gates.

Frequently Asked Questions about ad-hoc-profile-load

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

FAQPage Schema

How do I switch agent roles for a single interactive session without running the full mission loop?▼

Role switching outside the mission runtime loop is handled by loading an agent profile on demand, which applies the profile's identity, specialization boundaries, and scoped doctrine directives immediately for the current session.

How does loading an agent profile by explicit ID or contextual task intent work?▼

Loading an agent profile resolves the target role either by matching an explicit profile ID or by inferring the best match from described task intent, then applies the initialization declaration and governance scope.

Can I apply scoped doctrine directives and charter context to a specific agent role?▼

Yes, adopting a profile loads only the doctrine directives relevant to that profile and pulls charter context scoped to the inferred or requested action, ensuring the agent operates within correct boundaries.

Do I need to persist my agent profile selection to tool context for subsequent invocations?▼

Persisting the role selection to tool context is optional, allowing subsequent invocations within the interactive session to maintain the adopted identity, specialization boundaries, and governance scope.

What is the best way to adopt a reviewer persona with specific governance scope for an interactive session?▼

The best way to adopt a reviewer persona is to request a role-scoped agent profile by describing your intent, which applies the initialization declaration and specialization boundaries for immediate behavior alignment.

Why are handoff boundaries and specialization limits needed when switching agent roles on demand?▼

Handoff boundaries and specialization limits are needed to ensure the agent behaves appropriately immediately after role switching, restricting operations to the profile-scoped doctrine directives and adopted identity.