Agent skill

Obelisk

by tommy0103 in tommy0103/obelisk

Search and query past Claude Code, Codex, Kimi Code, Kiro, OMP, and Pi session history.

AGPL-3.0Auto-check passedAgent Workflows

Install Obelisk

skills CLI
$ npx skills add tommy0103/obelisk --skill obelisk -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install tommy0103/obelisk obelisk --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/tommy0103/obelisk.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skill-doc .claude/skills/obelisk && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
obelisk
GitHub stars
571
Token cost
~1.6k tokens
SKILL.md length
622 words
Files
21 (incl. references)
Skills in repo
3
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Search and query past Claude Code, Codex, Kimi Code, Kiro, OMP, and Pi session history.

  • Works in 5 steps: Choose the narrowest project, file,… → Normally start a new task with… → Recall prior conclusions with memories()… → …
  • Asks how did I fix X
  • SKILL.md covers Retrieval workflow, Run a query, Fresh index and permissions and Choose helpers, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Obelisk is an agent skill from tommy0103/obelisk. Search and query past Claude Code, Codex, Kimi Code, Kiro, OMP, and Pi session history. Reactive: when the user asks "how did I fix X", "what did we do last time", "find the session where", "上次怎么修的", "之前的session", "历史记录". Proactive: when the user references past work you lack context for, when you're about to modify a file with complex edit history, when the user says "继续之前的" or "continue where we left off", or when understanding prior decisions would improve your current response. Memory: when the user says…

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 22 other files, including reference files (for example `references/advanced-helpers.md`, `references/api-reference.md` and `references/memory-workflow.md`).

It sits in Agent Workflows. It works with Kimi. The repository describes itself as: Every past session, subagent, and workflow -- queryable by your agent, browsable by you. The licence is AGPL-3.0.

When your agent uses it

  • Asks how did I fix X
  • What did we do last time
  • Find the session where
  • References past work you lack context for

Example prompts

  • “how did I fix X”
  • “what did we do last time”
  • “find the session where”
  • “/obelisk”

Requirements

  • Pre-approved tools (allowed-tools): Read, Bash(obelisk:*), Write

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Choose the narrowest project, file, session, time range, or topic scope.
  2. Normally start a new task with overview({ limit: 6 }); skip orientation
  3. Recall prior conclusions with memories() and verify against session
  4. Group, deduplicate, and project inside the query. Return stable IDs and short
  5. Answer with concise evidence. Identify prior memories naturally when they

What it can do on your machine

Read from SKILL.md and the folder at commit a4b7329. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Bash(obelisk:*)
    • Write

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Obelisk loads about 1.6k tokens when it runs, and up to ~25k if it reads all its reference files. Until then it costs about 165 tokens; SKILL.md has 622 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~165
When it runs · the whole SKILL.md, loaded when a task matches
~1.6k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~25k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from tommy0103/obelisk at commit a4b7329, republished under its AGPL-3.0 licence (© tommy0103). 622 words, ~1,550 tokens.

