New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

TMA1 Session Search

by tma1-ai in tma1-ai/tma1

Searches past agent sessions on a project by keyword through the TMA1 MCP server and reads back a chosen session so answers can quote it directly.

Apache-2.0Auto-check passedAgent Workflows

Install TMA1 Session Search

skills CLI
$ npx skills add tma1-ai/tma1 --skill tma1-search -a claude-code

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

GitHub CLI
$ gh skill install tma1-ai/tma1 tma1-search --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/tma1-ai/tma1.git skills-src && mkdir -p .claude/skills && cp -r skills-src/claude-plugin/codex-skills/tma1-search .claude/skills/tma1-search && 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
tma1-search
GitHub stars
119
Token cost
~766 tokens
SKILL.md length
312 words
Files
1
Skills in repo
5
Repo updated
First seen
Licence
Apache-2.0

At a glance

Searches past agent sessions on a project by keyword through the TMA1 MCP server and reads back a chosen session so answers can quote it directly.

  • Works in 4 steps: Search — call the tma1 MCP server's… → Report the matches with their snippets… → Read — get_session_transcript with the… → …
  • Finding how a problem was fixed in an earlier agent session
  • SKILL.md covers Invocation, Workflow, Reading the response and Related tools
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

TMA1 keeps every agent session on the machine, yours and other agents', in a local database, and this skill is the read path: find the session, then read it. A command like `/tma1-search retry backoff` searches the current project over the last 7 days, `--agent` narrows to one agent, `--days` widens the window and `--session` takes a full ID or a prefix of at least 6 characters. A bare token is never treated as a session ID, since commit hashes look identical.

The workflow calls the `search_sessions` tool, reports matches with snippets, then fetches the chosen session with `get_session_transcript`, paging through older messages when `has_more` is true, and answers with quotes rather than a summary. It explains the response fields: the indexed term mode matches whole words case-sensitively, the substring fallback is noisier and should be flagged, and a truncated scope means narrowing the search. When nothing matches, the agent reports that rather than inventing a plausible past session.

When your agent uses it

  • Finding how a problem was fixed in an earlier agent session
  • Recovering what was decided or what another agent tried last week
  • Reading back a session when you are handed a session ID

Example prompts

  • “Search my sessions for the retry backoff discussion and quote what we decided.”
  • “Find flaky test sessions from Claude Code in the last 30 days.”
  • “Read the session whose ID starts with that prefix and tell me how it ended.”

Requirements

  • The tma1 MCP server with its local session database

Workflow steps

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

  1. Search — call the tma1 MCP server's search_sessions tool
  2. Report the matches with their snippets so the user can pick. One
  3. Read — get_session_transcript with the chosen session_id.
  4. Answer with quotes from the earlier session, not a summary.

What it can do on your machine

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

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    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

TMA1 Session Search loads about 766 tokens when it runs. Until then it costs about 114 tokens; SKILL.md has 312 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~114
When it runs · the whole SKILL.md, loaded when a task matches
~766

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 tma1-ai/tma1 at commit f3dfed8, republished under its Apache-2.0 licence (© tma1-ai). 312 words, ~766 tokens.

