danielmiessler
Life OS and project analysis. USE WHEN TELOS, life goals, projects, dependencies, books, movies. SkillSearch('telos') for docs.
bunx add-skill danielmiessler/personal_ai_infrastructure -s TelosLoading…
You MUST send this notification BEFORE doing anything else when this skill is invoked.
Send voice notification:
curl -s -X POST http://localhost:8888/notify \
-H "Content-Type: application/json" \
-d '{"message": "Running the WORKFLOWNAME workflow in the Telos skill to ACTION"}' \
> /dev/null 2>&1 &
Output text notification:
Running the **WorkflowName** workflow in the **Telos** skill to ACTION...
This is not optional. Execute this curl command immediately upon skill invocation.
TELOS (Telic Evolution and Life Operating System) is a comprehensive context-gathering system with two applications:
~/.claude/skills/CORE/USER/TELOS/When executing a workflow, output this notification directly:
Running the **WorkflowName** workflow in the **Telos** skill to ACTION...
| Workflow | Trigger | File |
|---|---|---|
| Update | "add to TELOS", "update my goals", "add book to TELOS" | Workflows/Update.md |
| InterviewExtraction | "extract content", "extract interviews", "analyze interviews" | Workflows/InterviewExtraction.md |
| CreateNarrativePoints | "create narrative", "narrative points", "TELOS report", "n=24" | Workflows/CreateNarrativePoints.md |
| WriteReport | "write report", "McKinsey report", "create TELOS report", "professional report" | Workflows/WriteReport.md |
Note: For general project analysis, dashboards, dependency mapping, and executive summaries, the skill handles these directly without a separate workflow file.
Example 1: Update personal TELOS
User: "add Project Hail Mary to my TELOS books"
--> Invokes Update workflow
--> Creates timestamped backup of BOOKS.md
--> Adds book entry with formatted metadata
--> Logs change in updates.md with timestamp
Example 2: Analyze project with TELOS
User: "analyze ~/Projects/MyApp with TELOS"
--> Scans all .md and .csv files in directory
--> Extracts entities, relationships, dependencies
--> Returns analysis with dependency chains and progress metrics
Example 3: Build project dashboard
User: "build a dashboard for TELOSAPP"
--> Launches up to 10 parallel engineers
--> Creates Next.js dashboard with shadcn/ui + Aceternity
--> Returns interactive dashboard with dependency graphs, metrics cards, progress tables
Example 4: Generate narrative points
User: "create TELOS narrative for Acme Corp, n=24"
--> Invokes CreateNarrativePoints workflow
--> Analyzes TELOS context (situation, problems, recommendations)
--> Returns 24 crisp bullet points (8-12 words each)
--> Output is slide-ready for presentations or customer briefings
Example 5: Generate McKinsey-style report
User: "write a TELOS report for Acme Corp"
--> Invokes WriteReport workflow
--> First runs CreateNarrativePoints to generate story content
--> Maps narrative to McKinsey report structure
--> Generates web-based report with professional styling
--> Output at {project_dir}/report - run `bun dev` to view
--> White background, subtle Tokyo Night Storm accents
--> Includes: cover page, executive summary, findings, recommendations, roadmap
How {DAIDENTITY.NAME} determines which TELOS context:
| User Request | Context | Location |
|---|---|---|
| "my TELOS", "my goals", "my beliefs", "add to TELOS" | Personal TELOS | ~/.claude/skills/CORE/USER/TELOS/ |
| "Alma", "TELOSAPP", "analyze [project]", "dashboard for" | Project TELOS | User-specified directory |
| "analyze ~/path/to/project" | Project TELOS | Specified path |
CRITICAL PATH: All personal TELOS files are located at:
~/.claude/skills/CORE/USER/TELOS/
Personal TELOS lives in the CORE USER directory, NOT directly under the Telos skill directory.
All files located in ~/.claude/skills/CORE/USER/TELOS/:
# View specific file
read ~/.claude/skills/CORE/USER/TELOS/GOALS.md
read ~/.claude/skills/CORE/USER/TELOS/BELIEFS.md
# View recent updates
read ~/.claude/skills/CORE/USER/TELOS/updates.md
CRITICAL: Never manually edit. Use the Update workflow.
Workflow: Workflows/Update.md
The workflow provides:
Valid files for updates: BELIEFS.md, BOOKS.md, CHALLENGES.md, FRAMES.md, GOALS.md, LEARNED.md, MISSION.md, MODELS.md, MOVIES.md, NARRATIVES.md, PREDICTIONS.md, PROBLEMS.md, PROJECTS.md, STRATEGIES.md, TELOS.md, TRAUMAS.md, WISDOM.md, WRONG.md
For any project directory, TELOS provides:
Flexible file discovery - no required structure:
# User specifies directory
"Analyze ~/Cloud/Projects/TELOSAPP"
--> {DAIDENTITY.NAME} scans for .md and .csv files anywhere in tree
# {DAIDENTITY.NAME} automatically finds all .md and .csv files regardless of structure
Auto-detection:
Discover all markdown and CSV files:
find $TARGET_DIR -type f \( -name "*.md" -o -name "*.csv" \)
Index:
Build relationship graph:
Produce analytics:
Output Formats:
CRITICAL: When building UIs, use up to 16 parallel engineers.
Launch Strategy: Use single message with 10 Task calls in parallel:
Engineer 1: Project structure + layout + navigation
Engineer 2: Overview page with metrics cards
Engineer 3: Projects page with progress tracking
Engineer 4: Teams page with performance tables
Engineer 5: Vulnerabilities/issues page
Engineer 6: Progress timeline visualization
Engineer 7: Data parsing library (MD/CSV)
Engineer 8: Shared components (cards, badges, tables)
Engineer 9: Design polish and theme
Engineer 10: Integration and testing
Tech Stack:
Features:
Design:
--background: #ffffff
--foreground: #1a1b26
--primary: #2e7de9
--accent: #9854f1
--destructive: #f52a65
--success: #33b579
--warning: #f0a020
Standard Project TELOS Structure (auto-detected):
Note: Files are optional. TELOS adapts to whatever exists.
Available Visualizations:
Personal TELOS:
Project TELOS:
~/.claude/skills/CORE/USER/TELOS/ (in CORE USER directory)TELOS is {PRINCIPAL.NAME}'s life operating system AND project analysis framework. One skill, two powerful contexts.
Remember: Personal TELOS files live at ~/.claude/skills/CORE/USER/TELOS/ (in the CORE USER directory)
Use when you need to run Flow type checking, or when seeing Flow type errors in React code.
Use when you want to validate changes before committing, or when you need to check all React contribution requirements.
Use when feature flag tests fail, flags need updating, understanding @gate pragmas, debugging channel-specific test failures, or adding new flags to React.
Use when you need to check feature flag states, compare channels, or debug why a feature behaves differently across release channels.