Download SKILL.mdSave it as .claude/skills/obelisk/SKILL.md (or your agent's skills folder). This skill also uses 20 other files; get the full folder from GitHub.
name
obelisk
description
Search and query past Claude Code, Codex, Kimi Code, Kiro, OMP, and Pi session history. Reactive: when the user asks "how did I fix X", "what did we do last time", "find the session where", "上次怎么修的", "之前的session", "历史记录". Proactive: when the user references past work you lack context for, when you're about to modify a file with complex edit history, when the user says "继续之前的" or "continue where we left off", or when understanding prior decisions would improve your current response. Memory: when the user says "记住这个", "remember this", "写入记忆", "save this conclusion", or when you determine a retrieval result contains a conclusion worth persisting.
allowed-tools
Read, Bash(obelisk:*), Write

obelisk

Retrieve local coding-agent history through the installed obelisk CLI. Write a bounded JS query, read its JSON result, then answer from evidence.

Retrieval workflow

  1. Choose the narrowest project, file, session, time range, or topic scope. Read the matching reference below before writing the query.
  2. Normally start a new task with overview({ limit: 6 }); skip orientation for an exact session ID, message UUID, or absolute file path. Overview is a navigation map, not evidence.
  3. Recall prior conclusions with memories() and verify against session evidence with search() or scoped helpers. Use English memory query terms. Expand selected hits with messages() rather than loading entire sessions.
  4. Group, deduplicate, and project inside the query. Return stable IDs and short snippets; keep synthesis JSON around 10k–12k characters when possible.
  5. Answer with concise evidence. Identify prior memories naturally when they influence the answer. Offer to save a durable, new conclusion; wait for approval before writing the memory file or changing memory records.

Treat is_invoking: true as your current session, not independent historical evidence. Ordinary conversation evidence uses visible, non-meta text; thinking and tool output have different evidentiary roles. Read retrieval semantics before querying those surfaces or superseded branches.

Run a query

Use a unique temporary directory so the query path cannot collide:

bash
qdir=$(mktemp -d /tmp/obq.XXXXXX 2>/dev/null || { d="/tmp/obq.$$.$RANDOM"; mkdir "$d"; echo "$d"; })
qfile="$qdir/query.mjs"
cat > "$qfile" <<'JS'
const hits = search('auth fix', { limit: 5 });
return hits.map(h => ({
  session_id: h.session.id, uuid: h.message.uuid,
  content_type: h.message.content_type,
  snippet: h.message.text?.slice(0, 240),
}));
JS
obelisk --query "$qfile"

The CLI runs the file in an async wrapper; return emits JSON. Queries are read-only, with no filesystem or network access inside the script. For broad history, adapt the first-pass recipe in query patterns instead of this tiny keyword example.

For a quick keyword lookup:

bash
obelisk --search "keyword" --nonce "obq-<unique-token-you-invent>"

Type a unique literal nonce: shell substitutions cannot identify the invocation in the transcript. Query-file identity resolves through its recorded path or script content.

Fresh index and permissions

A successful CLI invocation is required: it refreshes ~/.obelisk/obelisk.sqlite before retrieval. Never degrade to a stale, read-only index when refresh fails.

If the command fails with a write-permission error for ~/.obelisk (such as SQLITE_READONLY, EACCES, or EPERM), rerun the same command with sandbox_permissions: "require_escalated", or the host's equivalent write permission mechanism. If access is unavailable or denied, stop and report the blocker. Direct SQLite or JSONL reads do not substitute for a successful refresh.

Show full SKILL.md (263 more words)Show less

Choose helpers

The default retrieval surface is:

HelperPurpose
overviewOrient to projects and recent entry points.
sessionsLocate sessions under structural filters.
searchFind message evidence by topic.
messagesRead one message, a bounded window, or a session interval (CLI 0.3.0+).
memoriesRecall previously saved conclusions.
summariesRead recorded session summaries.
sqlExpress joins or aggregations the other helpers cannot.

Specialized and legacy helpers remain callable; read their API contracts when needed. Check uncertain option names and row fields before relying on them.

Load references by task

Load only the references needed for the current task. Each reference owns its contracts or recipes; do not preload the whole directory.

Before doing thisRead
Broad synthesis, design history, progress summaries, ordinary weekly/monthly reviews, or what the user did, learned, decided, tried, or abandonedQuery patterns and retrieval semantics.
Scoped project/file/session searches, multi-step retrieval, correlation, or evidence classificationRetrieval semantics.
Choosing helper options, fields, paging, or specialized/legacy helpersAPI reference; for message expansion, the messages contract.
Writing raw SQLSchema before execution.
Saving, archiving, or updating memoryMemory workflow before writing files or running a mutation.
Workflow-specific retrievalAdvanced helpers.
Recovering from an error or resolving FTS, ordering, row-shape, or raw-record surprisesPitfalls.
Explicit /obelisk recap ...Recap overview before the first query, then follow its card-by-card disclosure.

Route to recap only when the first word after /obelisk is recap; ordinary weekly/monthly summaries do not select that workflow.

Approved memory changes run locally through a separate mutation entry point: obelisk --attune /tmp/register-memory.mjs. Retrieve the necessary IDs first with --query; --attune exposes only remember() and forget().

© tommy0103, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 20 other files (references) in skill-doc of tommy0103/obelisk.

  • SKILL.md
  • references/advanced-helpers.md
  • references/api-reference.md
  • references/memory-workflow.md
  • references/pitfalls.md
  • references/query-patterns.md
  • references/recap-patterns.md
  • references/recap-writing.md
  • references/recap/overview.md
  • references/recap/pattern1-cover.md
  • references/recap/pattern2-thinking.md
  • references/recap/pattern3-vibe.md
  • references/recap/pattern4-workflow.md
  • references/recap/pattern5-closing.md
  • references/recap/writing1-cover.md
  • references/recap/writing2-thinking.md
  • references/recap/writing3-vibe.md
  • references/recap/writing4-workflow.md
  • references/recap/writing5-closing.md
  • … and 2 more

Open the folder on GitHubat commit a4b7329

Compare with similar skills

Obelisk next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Obelisk compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Obelisk this skilltommy0103/obelisk571—~1.6kAutomated safety check: PassAGPL-3.0
CCS Task Delegationkaitranntt/ccs2.9k—~1.8kAutomated safety check: PassMIT
Helmor Bump Vendorsdohooo/helmor1.3k—~2.1kAutomated safety check: PassApache-2.0
Kimi Code DelegationCherryHQ/cherry-studio53k—~504Automated safety check: PassAGPL-3.0
MetaBot Agent Teams CLIxvirobotics/metabot994—~693Automated safety check: PassMIT
Crossreviewcoddy-project/coddy-agent168—~3.3kAutomated safety check: PassMIT

Similar skills

  • CCS Task Delegation

    kaitranntt/ccs

    Hands simple, deterministic tasks such as typo fixes, tests and small refactors to cheaper models through the ccs CLI, choosing a profile from your config.

    2.9k GitHub stars~1.8k tokensUpdated 10 days ago
    Agent WorkflowsAuto-check passed
  • Helmor Bump Vendors

    dohooo/helmor

    Bump or upgrade the pinned versions of Helmor's bundled agent CLIs, SDKs, and supporting binaries — Claude Code + claude-agent-sdk (lockstep), Codex, Cursor SDK, OpenCode, Kimi, Pi, and gh / glab /…

    1.3k GitHub stars~2.1k tokensUpdated 1 mo ago
    Agent WorkflowsAuto-check passed
  • Kimi Code Delegation

    CherryHQ/cherry-studio

    Delegates one bounded repository task to Kimi Code in non-interactive prompt mode and reads back the final result from its JSON event stream.

    53k GitHub stars~504 tokensUpdated today
    Agent WorkflowsAuto-check passed
  • MetaBot Agent Teams CLI

    xvirobotics/metabot

    Documents the metabot teams command surface for creating durable teams, spawning teammates, dispatching tasks and inspecting their runs across engine sessions.

    994 GitHub stars~693 tokensUpdated 25 days ago
    Agent WorkflowsAuto-check passed
  • Crossreview

    coddy-project/coddy-agent

    Run when the user invokes /crossreview (or /crossreview:setup to choose the reviewers) or asks for a cross-review, a quorum review or a second opinion from other agents or models: fan a code review…

    168 GitHub stars~3.3k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Kimi Datasource

    MoonshotAI/kimi-code

    Universal data-source assistant for stocks (Wind, S&P, SEC EDGAR), macro (World Bank, IMF, FRED, NBS), Chinese government data and standards (GB/HB/DB/TT), corporate, academic, legal, WHO/FAO/OECD…

    7.8k GitHub stars~1.8k tokensUpdated today
    Agent WorkflowsAuto-check passed

More from tommy0103/obelisk

  • Obelisk

    tommy0103/obelisk

    Search and query past Claude Code, Codex, Kimi Code, Kiro, and Pi session history.

    571 GitHub stars~6.5k tokensUpdated yesterday
    Auto-check passed
  • Adapter Review

    tommy0103/obelisk

    Review a provider/agent adapter implementation or PR — transcript discovery, parsing, and indexing for agent hosts (Claude, Codex, Kimi, Pi, DeepSeek Harness, OMP, Copilot, etc.).

    571 GitHub stars~1.4k tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Obelisk

What does Obelisk do?

Search and query past Claude Code, Codex, Kimi Code, Kiro, OMP, and Pi session history. Obelisk is an agent skill from tommy0103/obelisk. Search and query past Claude Code, Codex, Kimi Code, Kiro, OMP, and Pi session history.

When should I use Obelisk?

Obelisk fits situations like: asks how did I fix X; what did we do last time; find the session where; references past work you lack context for.

How do I install Obelisk in Claude Code?

Run `npx skills add tommy0103/obelisk --skill obelisk -a claude-code`. Or copy the skill folder (skill-doc in tommy0103/obelisk) into .claude/skills/obelisk in your project. Claude Code loads it when a task matches its description.

How do I install Obelisk in Codex?

Run `npx skills add tommy0103/obelisk --skill obelisk -a codex`. Or copy the skill folder (skill-doc in tommy0103/obelisk) into .agents/skills/obelisk in your project. Codex loads it when a task matches its description.

Can I use Obelisk in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add tommy0103/obelisk --skill obelisk -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/obelisk, .gemini/skills/obelisk, .github/skills/obelisk and .opencode/skills/obelisk in your project.

What does Obelisk need to run?

SKILL.md names no scripts, command-line tools or credentials: Obelisk is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Bash(obelisk:*), Write.

Does Obelisk access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Obelisk safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Obelisk use?

Obelisk is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Obelisk use?

About 1.6k tokens (SKILL.md is roughly 6.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 24k tokens, read only when the agent opens those files.

What are the alternatives to Obelisk?

Skills that share tags, products or a category with Obelisk: CCS Task Delegation (kaitranntt/ccs, 2.9k stars), Helmor Bump Vendors (dohooo/helmor, 1.3k stars), Kimi Code Delegation (CherryHQ/cherry-studio, 53k stars) and MetaBot Agent Teams CLI (xvirobotics/metabot, 994 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Obelisk?

tommy0103 (a GitHub user) maintains it in tommy0103/obelisk, which has 571 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 9, 2026.

Source: tommy0103/obelisk on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.