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

Using Entire

by entireio in entireio/skills

Use as the FIRST action on any research, investigation, or codebase-understanding request — "research X", "investigate X", "look into X", "dig into X", "search X", "explore X", "understand X", "why…

MITAuto-check passedAgent Workflows

Install Using Entire

skills CLI
$ npx skills add entireio/skills --skill using-entire -a claude-code

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

GitHub CLI
$ gh skill install entireio/skills using-entire --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/entireio/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/using-entire .claude/skills/using-entire && 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
using-entire
GitHub stars
223
Token cost
~1.8k tokens
SKILL.md length
917 words
Files
1
Skills in repo
12
Repo updated
First seen
Licence
MIT

At a glance

Use as the FIRST action on any research, investigation, or codebase-understanding request — "research X", "investigate X", "look into X", "dig into X", "search X", "explore X", "understand X", "why…

  • Works in 2 steps: Identify key files in the target area… → Check for checkpoint coverage on each…
  • Tasks that involve Session handoff
  • SKILL.md covers When This Skill Activates, First Step: Check Repository…, Scenario Routing and General Exploration Flow, plus 4 more sections
  • Calls git

What it does

Using Entire is an agent skill from entireio/skills. Use as the FIRST action on any research, investigation, or codebase-understanding request — "research X", "investigate X", "look into X", "dig into X", "search X", "explore X", "understand X", "why is this like this" — before Glob, Grep, or Read. Recorded intent lives in Entire checkpoints on the server, not in local files, so an empty or unfamiliar working copy is not a reason to skip it. Routes to the right Entire sub-skill (search, recall, explain, what-happened, replay, teach, review, session-handoff).

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows, covering Session handoff. The repository describes itself as: ✨ Cross-agent skills that help coding agents use Entire context from Checkpoints, sessions, and git history to search past work, explain code, and hand off sessions. The licence is MIT.

When your agent uses it

  • Tasks that involve Session handoff

Example prompts

  • “research X”
  • “investigate X”
  • “look into X”
  • “/using-entire”

