Using Entire
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).
Install
/plugin marketplace add entireio/skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add entireio/skills --skill using-entiregit clone --depth 1 https://github.com/entireio/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/skills/using-entire ~/.claude/skills/using-entirePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# 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 ```
Details
- Skill name
using-entire- Repository
- entireio/skills
- Path
skills/using-entire/SKILL.md- License
- MIT
- Repo updated
- 15 November 2026
FAQ
What does the Using Entire skill 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 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).
How do I install the Using Entire skill?
Claude Code plugin: /plugin marketplace add entireio/skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Using Entire popular?
It lives in entireio/skills, which has 240 GitHub stars and 28 forks.
Related skills
Address Findings
240entireio/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. Use when the user gives a trail URL or number and asks to address, fix, or resolve its findings or review comments. Not for local diff review — that is the `review` skill.
Explain
240entireio/skills
Explains the intent behind source code by finding original session transcripts. Use explain with a function, file, or line of code to understand why it exists.
Recall
240entireio/skills
Use 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. Triggers on phrases like "have we done this before", "recall how we did X", "find similar work", "any precedent for", "has anyone solved", "is there a template for", and "how did we do this last time
Setup Solidity Contracts
223OpenZeppelin/openzeppelin-skills
Set up a Solidity smart contract project with OpenZeppelin Contracts. Use when users need to: (1) create a new Hardhat or Foundry project, (2) install OpenZeppelin Contracts dependencies for Solidity, (3) configure remappings for Foundry, or (4) understand Solidity import conventions for OpenZeppelin.
Databricks Metric Views
407databricks/databricks-agent-skills
Unity Catalog metric views: define, create, query, and manage governed business metrics in YAML. Use when building standardized KPIs, revenue metrics, order analytics, or any reusable business metrics that need consistent definitions across teams and tools.
Polymarket Trading
271machina-sports/sports-skills
High-risk Polymarket trading operations — configure wallet-backed CLOB access, place limit/market orders, cancel orders, and view account-specific orders/trades. Requires py-clob-client-v2 and a user-controlled wallet. Use only when the user explicitly asks to trade or manage orders in the current session. Do not use for read-only odds, probabilities, market search, or event discovery — use the `polymarket` skill instead. Do not ask the user to paste private keys into chat. Do not place or cancel orders without explicit confirmation of token_id, side, price/amount, and size.
Browse the most popular Claude skills, all finance & crypto skills, or write your own with the skills generator.