⏳ This skill is pending AI review.

Scores will appear once the review pipeline completes.

version unknown

telos

sauldataman@sauldataman⭐ 0 stars· last commit 7mo ago· 0 open issues

TELOS (Telic Evolution and Life Operating System) — Reads, updates, and backs up the user's personal life OS stored in ~/clawd/telos/. Provides missions, goals, beliefs, challenges, and wisdom as context for life-aligned AI assistance. Based on Daniel Miessler's PAI framework. Use when: (1) user mentions 'telos', 'setup telos', 'update telos', 'add to telos', 'my goals', 'my beliefs', 'my missions', 'telos status'; (2) user asks about personal decisions, career direction, investment choices, relationships, priorities, or life strategy — always check for telos context first; (3) user says 'help me fill telos', '引导我填 telos', or 'telos onboarding'; (4) user says 'backup telos', 'restore telos', 'telos backups', 'telos history', or 'list telos snapshots'.

Choose how to use this skill

You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.

1. Native installer

This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.

Do not guess an installer command or replace an existing version without reviewing the diff.

2. Complete package recommended

Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.

No complete ProSkills package is published for this listing yet.

3. Prompt-only

Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.

Need only the instruction file?

Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.

No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.

—/10

// RATINGS

⭐GitHub Stars
⭐ 0 on GitHubGitHub ↗

New / niche

🟢ProSkills Score
—
📍

Not yet listed on ClawHub or SkillsMP

// README

openclaw-telos

version

TELOS (Telic Evolution and Life Operating System) — A personal life OS skill for OpenClaw and Claude Code.

Captures who you are across missions, goals, beliefs, challenges, and wisdom. Gives your AI a persistent understanding of you — so it can give life-aligned advice, not just generic answers.

Based on Daniel Miessler's PAI Framework.


What It Does

FeatureDescription
📁 20 TemplatesFull TELOS file set — fill at your own pace
🧭 Guided OnboardingStep-by-step Q&A to fill your core files (Missions → Goals → Beliefs)
🔄 Safe UpdatesTypeScript scripts handle backup → append → changelog automatically
🧠 Session ContextAI reads your TELOS at session start, knows your missions and goals throughout
💡 Personal AnalysisWhen you ask about decisions, career, or investments — AI cross-references your telos
💬 ConversationalAI engages with your insights before recording — not just a database, a thinking partner

Quick Start

1. Install

OpenClaw:

openclaw skills install ./telos.skill

Claude Code:

git clone https://github.com/sauldataman/openclaw-telos.git
cp -r openclaw-telos ~/.claude/skills/telos

2. Initialize

Say:

setup telos

This runs the init script, copies all 20 templates to ~/clawd/telos/, and walks you through filling the core files.

Or initialize manually:

bun ~/.claude/skills/telos/scripts/init-telos.ts

3. Start Filling

The AI guides you through the essentials:

  1. Missions — What are you ultimately trying to achieve?
  2. Goals — Specific objectives supporting your missions
  3. Beliefs — Core beliefs that guide your decisions

No pressure to fill everything at once — TELOS grows with you. The AI learns from your conversations and suggests additions over time.

4. Use It

Once set up, the AI automatically:

  • Reads your telos at session start
  • References your goals and beliefs when advising on decisions
  • Flags conflicts between suggestions and your stated missions
  • Suggests telos additions when relevant topics come up naturally

Trigger updates anytime:

add this book to telos — The Psychology of Money by Morgan Housel
I learned something, add to telos — consistency beats intensity
add to my wisdom — [principle or insight]
I was wrong about [X]
update my goals
telos status

Skill Structure

openclaw-telos/
├── SKILL.md                    ← Main skill instructions
├── telos.skill                 ← OpenClaw package
├── assets/templates/           ← 20 template files
├── references/
│   ├── onboarding.md           ← Guided setup workflow
│   └── update-workflow.md      ← Update format rules per file
├── scripts/
│   ├── init-telos.ts           ← Initialize ~/clawd/telos/ from templates
│   └── update-telos.ts         ← Safe update: backup → append → changelog
└── evals/
    └── evals.json              ← Test cases for skill evaluation

Scripts