Workflow steps

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

  1. Identify key files in the target area (entry points, main types, core
  2. Check for checkpoint coverage on each key file

What it can do on your machine

Read from SKILL.md and the folder at commit fe5266f. 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

    Shell commands in SKILL.md call:

    • git

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

  • Network

    Links to these hosts (documentation or services it may open):

    • docs.entire.io
    • llmstxt.org

    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

Using Entire loads about 1.8k tokens when it runs. Until then it costs about 131 tokens; SKILL.md has 917 words of instructions outside code blocks.

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

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 entireio/skills at commit fe5266f, republished under its MIT licence (© entireio). 917 words, ~1,831 tokens.

Download SKILL.mdSave it as .claude/skills/using-entire/SKILL.md (or your agent's skills folder).
name
using-entire
description
Use as the FIRST action on any research, investigation, or codebase-understanding request — "research X", "investigate X", "look into X", "dig into X", "search X", "explore X", "understand X", "why is this like this" — before Glob, Grep, or Read. Recorded intent lives in Entire checkpoints on the server, not in local files, so an empty or unfamiliar working copy is not a reason to skip it. Routes to the right Entire sub-skill (search, recall, explain, what-happened, replay, teach, review, session-handoff).

Using Entire

Your default when exploring or understanding code should be: read the recorded intent, don't guess.

Entire checkpoints capture the prompts, transcripts, and decisions behind every agent-driven change. When you need to understand why code exists or how a module evolved, look up the checkpoint history first. Only fall back to inference from code structure when no history is available — and label that explicitly.

When This Skill Activates

Use this skill whenever the task involves:

  • A request phrased as "research X", "investigate X", "look into X", "dig into X", or "find out how X works"
  • Exploring or understanding an unfamiliar module or file
  • Preparing to refactor, extend, or debug code you didn't write
  • Answering "why is this like this?" or "what was the intent?"
  • Doing pre-work research before making changes
  • Any codebase exploration where historical context would help

For a research- or investigate-shaped request, the very first action is an entire search via the search skill. Do not open source files or grep first; the recorded history says what was tried and why, and code reads come after to confirm it.

Do not use this skill for simple, well-understood edits where you already have full context (e.g. "add a comment to line 5").

First Step: Check Repository Status

Before diving into specific lookups, check whether Entire is available and the repository has checkpoint history:

bash
entire status

This tells you whether Entire is enabled, which git hooks are installed, whether the metadata branch is initialized, and any active sessions on the current branch.

Scenario Routing

When this skill activates, determine which sub-skill best fits the user's need:

ScenarioTypical user expressionsDelegate to
Code block provenance"why is this like this" / "wtf is going on" / "what happened at src/auth.ts:42" / "tell me why this changed"what-happened
Research or investigate a topic"research X" / "investigate X" / "look into X" / "dig into X" / "what do we know about X"search first, then this skill's exploration flow if needed
Find prior work"has anyone done X before" / "search past work for rate limiting" / "find the previous implementation"search
Recall a task playbook"have we done this before" / "recall how we did X" / "how did we do this last time"recall
Replay feature history"replay <feature>" / "walk me through how X was built" / "show me the journey of Y"replay
Teach a repo topic"teach me <topic>" / "how does <topic> work in this repo" / "give me a lesson on X"teach
Understand original intent"explain this function" / "explain parseConfig" / "what was the intent behind src/auth.ts"explain
Generate a dispatch / summary"summarize recent work" / "generate a dispatch" / "what was accomplished this week"run entire dispatch directly
Code review with intent context"review these changes" / "review this branch" / "audit before merging"review
Hand off to another agent"hand off this session" / "continue in another agent" / "pick up the codex session"session-handoff
Convert session to skill"turn this into a skill" / "make a skill from this session"session-to-skill
Link session to other repos"link session to other repos" / "attach session to the foo repo"session-crosslink
General exploration"understand this module" / "explore how auth works" / "help me understand the codebase"(self — see below)

If the scenario clearly maps to a sub-skill, delegate entirely to that skill's workflow. Do not duplicate their steps here.

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

General Exploration Flow

When no specific sub-skill fits — e.g. the user asks to "understand this module" or "explore how auth works" — use this flow:

  1. Identify key files in the target area (entry points, main types, core functions).

  2. Check for checkpoint coverage on each key file:

bash
git log --format='%H %s' -5 -- <file>

Look for Entire-Checkpoint: trailers in the commit bodies:

bash
git log --format='%H %b' -5 -- <file> | grep -B1 'Entire-Checkpoint:'
  1. Read intent for covered commits — extract the checkpoint ID from the trailer, then use JSON output for non-interactive consumption:
bash
entire checkpoint explain --checkpoint <checkpoint-id> --json --no-pager

If you only have a commit hash (not a checkpoint ID), use:

bash
entire checkpoint explain --commit <sha> --no-pager

  1. Synthesize: combine the recorded intent (from checkpoints) with the current code structure to build a comprehensive understanding.

  2. Report your findings, clearly distinguishing:

    • Facts backed by checkpoint transcripts (label as "recorded intent")
    • Observations inferred from code alone (label as "inferred from code")

AI Agent Usage Notes

When running Entire commands from an agent subprocess:

  • Always pass --json for commands that support it and might prompt interactively. --json implies non-interactive output.
  • Always pass --no-pager to prevent pager activation in subprocess contexts.
  • Always specify --checkpoint <id> or --commit <sha> for entire checkpoint explain — without a locator, the command falls back to an interactive picker.

When No Checkpoints Exist

If the target code predates Entire or has no checkpoint coverage:

  1. Say explicitly: "No Entire checkpoint history is available for this code."
  2. Proceed with standard code understanding (read source, check git log, trace call sites).
  3. Label all explanations as "inferred from code — not backed by recorded intent."
  4. If the user wants deeper history, suggest search with related keywords — there may be checkpoints on related work even if the specific file isn't directly covered.

Transparency Principle

Always make it clear whether your answer comes from:

  • Checkpoint-backed history — you read the actual session transcript and know the developer's stated intent
  • Code inference — you analyzed the code structure and are reasoning about probable intent

Never present inferred intent as if it were recorded fact. The core value of this workflow is that distinction.

References

For a deeper understanding of Entire's capabilities beyond what the sub-skills cover, consult these resources:

  • CLI help: run entire help to see all available commands and flags
  • Documentation: https://docs.entire.io/llms.txt — AI-friendly documentation index following the llms.txt standard, designed to be consumed directly by LLMs and coding agents

© entireio, MIT. 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 skills/using-entire of entireio/skills.

Open the folder on GitHubat commit fe5266f

Compare with similar skills

Using Entire 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.

Using Entire compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Using Entire this skillentireio/skills223—~1.8kAutomated safety check: PassMIT
Orca CLIstablyai/orca88k2 repos~593Automated safety check: PassMIT
Beads Task Memorygastownhall/beads28k—~1.2kAutomated safety check: PassMIT
Session History Searchslopus/happy24k—~3.1kAutomated safety check: PassMIT
Paseo Agent Handoffgetpaseo/paseo20k1 repos~606Automated safety check: PassCustom licence
Memori Long-Term MemoryMemoriLabs/Memori17k—~2kAutomated safety check: NotesCustom licence

Similar skills

  • Orca CLI

    stablyai/orca

    Operate Orca-managed worktrees, folder contexts, terminals, repos, automations, artifacts, skill sharing, worktree comments, and Orca's embedded browser…

    88k GitHub starsUsed in 2 repos~593 tokens
    Agent WorkflowsAuto-check passed

  • Beads Task Memory

    gastownhall/beads

    Tracks multi-session work with dependencies in the bd issue tracker so the agent can find ready tasks and recover its context after conversation compaction.

    28k GitHub stars~1.2k tokensUpdated today
    Agent WorkflowsAuto-check passed

  • Session History Search

    slopus/happy

    Searches past Claude Code, Codex and Cursor sessions and summarizes what was worked on, tried or decided, using extraction scripts instead of reading raw logs.

    24k GitHub stars~3.1k tokensUpdated today
    Agent WorkflowsAuto-check passed

  • Paseo Agent Handoff

    getpaseo/paseo

    Hands off the current task, including context, decisions and failed attempts, to a fresh agent through Paseo by writing a self-contained briefing prompt and launching that agent.

    20k GitHub starsUsed in 1 repo~606 tokens
    Agent WorkflowsAuto-check passed

  • Memori Long-Term Memory

    MemoriLabs/Memori

    Connects Claude Code to Memori Cloud for long-term memory, recalling stored context before substantive replies and saving new context afterward.

    17k GitHub stars~2k tokensUpdated 7 days ago
    Agent WorkflowsAuto-check: notes

  • Beads

    liwp/again

    A skill your agent uses when working in a repository that uses bd or Beads for durable project task tracking, issue dependencies, blocker management, multi-session handoff, or shared work memory.

    118 GitHub starsUsed in 6 repos~537 tokens
    Agent WorkflowsAuto-check passed

More from entireio/skills

All 12 skills in this repo

  • Review

    entireio/skills

    Review code changes on the current branch using checkpoint transcript context to understand developer intent before auditing the diff.

    223 GitHub stars~1.9k tokensUpdated 10 days ago
    Auto-check passed

  • Address Findings

    entireio/skills

    Address the review findings posted on an Entire trail: fetch the trail's open findings, fix the code, and resolve them on the trail.

    223 GitHub stars~1.6k tokensUpdated 10 days ago
    Auto-check passed

  • Recall

    entireio/skills

    A skill your agent uses when the user describes a task and wants to know whether something similar has been done before, then turn the closest prior session into a task playbook.

    223 GitHub stars~1.6k tokensUpdated 10 days ago
    Auto-check passed

  • Replay

    entireio/skills

    A skill your agent uses when the user wants to step through a feature's checkpoints chronologically, pausing at each step to ask questions.

    223 GitHub stars~1.7k tokensUpdated 10 days ago
    Auto-check passed

  • Search

    entireio/skills

    A skill your agent uses when the user asks to research, investigate, look into, dig into, or search for anything — a topic, feature, bug, decision, or "what do we know about X".

    223 GitHub stars~2.1k tokensUpdated 10 days ago
    Auto-check passed

  • Session Crosslink

    entireio/skills

    A skill your agent uses when an agent session ran outside the repo whose commits should record it — e.g.

    223 GitHub stars~2k tokensUpdated 10 days ago
    Auto-check passed

Categories

Questions about Using Entire

What does Using Entire do?

Use as the FIRST action on any research, investigation, or codebase-understanding request — "research X", "investigate X", "look into X", "dig into X", "search X", "explore X", "understand X", "why…. Using Entire is an agent skill from entireio/skills. Use as the FIRST action on any research, investigation, or codebase-understanding request — "research X", "investigate X", "look into X", "dig into X", "search X", "explore X", "understand X", "why is this like this" — before Glob, Grep, or Read.

When should I use Using Entire?

Using Entire fits situations like: tasks that involve Session handoff.

How do I install Using Entire in Claude Code?

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

How do I install Using Entire in Codex?

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

Can I use Using Entire 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 entireio/skills --skill using-entire -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/using-entire, .gemini/skills/using-entire, .github/skills/using-entire and .opencode/skills/using-entire in your project.

What does Using Entire need to run?

Going by SKILL.md and its folder, Using Entire needs the command-line tools its instructions call (git).

Does Using Entire access the network?

SKILL.md names 2 domains. As links in the text: docs.entire.io and llmstxt.org. This is read from the text; nothing was executed.

Is Using Entire 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 Using Entire use?

Using Entire is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Using Entire use?

About 1.8k tokens (SKILL.md is roughly 7.3k 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 Using Entire?

Skills that share tags, products or a category with Using Entire: Orca CLI (stablyai/orca, 88k stars), Beads Task Memory (gastownhall/beads, 28k stars), Session History Search (slopus/happy, 24k stars) and Paseo Agent Handoff (getpaseo/paseo, 20k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Using Entire?

entireio (a GitHub organization) maintains it in entireio/skills, which has 223 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on September 29, 2026.

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