skills.rest
danielmiessler
danielmiesslerCOMMUNITY
Explore all skills by this author →
Website𝕏@danielmiesslerGitHub

always-init

Load complete PAI context before processing any user request.

55|8|Updated Oct 25, 2025
Search Tags:#automation#context management#personalization#foundational AI#AI initialization#security protocols#system configuration
One-click install
npx skills add https://github.com/danielmiessler/PAIPlugin --skill always-init
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: always-init
Source: https://github.com/danielmiessler/PAIPlugin/tree/main/skills/always-init
Command: npx skills add https://github.com/danielmiessler/PAIPlugin --skill always-init

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Without consistent, personalized context, AI agents can provide generic, unhelpful, or even incorrect responses. This critical foundational skill ensures that every user request is processed with full awareness of your personal preferences, security protocols, and contacts, preventing errors and enhancing personalization.

Core Features & Use Cases

  • Universal Context Loading: Automatically loads essential PAI (Personal AI Infrastructure) context, including contacts, preferred tech stack, security protocols, response formats, and voice routing, before any other operation.
  • Guaranteed Personalization: Ensures all subsequent AI operations are informed by your specific needs and environment, making every interaction relevant and tailored.
  • Use Case: This skill is a foundational system requirement. It ensures that whether you're asking for code, a summary, or a message to a contact, the AI always operates within your defined personal and technical parameters, making every interaction relevant, secure, and efficient.

Quick Start

This skill is designed for automatic invocation as the FIRST action for EVERY user request without exception. It should be hardcoded into the request handler or system prompt, for example: if (userRequest) → invoke("always-init") → then processRequest() It loads the complete Personal AI Infrastructure context from: read ~/.claude/skills/PAI/SKILL.md

Frequently Asked Questions about always-init

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

FAQPage Schema
How do I ensure my AI has access to my personal contacts and preferences before processing requests?▼

Context loading automatically retrieves your Personal AI Infrastructure before any request is processed. This loads contacts, preferred tech stack, security protocols, and response formats from ~/.claude/skills/PAI/SKILL.md, ensuring every interaction is personalized and secure from the start.

What happens if AI context isn't loaded before a user request?▼

Without mandatory context initialization, AI responses become generic and may violate your security protocols or miss critical personal preferences. Always-init prevents this by executing first in the processing chain, guaranteeing full context awareness before tool use or response formulation.

Can I use context management to enforce security protocols across all AI operations?▼

Yes. Context loading embeds security rules and voice routing into every request automatically. By invoking context initialization as the first step, all downstream AI operations respect your defined security parameters without requiring per-request configuration.

How do I hardcode context loading into my AI request handler?▼

Integrate context initialization as a mandatory first step: `if (userRequest) → invoke('always-init') → then processRequest()`. This pattern ensures Personal AI Infrastructure loads before any other operation, making personalization foundational rather than optional.

Does context initialization work across different task types and scenarios?▼

Context loading applies universally across all user requests and task scenarios—code generation, summaries, messaging, and more. It loads the same comprehensive PAI context regardless of task type, ensuring consistent personalization and security enforcement.

What's the difference between generic AI responses and personalized ones with context?▼

Generic responses lack awareness of your preferences, contacts, and security rules. Personalized responses with loaded context are tailored to your environment, enforce your protocols, and route appropriately to your defined contacts and systems.

Related Skills

Explore More Software Engineering Skills→
zmrezmre
1

CORE

Manage centralized context and operational guidelines for a Claude-based Personal AI Infrastructure.

Community
Basic
sabaniasabania
8

outreach

Generate personalized LinkedIn outreach messages from contact profiles and interaction history.

Community
Intermediate
blackpwnguinblackpwnguin
1

CORE

Define PAI identity and mandatory response format at session start.

Community
Advanced
vertivolatamvertivolatam
1

Code Generation Workflows

Automate Flutter boilerplate code generation with build_runner, freezed, and json_serializable.

Official
Intermediate