Download SKILL.mdSave it as .claude/skills/tma1-search/SKILL.md (or your agent's skills folder).
name
tma1-search
description
Search past agent sessions on this project by keyword, and read back any session's conversation. Invoke this skill when the answer lives in an earlier session — how something was fixed before, what was decided, what another agent tried last week — or when the user hands you a session id. Trigger phrases: "what did we decide about", "how did we fix this before", "search my sessions", "find that session", "read session <id>", "/tma1-search".

TMA1 Session Search (Codex)

TMA1 keeps every agent session on this machine — yours and other agents' — in a local database. This skill is the read path: find the session, then read it.

Invocation

/tma1-search retry backoff             # keyword search, this project, last 7 days
/tma1-search flaky test --agent claude # only Claude Code's sessions
/tma1-search migration --days 30       # widen the window
/tma1-search pipeline --all-projects   # every project
/tma1-search --session 3d8f1d0a        # read one session directly

--session takes a full id or a prefix of 6+ characters. Do not infer a session id from a bare token: commit hashes look identical, and oc: / cp: ids don't look like hex at all. Anything not behind --session is search text.

Workflow

  1. Search — call the tma1 MCP server's search_sessions tool:
    • query: everything that isn't a flag
    • agent_source: --agent value (claude → claude_code, openclaw, copilot → copilot_cli, self); omit for every agent
    • since_min: --days N × 1440; omit for the 7-day default
    • project: "*" with --all-projects; otherwise omit
  2. Report the matches with their snippets so the user can pick. One obvious hit and a clear question → go straight to step 3.
  3. Read — get_session_transcript with the chosen session_id. has_more: true means older messages exist; call again with the returned next_offset if the answer isn't in this page.
  4. Answer with quotes from the earlier session, not a summary.

Reading the response

  • sessions[] — session_id, agent_source, last_activity_ago, hit_count, snippets[] (a window around each match).
  • match_mode — term is the indexed pass: whole words, case-sensitive. substring means that pass found nothing, so the search widened to a case-folded substring scan: noisier results, say so.
  • scope_truncated: true — more sessions exist in the window than were scanned; narrow with --agent or --days.
  • note — only when nothing matched. Report the silence; don't invent a plausible past session.

The indexed pass matches whole words and is case-sensitive: Cwd does not find peerCwdFilter, and neither does peercwdfilter. Search the identifier as written. The substring fallback folds case, which is what rescues a mistyped query.

  • Browsing by agent rather than keyword → the tma1-peer skill.
  • Aggregates over the raw tables (cost by model, tool failure rates) → the tma1 skill's exec_query.

© tma1-ai, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in claude-plugin/codex-skills/tma1-search of tma1-ai/tma1.

Open the folder on GitHubat commit f3dfed8

Compare with similar skills

TMA1 Session Search 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.

TMA1 Session Search compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
TMA1 Session Search this skilltma1-ai/tma1119—~766Automated safety check: PassApache-2.0
MemPalace Setup and OperationMemPalace/mempalace60k—~2.2kAutomated safety check: PassMIT
agentmemory Setup and Diagnosticsrohitg00/agentmemory29k—~1kAutomated safety check: NotesApache-2.0
Qmdbreferrari/obsidian-mind5k—~1.7kAutomated safety check: PassMIT
Memori MCP Memory UsageMemoriLabs/Memori17k—~3.8kAutomated safety check: PassMIT
Shared Agent Knowledge Commonsmozilla-ai/cq1.3k—~6.5kAutomated safety check: PassApache-2.0

Similar skills

  • MemPalace Setup and Operation

    MemPalace/mempalace

    Installs and configures MemPalace as a private local palace, a shared-brain hub or a client of an existing hub, including MCP registration and version-correct initialization.

    60k GitHub stars~2.2k tokensUpdated today
    Agent WorkflowsAuto-check passed

  • agentmemory Setup and Diagnostics

    rohitg00/agentmemory

    Sets up and troubleshoots a local agentmemory install, covering the MCP connection, environment variables, ports, authentication and optional feature flags.

    29k GitHub stars~1k tokensUpdated yesterday
    Agent WorkflowsAuto-check: notes

  • Qmd

    breferrari/obsidian-mind

    Search the vault using QMD semantic search. An agent skill from breferrari/obsidian-mind.

    5k GitHub stars~1.7k tokensUpdated 5 days ago
    Agent WorkflowsAuto-check passed

  • Memori MCP Memory Usage

    MemoriLabs/Memori

    Teaches an MCP-connected agent when and how to call Memori's recall, summary, compaction, augmentation, feedback and quota tools to keep context across sessions.

    17k GitHub stars~3.8k tokensUpdated 8 days ago
    Agent WorkflowsAuto-check passed

  • Shared Agent Knowledge Commons

    mozilla-ai/cq

    Queries a shared knowledge store before acting, proposes newly discovered insights, and confirms or flags existing entries, so agents stop rediscovering the same failures.

    1.3k GitHub stars~6.5k tokensUpdated 5 days ago
    Agent WorkflowsAuto-check passed

  • Ruflo Multi-Agent Orchestration

    ruvnet/ruflo

    Sets up and drives Ruflo, an npm-installed orchestration layer for multi-agent swarms, persistent memory, routing, hooks and its MCP tool catalog.

    74k GitHub starsUsed in 1 repo~975 tokens
    Agent WorkflowsAuto-check passed

More from tma1-ai/tma1

  • TMA1 Peer Sessions

    tma1-ai/tma1

    Lists recent sessions on the current project from other agents such as Claude Code, OpenClaw and Copilot CLI, or from your own earlier work.

    119 GitHub stars~1.3k tokensUpdated 2 days ago
    Auto-check passed

  • TMA1 Peer Sessions

    tma1-ai/tma1

    Lists recent sessions of peer coding agents such as Codex, OpenClaw or Copilot CLI, or your own past sessions, so you can act on their work without copying between terminals.

    119 GitHub stars~1.1k tokensUpdated 2 days ago
    Auto-check passed

  • TMA1 Session Search

    tma1-ai/tma1

    Searches earlier agent sessions on this project by keyword and reads back a session's conversation, answering with quotes from what was actually said.

    119 GitHub stars~904 tokensUpdated 2 days ago
    Auto-check passed

  • TMA1 Observability Query

    tma1-ai/tma1

    Answers questions about agent spend, token use, traces, events, errors and tool usage by running read-only SQL against a local TMA1 observability store.

    119 GitHub stars~5.1k tokensUpdated 2 days ago
    Auto-check: notes

Works with

Categories

Questions about TMA1 Session Search

What does TMA1 Session Search do?

Searches past agent sessions on a project by keyword through the TMA1 MCP server and reads back a chosen session so answers can quote it directly. TMA1 keeps every agent session on the machine, yours and other agents', in a local database, and this skill is the read path: find the session, then read it. A command like `/tma1-search retry backoff` searches the current project over the last 7 days, `--agent` narrows to one agent, `--days` widens the window and `--session` takes a full ID or a prefix of at least 6 characters.

When should I use TMA1 Session Search?

TMA1 Session Search fits situations like: finding how a problem was fixed in an earlier agent session; recovering what was decided or what another agent tried last week; reading back a session when you are handed a session ID.

How do I install TMA1 Session Search in Claude Code?

Run `npx skills add tma1-ai/tma1 --skill tma1-search -a claude-code`. Or copy the skill folder (claude-plugin/codex-skills/tma1-search in tma1-ai/tma1) into .claude/skills/tma1-search in your project. Claude Code loads it when a task matches its description.

How do I install TMA1 Session Search in Codex?

Run `npx skills add tma1-ai/tma1 --skill tma1-search -a codex`. Or copy the skill folder (claude-plugin/codex-skills/tma1-search in tma1-ai/tma1) into .agents/skills/tma1-search in your project. Codex loads it when a task matches its description.

Can I use TMA1 Session Search 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 tma1-ai/tma1 --skill tma1-search -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/tma1-search, .gemini/skills/tma1-search, .github/skills/tma1-search and .opencode/skills/tma1-search in your project.

What does TMA1 Session Search need to run?

SKILL.md names no scripts, command-line tools or credentials: TMA1 Session Search is instructions for the agent only. Our summary lists: The tma1 MCP server with its local session database.

Does TMA1 Session Search 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 TMA1 Session Search 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 TMA1 Session Search use?

TMA1 Session Search is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does TMA1 Session Search use?

About 766 tokens (SKILL.md is roughly 3.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to TMA1 Session Search?

Skills that share tags, products or a category with TMA1 Session Search: MemPalace Setup and Operation (MemPalace/mempalace, 60k stars), agentmemory Setup and Diagnostics (rohitg00/agentmemory, 29k stars), Qmd (breferrari/obsidian-mind, 5k stars) and Memori MCP Memory Usage (MemoriLabs/Memori, 17k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains TMA1 Session Search?

tma1-ai (a GitHub organization) maintains it in tma1-ai/tma1, which has 119 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 8, 2026.

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