orient
Use when entering a vault cold, starting any work, or needing to understand what is in the vault. Orients to vault identity, strategic priorities, and assembles topic-focused context. Activates on "orient", "load context", "what is in the vault", or "vault status".
- License 许可
- MIT
- 最近更新
- 2026-03-22
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- orient
- version
- 1.0.0
- description
- Use when entering a vault cold, starting any work, or needing to understand what is in the vault. Orients to vault identity, strategic priorities, and assembles topic-focused context. Activates on "orient", "load context", "what is in the vault", or "vault status".
02 资源文件 2
- 参考文档evals/triggers.json1.2 KB
- 参考文档references/context-assembly.md2.7 KB
03 SKILL.md 正文
Vault Orientation
Orient to the vault before doing any work. This skill assembles the full context payload: identity, polaris priorities, and topic-relevant content.
Workflow
-
Read
ztlctl://self/identity— understand vault personality, owner, and structure. This establishes who owns the vault and what its core purpose is. -
Read
ztlctl://polaris— load strategic priorities (mission, active priorities, and decision principles). Polaris is Layer 1 of every context payload — always load it. -
Call
session_status()— check if a session is currently open. Surface the active session ID, topic, and duration if one exists. -
Call
work_queue()— get a summary count of actionable items (tasks, stale seeds, orphans). Report the total count and top 3 highest-scored items. -
Call
agent_context(topic="<user-topic>", budget=8000)— assemble the 5-layer context payload (polaris, related notes, graph neighbors, session history, methodology). If no specific topic was requested, omit the topic parameter for general vault orientation. -
Report structured summary to the user before proceeding with any work.
What to report
After completing the workflow, surface:
- Vault identity — name, owner (if present in identity), and stated purpose
- Top 3 polaris priorities — the strategic priorities most relevant to the current topic
- Related content count — number of related notes found for the topic
- Session status — whether a session is currently open (ID, topic, duration)
- Work queue summary — total actionable items count and top 3 by score
- Methodology summary — one-liner from the vault identity describing the owner's working style
When NOT to use
- If already oriented in this conversation — skip re-reading identity and polaris
(the context is still in your window). Call
agent_contextagain only if the topic changes significantly. - If the user issued a specific tool call — do not pre-orient before every single action. Orient once per conversation entry point, not before each operation.
- If orientation data is already present — check whether you have already read
ztlctl://self/identityandztlctl://polarisbefore re-reading them.
See references/context-assembly.md for details on the 5-layer context payload
and budget tuning.
04 同仓库更多 Skills
vault-methodology
Use when working in a ztlctl vault — creating notes, organizing knowledge, tagging, linking, or making decisions about content types and structure. Activates for any knowledge management task.
synthesize
Use when the user wants to synthesize scattered notes into a unified artifact, consolidate knowledge on a topic, connect existing notes, find structural gaps, or create a synthesis note. Activates on "synthesize", "consolidate", "connect my notes on X", "summarize what I know about X", "find gaps in X", or "create synthesis".
session
Use when the user wants to start, begin, or open a work session, OR close, end, or finish an active session. Manages the full session lifecycle: pre-flight checks, polaris alignment, session start, and session close with enrichment pipeline.
session-workflow
Use when starting, running, or closing research sessions. Guides structured knowledge capture workflows: start → capture → synthesize → close.
review-triage
Use when the user asks to review the work queue, triage pending items, clear the backlog, or find out what needs attention in the vault. Surfaces prioritized actionable items and batch-processes approved updates.
review-contradictions
Use when the user wants to review conflicting notes, find inconsistencies in the vault, check for contradictions between knowledge claims, or inspect semantically-close notes that may conflict. Runs the per-pair evaluation loop to surface genuine contradictions and dismiss false positives.