always-init
Universal task initializer that automatically loads PAI context for all user requests. Ensures complete context availability (contacts, preferences, protocols) before responding to any task. (project, gitignored)
Best use case
always-init is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Universal task initializer that automatically loads PAI context for all user requests. Ensures complete context availability (contacts, preferences, protocols) before responding to any task. (project, gitignored)
Teams using always-init should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/always-init/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How always-init Compares
| Feature / Agent | always-init | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Universal task initializer that automatically loads PAI context for all user requests. Ensures complete context availability (contacts, preferences, protocols) before responding to any task. (project, gitignored)
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# ALWAYS-INIT - Universal Task Initializer
---
⚠️ **CRITICAL SYSTEM REQUIREMENT** ⚠️
**AUTOMATIC INVOCATION REQUIRED:**
This skill MUST be automatically invoked as the FIRST action for EVERY user request without exception.
**Trigger Pattern:** ALL user messages/requests
**Priority Level:** P0 (Highest - blocks all other operations)
**Automation Rule:** `if (userRequest) → invoke("always-init") → then processRequest()`
---
## 🎯 Purpose
Universal context loader providing complete PAI (Personal AI Infrastructure):
- 👥 **Contacts**: Alice, Bob, Carol, Dave, team members
- 🛠️ **Stack Preferences**: TypeScript>Python, bun>npm, uv>pip
- 🔒 **Security Protocols**: Repository safety, credential handling
- 📝 **Response Format**: Structured output standards
- 🎙️ **Voice Routing**: ElevenLabs voice IDs for agents
- ⚙️ **Operating Instructions**: Personal preferences and workflows
## ❌ Consequences of Skipping
Without ALWAYS-INIT context loading:
- Responses lack relationship/contact awareness
- Wrong technical stacks used (npm instead of bun, pip instead of uv)
- Security protocols violated
- Incorrect response formatting
- Missing personalization
- Context-dependent decisions fail
- Agent routing fails
## 🔄 Implementation Protocol
### For AI Assistant (Claude):
```
1. Receive user request
2. ⚡ IMMEDIATELY: Skill("always-init") ← THIS STEP
3. Wait for PAI context to load
4. THEN proceed with request processing
```
### For Skill System (Automation):
```javascript
// Automatic prepend to request pipeline
function handleUserRequest(request) {
await invokeSkill("always-init"); // MANDATORY FIRST STEP
const paiContext = loadContext();
return processWithContext(request, paiContext);
}
```
## 🎯 Success Criteria
**This skill is working correctly when:**
- ✅ Invoked before ANY tool use
- ✅ Invoked before ANY other skill
- ✅ Invoked before ANY response formulation
- ✅ Invoked for 100% of user requests
- ✅ PAI context available in all subsequent operations
## 📍 Context Loading
**Execute:** `read ~/.claude/skills/PAI/SKILL.md`
This provides the complete Personal AI Infrastructure context that all skills and responses depend on.
Once PAI context is loaded, proceed immediately with the user's actual request.
## 🏗️ Design Philosophy
This skill implements a "context-first" architecture where PAI loads universally rather than being distributed across individual skills. It acts as a bootstrap loader that:
1. **Triggers on every user interaction**
2. **Loads PAI context once**
3. **Gets out of the way**
4. **Allows the actual task to proceed**
This eliminates the need for individual skills to manually load PAI context and ensures consistent, complete context availability across all operations.
---
**💡 Implementation Note:**
Ideally, this skill should be **hardcoded into the request handler** rather than relying on manual invocation. The skill system should automatically prepend this to every request pipeline.
**Alternative Approach:**
Add to system prompt: "Before responding to ANY user request, you MUST first invoke the always-init skill to load PAI context."Related Skills
minitest-testing
Write, review, and improve Minitest tests for Ruby on Rails applications. Covers model tests, controller tests, system tests, fixtures, and best practices from Rails Testing Guide.
init
Initialize warehouse schema discovery. Generates .astro/warehouse.md with all table metadata for instant lookups. Run once per project, refresh when schema changes. Use when user says "/data:init" or asks to set up data discovery.
aix-init
Initialize or upgrade aix framework in a project. Detects tech stack, generates appropriate tier structure, and sets up Claude Code integration.
session-init
Initializes session with environment check and task status overview. Use when user mentions セッション開始, 作業開始, 状況確認, what should I work on, start session. Do NOT load for: 実装作業, レビュー, セッション途中の作業.
always-on
always on skill for handoffs
agentuity-cli-project-auth-init
Set up Agentuity Auth for your project. Requires authentication. Use for managing authentication credentials
affinity-mcp-workflows
Use when working with Affinity CRM via MCP tools - find entities, manage workflows, log interactions, prepare briefings, find warm intros. Also use when user mentions "pipeline", "deals", "relationship strength", or wants to prepare for meetings.
init-agents
Initialize or update AGENTS.md (or CLAUDE.md for Claude Code) with AI agent guidance. Use when user says 'init agents', 'create AGENTS.md', 'setup agent instructions', or wants project-specific AI coding assistant configuration.
agent-sdk-definitions
Programmatic agent definitions for the Claude Agent SDK in TypeScript and Python. Use when creating agents for SDK-based applications rather than filesystem-based Claude Code.
agent-init
Initialize or improve AGENTS.md files that define how coding agents operate in a repo. Use when asked to set up or replace an agent init command (Codex, Claude), standardize multi-agent behavior, or audit an existing AGENTS.md for clarity, commands, boundaries, and repo-specific context. For Claude Code, also create CLAUDE.md as a symlink to AGENTS.md.
bgo
Automates the complete Blender build-go workflow, from building and packaging your extension/add-on to removing old versions, installing, enabling, and launching Blender for quick testing and iteration.
obsidian-daily
Manage Obsidian Daily Notes via obsidian-cli. Create and open daily notes, append entries (journals, logs, tasks, links), read past notes by date, and search vault content. Handles relative dates like "yesterday", "last Friday", "3 days ago".