CORE

Enforce CORE identity and mandatory response format across Claude Code sessions.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/mikegil/MaxAI --skill core-mikegil
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: CORE
Source: https://github.com/mikegil/MaxAI/tree/main/.claude/Skills/CORE
Command: npx skills add https://github.com/mikegil/MaxAI --skill core-mikegil

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill defines your PAI's identity, mandatory response format, and core operating principles, auto-loading at session start.

Core Features & Use Cases

  • Auto-load core context at session start to ensure consistent identity and behavior
  • Enforce a canonical response format and identity guardrails
  • Support delegation and multi-agent workflow routing for complex tasks

Quick Start

Load CORE context at session start to establish the AI's identity and default behavior. For example: "Initialize CORE context and respond using the canonical format."

Frequently Asked Questions about CORE

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

FAQPage Schema
How do I define and auto-load my AI system's core identity at session start?

Core identity auto-loads at session start to enforce consistent behavior, response format, and operating principles across all Claude Code sessions. Use YAML frontmatter with mandatory USE WHEN directives and TitleCase naming to establish canonical identity and guardrails that apply globally.

What's the difference between manually setting identity versus using auto-load at session start?

Auto-load enforces core identity deterministically across all sessions without manual intervention, ensuring consistent behavior during user inquiries, workflow initiation, and observability events. Manual setup requires per-session configuration and risks inconsistency in identity enforcement.

Can I use workflow routing to delegate tasks across multiple AI agents?

Yes. Core identity supports delegation and multi-agent workflow routing through the Workflow Routing blueprint, enabling deterministic CLI-first operation and task delegation patterns across complex workflows.

How does CORE integrate with CLI-first operation and session lifecycles?

CORE applies globally during session initialization, tool usage, and lifecycle events, integrating with the hook-system for notifications and history capture. It ensures mandatory response format and identity guardrails persist throughout CLI-first workflows.

What happens if I don't enforce core identity at session start?

Without core identity enforcement at session start, response format becomes inconsistent, identity guardrails may not apply uniformly, and delegation patterns across sessions risk ambiguity or deviation from canonical behavior requirements.

Do I need prior knowledge of workflow routing to use CORE's delegation patterns?

CORE integrates the Workflow Routing blueprint, but understanding delegation and multi-agent routing helps you leverage advanced features. Basic auto-load identity enforcement requires only YAML frontmatter setup with USE WHEN and TitleCase naming.