init-telos.ts — Copies templates to ~/clawd/telos/. Skips files that already exist (safe to rerun).

bun scripts/init-telos.ts

update-telos.ts — Updates a telos file with automatic backup and changelog.

bun scripts/update-telos.ts <file> "<content>" "<description>"

# Example:
bun scripts/update-telos.ts BOOKS.md \
  "- *Dune* by Frank Herbert — power, ecology, and the danger of messiahs" \
  "Added book: Dune"

The script:

  1. Validates the filename against the allowed list
  2. Creates a timestamped backup in ~/clawd/telos/backups/
  3. Appends content (never overwrites)
  4. Logs the change in ~/clawd/telos/updates.md

User Data Structure

~/clawd/telos/              ← Your personal data (never shared)
├── TELOS.md                ← Master overview (start here)
├── MISSION.md              ← M0, M1, M2...
├── GOALS.md                ← G0, G1, G2...
├── BELIEFS.md              ← B0, B1, B2...
├── CHALLENGES.md           ← C0, C1...
├── STRATEGIES.md           ← S0, S1...
├── FRAMES.md               ← FR0, FR1...
├── MODELS.md               ← MO0, MO1...
├── NARRATIVES.md           ← N0, N1...
├── PROBLEMS.md             ← P0, P1...
├── PREDICTIONS.md
├── PROJECTS.md
├── TRAUMAS.md              ← TR0, TR1...
├── IDEAS.md                ← I0, I1...
├── BOOKS.md
├── MOVIES.md
├── STATUS.md
├── LEARNED.md
├── WISDOM.md
├── WRONG.md
├── updates.md              ← Append-only changelog
└── backups/                ← Auto-created timestamped backups

Priority Guide

Start with these, fill the rest over time:

PriorityFiles
⭐⭐⭐ Core (fill first)MISSION.md + GOALS.md + BELIEFS.md
⭐⭐ ImportantCHALLENGES.md, STRATEGIES.md, STATUS.md
⭐ Accumulate over timeWISDOM.md, LEARNED.md, BOOKS.md, MODELS.md, FRAMES.md, WRONG.md
OptionalTRAUMAS.md, PREDICTIONS.md, MOVIES.md, NARRATIVES.md, PROBLEMS.md

Numbering System

All entries use cross-referenceable prefixes:

M#   Missions      G#   Goals         C#   Challenges
S#   Strategies    B#   Beliefs       FR#  Frames
MO#  Models        N#   Narratives    P#   Problems
TR#  Traumas       I#   Ideas

Relationships:

MISSIONS (M#)
    └─ supported by → GOALS (G#)
                          └─ blocked by → CHALLENGES (C#)
                                              └─ solved by → STRATEGIES (S#)

BELIEFS (B#)  → guide all decisions
PROBLEMS (P#) → drive GOALS
MODELS (MO#)  → shape understanding

OpenClaw Hook (Optional)

For automatic context injection, install the included hook:

cp hooks/telos-context.js ~/.openclaw/hooks/

This gives you:

  • Session start: AI automatically knows your missions, goals, beliefs from the first message
  • Personal questions: Relevant TELOS files injected before the AI responds (career question → loads STRATEGIES, book question → loads BOOKS.md, coding question → nothing loaded)
  • Zero overhead: Non-personal conversations get no TELOS context at all

Without the hook, the skill still works — the AI follows the SKILL.md instructions to load files on demand. The hook just makes it seamless.


Privacy

  • ~/clawd/telos/ is never committed to git by default
  • Templates in this repo contain no personal data
  • All personal data stays local on your machine

Compatibility

  • OpenClaw — Primary target (.skill install format)
  • Claude Code — Copy to ~/.claude/skills/telos/; compatible with the Agent Skills specification
  • PAI — Templates can be used directly in ~/.claude/PAI/USER/TELOS/

Credits


License

MIT — see LICENSE


"Most people don't believe they have valuable contributions to make. They've never asked who they are, what they're about, and have never articulated or written it down."

— Daniel Miessler

// HOW IT'S BUILT

// FILES

2 files shipped with this skill. Inline text is the catalog copy. The upstream link is the source repository.

  • SKILL.md7.9 KBupstream ↗
    ---
    name: telos
    description: "TELOS (Telic Evolution and Life Operating System) — Reads, updates, and backs up the user's personal life OS stored in ~/clawd/telos/. Provides missions, goals, beliefs, challenges, and wisdom as context for life-aligned AI assistance. Based on Daniel Miessler's PAI framework. Use when: (1) user mentions 'telos', 'setup telos', 'update telos', 'add to telos', 'my goals', 'my beliefs', 'my missions', 'telos status'; (2) user asks about personal decisions, career direction, investment choices, relationships, priorities, or life strategy — always check for telos context first; (3) user says 'help me fill telos', '引导我填 telos', or 'telos onboarding'; (4) user says 'backup telos', 'restore telos', 'telos backups', 'telos history', or 'list telos snapshots'."
    requires:
      - bun       # scripts/init-telos.ts, update-telos.ts, backup-telos.ts
      - node      # hooks/telos-context.js (optional hook)
    ---
    
    # TELOS — Telic Evolution and Life Operating System
    
    User's personal life OS. 20-file system capturing who they are across missions, goals, beliefs, challenges, and wisdom. Read at session start. Updated through guided workflows.
    
    ## Data Location
    
    - **User data**: `$OPENCLAW_WORKSPACE/telos/` (defaults to `~/openclaw/telos/`, never committed to git)
    - **Templates**: `assets/templates/` in this skill (20 files)
    - **References**: `references/onboarding.md`, `references/update-workflow.md`
    
    ## Context Loading
    
    **Two modes depending on setup:**
    
    - **With hook** (`hooks/telos-context.js` installed): MISSION.md + GOALS.md + BELIEFS.md are **automatically pre-loaded at session start** via `agent:bootstrap`. Additional files are injected on-demand when relevant topics are detected in your messages. This grants the hook persistent, automatic behavior — only install if you want this.
    - **Without hook** (default): Files are loaded **on-demand only** — the AI reads SKILL.md instructions and loads the relevant files based on the context. Nothing is auto-injected.
    
    > ⚠️ **Persistence note:** Installing the hook enables automatic context injection at every session start. This is intentional behavior — opt in only if you want TELOS context always available.
    
    ### File Index
    
    Use this index to decide which files to read. Each file captures a different dimension of the user's life context:
    
    | File | Contains | Load when the conversation touches... |
    |---|---|---|
    | MISSION.md | M# — ultimate life purposes | direction, meaning, "why am I doing this", major decisions |
    | GOALS.md | G# — specific objectives with timelines | planning, priorities, "should I do X", progress, deadlines |
    | BELIEFS.md | B# — core convictions guiding decisions | values, principles, "what do you think about", worldview |
    | CHALLENGES.md | C# — current obstacles | frustration, being stuck, blockers, "I can't seem to" |
    | STRATEGIES.md | S# — approaches to challenges/goals | how to tackle something, methodology, "what's my plan for" |
    | PROBLEMS.md | P# — problems in the world to solve | entrepreneurship, impact, "what problem should I work on" |
    | PROJECTS.md | Active initiatives | work, side projects, "what am I working on" |
    | NARRATIVES.md | N# — talking points, self-story | pitching, introducing yourself, "how do I explain what I do" |
    | FRAMES.md | FR# — mental perspectives | reframing, alternative viewpoints, "how should I think about" |
    | MODELS.md | MO# — how things work | decision-making, analysis, cause-and-effect reasoning |
    | PREDICTIONS.md | Future bets with confidence levels | forecasting, trends, "what do you think will happen" |
    | WISDOM.md | Accumulated principles and quotes | advice, life lessons, "what's your take on" |
    | LEARNED.md | Specific lessons from experience | reflecting, "what have I learned about", mistakes made |
    | WRONG.md | Things the user was wrong about | intellectual humility, updating beliefs, "I changed my mind" |
    | BOOKS.md | Influential books | reading, recommendations, "what should I read" |
    | MOVIES.md | Influential films | media, culture, recommendations |
    | TRAUMAS.md | TR# — formative experiences | deep personal context, patterns, "why do I always" |
    | IDEAS.md | I# — ideas worth capturing | brainstorming, "I just thought of", creative exploration |
    | STATUS.md | Current life snapshot | "where am I right now", life audit, quarterly review |
    | TELOS.md | Master overview with all sections | "show me my telos", full context needed, onboarding |
    
    ### Loading Rules
    
    1. Check if `~/clawd/telos/` exists. If not, skip silently.
    2. Read the user's message. Identify which life dimensions it touches (use the "Load when" column).
    3. Read only those files. Usually 1-3 files, rarely more than 4.
    4. Absorb silently — use the context to inform your response without announcing it.
    5. If a file is empty (only template content), skip it.
    6. For major life decisions, load the core trio: MISSION.md + GOALS.md + BELIEFS.md.
    7. If no telos directory exists and the user asks about personal topics, suggest "setup telos."
    
    The goal: every response to a personal question should be informed by the user's own stated values, not generic advice. But unrelated conversations (coding, factual questions, etc.) should not trigger any telos loading.
    
    ## Trigger → Action Map
    
    | Trigger | Action |
    |---|---|
    | "setup telos" / "telos onboarding" / "引导我填" | Run `bun {baseDir}/scripts/init-telos.ts` then see `references/onboarding.md` |
    | "update telos" / "add to telos" | Run update script (see below) — respond conversationally, not mechanically |
    | "add book [title]" | Acknowledge the book, reflect on the insight, then append to `BOOKS.md` |
    | "learned [X]" / "add to learned" | Engage with the lesson first, then append to `LEARNED.md` |
    | "add to wisdom" | Discuss the principle, then append to `WISDOM.md` |
    | "telos status" | Read + summarize `STATUS.md` |
    | "my goals / beliefs / missions" | Read relevant file, respond in context |
    | "I was wrong about [X]" | Append to `WRONG.md` with date + lesson |
    | "backup telos" | Run `bun {baseDir}/scripts/backup-telos.ts backup` |
    | "restore telos" / "restore telos from [name]" | Run `bun {baseDir}/scripts/backup-telos.ts restore <name>` |
    | "list telos backups" / "telos snapshots" | Run `bun {baseDir}/scripts/backup-telos.ts list` |
    | "telos history [file]" / "show beliefs history" | Run `bun {baseDir}/scripts/backup-telos.ts history <file>` |
    | "restore beliefs from [version]" | Run `bun {baseDir}/scripts/backup-telos.ts restore-file <file> <ver>` |
    
    ## Personal Analysis Context
    
    When user asks about **personal decisions, investments, career, relationships, life priorities, or strategy** — always check telos first:
    
    1. If telos files exist → read relevant sections before responding
    2. Frame advice against their Goals (G#) and Beliefs (B#)
    3. Flag if a suggested action conflicts with their stated Missions (M#)
    4. Reference their Challenges (C#) and Strategies (S#) when relevant
    
    Example: user asks "should I take this opportunity?" → read M#, G#, B# → advise through that lens.
    
    ## Numbering System
    
    `M#` Missions · `G#` Goals · `C#` Challenges · `S#` Strategies · `B#` Beliefs · `FR#` Frames · `MO#` Models · `N#` Narratives · `P#` Problems · `TR#` Traumas · `I#` Ideas
    
    Hierarchy: `M → G ← (blocked by) C ← (solved by) S` | `B` guides all | `P` drives `G`
    
    ## Update Workflow
    
    When updating telos, the conversation matters as much as the data. Follow this order:
    
    1. **Engage first** — Acknowledge what the user shared. Reflect on the insight, ask a follow-up, or connect it to their existing telos context. This is a life framework, not a database — treat additions as meaningful moments.
    2. **Execute** — Run the update script: `bun {baseDir}/scripts/update-telos.ts <file> "<content>" "<description>"`
    3. **Confirm briefly** — Mention it's backed up and logged. Don't dump execution logs.
    4. **Suggest connections** — After adding to one file, suggest related files that might benefit. ("This connects to your B0 about compounding — want to add a r
  • README.mdupstream ↗

    Contents are not inlined in the catalog. Open the upstream file.

Plain-text copy, no login: /skill-bundles/sauldataman-openclaw-telos.md

// REPO STATS

0 stars
0 open issues
Last commit: 7mo ago