skills

In the author's own words, from each skill's SKILL.md.

• address-findings

  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.

  skills/address-findings/SKILL.md on GitHub (opens in a new tab)

• explain

  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.

  skills/explain/SKILL.md on GitHub (opens in a new tab)

• recall

  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"

  skills/recall/SKILL.md on GitHub (opens in a new tab)

• replay

  Use when the user wants to step through a feature's checkpoints chronologically, pausing at each step to ask questions. Triggers on phrases like "replay <feature>", "walk me through how X was built", "show me the journey of", "step me through how Y was implemented", and "replay the last week"

  skills/replay/SKILL.md on GitHub (opens in a new tab)

• review

  Review code changes on the current branch using checkpoint transcript context to understand developer intent before auditing the diff. Use when the user asks for a code review, wants to review branch changes, or asks to audit recent work before merging.

  skills/review/SKILL.md on GitHub (opens in a new tab)

• search

  Use 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". Invoke this as the FIRST action on such requests, before Glob, Grep, or Read: the answer is in Entire's recorded history (prompts, transcripts, and decisions, across repos), not in the local files, and a working copy that looks empty or unfa…

  skills/search/SKILL.md on GitHub (opens in a new tab)

• session-crosslink

  Use when an agent session ran outside the repo whose commits should record it — e.g. launched from a higher-level folder, a non-Entire repo, or one repo but editing another — to attach the session to each affected Entire-enabled repo's HEAD commit.

  skills/session-crosslink/SKILL.md on GitHub (opens in a new tab)

• session-handoff

  Use when the user wants to continue work from one agent in another agent, inspect recent sessions, or summarize a saved session or checkpoint for handoff

  skills/session-handoff/SKILL.md on GitHub (opens in a new tab)

• session-to-skill

  Use when the user wants to turn one or more Entire-tracked sessions, checkpoints, or repeated agent workflows into a reusable agent skill.

  skills/session-to-skill/SKILL.md on GitHub (opens in a new tab)

• teach

  Use when a developer wants a topic-focused guided lesson built from canonical checkpoints, not a whole-repo overview. Triggers on phrases like "teach me <topic>", "teach me how this repo handles", "how does <topic> work in this repo", "give me a lesson on", "school me on", and "I need to learn about"

  skills/teach/SKILL.md on GitHub (opens in a new tab)

• 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…

  skills/using-entire/SKILL.md on GitHub (opens in a new tab)

• what-happened

  Explain why code looks the way it does by tracing the latest change for a file range or pasted snippet through `git blame` and deduplicated `entire checkpoint explain` lookups. Use when the user asks what happened, says "tell me why" about a code block, is confused about a section of code, asks "wtf is going on", "why is this like this", "why was this changed", or wants provenance for a specific…

  skills/what-happened/SKILL.md on GitHub (opens in a new tab)

No skill matches that filter.

Similar skills

• superpowersby obra An agentic skills framework & software development methodology that works. 300k stars · 15 skills
• agent-skillsby addyosmani Production-grade engineering skills for AI coding agents. 107k stars · 25 skills
• skillsby google Agent Skills for Google products and technologies 21.3k stars · 30 skills
• garden-skillsby ConardLi ConardLi's open-source Skills collection, featuring web design, knowledge retrieval, image generation, and more. 12.9k stars · 5 skills
• ui-skillsby ibelick Skills for Design Engineers 9.8k stars · 7 skills
• Claude-Redby SnailSploit claude-red is a curated library of offensive security skills designed for the Claude skills system. Each skill is a structured SKILL.md fil… 7.5k stars · 30 skills