All authors
Claude Skills by wilbeibi
github.com/wilbeibi22 skills4 installs90 views
- catchupRecovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.Votes: 1GitHub stars: 74
- Code ReviewReview a diff, package, or API through one of five lenses — necessity and layering (Russ Cox), honest invariants and costs (BurntSushi), product-versus-library fit (Mitsuhiko), a complexity gate before a design change, or newcomer clarity. Use when asked to review, audit, or polish code, vet a dependency, judge whether a change is too complex, or find what a new hire would not understand.Votes: 0GitHub stars: 2
- DatavizDesign and implement evidence-first charts from real data for technical blogs, reports, READMEs, and product explainers. Use when asked for a benchmark graph, data illustration, performance chart, tradeoff plot, small multiple, or an editorial chart in React/Recharts or a static plotting stack. Do NOT use for text-only diagrams (use show-me), hand-drawn conceptual art (use sketch-concept), or dashboard UI design.Votes: 0GitHub stars: 2
- Grill MeInterview the user one question at a time until a plan is resolved, capturing durable decisions in CONTEXT.md or ADRs when the repo warrants it. Use when asked to "grill me," stress-test a design, or challenge assumptions before implementation.Votes: 0GitHub stars: 2
- Grok RepoExplain an unfamiliar codebase through a repository briefing, dataflow trace, or reconstruction of why and how a change was made. Use when asked for a repo tour, how something works, where a value comes from, or why a feature changed. Not for repo health (use repo-eval).Votes: 0GitHub stars: 2
- HammerspoonOperate macOS via Hammerspoon, either one-off `hs -c` Lua (launch, quit, or focus apps and browser tabs; volume, wifi, caffeinate, alerts, clipboard) or persistent hotkeys, watchers, and menubar items in ~/.hammerspoon. Use when asked to control an app, tab, or Mac system state, keep the Mac awake, or write a Hammerspoon module. Not for web page content.Votes: 0GitHub stars: 2
- Karpathy PlanningDevelop a scoped implementation plan when explicitly asked to plan a coding task. Use grill-me for a deliberate design interview.Votes: 0GitHub stars: 2
- Obsidian CaptureAppend todos, logs, learnings, and reflections to Obsidian daily or weekly notes and run the agent's #agent-todo queue via scripts/capture.py. Use when asked to add a todo, note something down, log this, capture an idea, set a due date, record a weekly reflection, or list or close the agent's tasks ("看你的 todo", "干活"). Not for searching notes (use obsidian-search) or standalone long-form notes.Votes: 0GitHub stars: 2
- Obsidian SearchSearch an Obsidian vault for topics, exact text, tags, recent notes, and tasks. Use when fuzzy, date-aware, due, or overdue note retrieval is needed.Votes: 0GitHub stars: 2
- Paper SearchFind and rank research papers by relevance, recency, field-adjusted impact, venue, and author affiliation. Use when searching AI, agents, runtimes, storage, databases, infrastructure, recent or superseding work, company or lab research, or evidence for technical claims. Do NOT use for general web search or GitHub repository evaluation.Votes: 0GitHub stars: 2
- ReadbackPut a long reply of your own - or a plan, document, or session transcript - on an HTML page the user reads, highlights, and comments on, returning their notes as a follow-up prompt through a waiting local command. Use when your answer is too long to review in a terminal, when the user wants to mark up or annotate a document, or when you want line-level feedback on a plan before implementing it. Do NOT use to collect answers to specific open decisions or to interview the user one question at a...Votes: 0GitHub stars: 2
- Repo EvalEvaluate a public GitHub repository's momentum and maintenance health. Use when asked whether a repository is healthy, growing, declining, abandoned, or well maintained, or when vetting dependencies and OSS projects. Do NOT use for code or architecture review.Votes: 0GitHub stars: 2
- Route SkillDiscovers skills in the wilbeibi-skills catalog and loads explicitly selected skills from local files or cache, fetching missing skills. Use when asked to use an unavailable skill by name, find a suitable skill, or when available capabilities are insufficient and a catalog skill could fill the specific gap. Do NOT treat a question about a skill as permission to use it.Votes: 0GitHub stars: 2
- SherlockWork an open question like a case — graded clues, competing theories in a consistency matrix, eliminate by evidence, backtrack, converge, with a casebook on disk for long cases. Use for puzzling bugs, reverse-engineering how a product works from public signals, or "what actually happened here". Do NOT use for planning (use karpathy-planning), repo tours (use grok-repo), or diff review.Votes: 0GitHub stars: 2
- Show MeExplain code structure, dataflow, or proposed changes with a compact tree, pseudocode, type signature, diff, or diagram. Use when a visual clarifies those relationships; whole-repo briefings belong to grok-repo.Votes: 0GitHub stars: 2
- Sketch ConceptGenerate a playful hand-drawn illustration that explains one technical mechanism or data insight — architecture, concurrency, storage, caching, queues, retries — for a blog post, doc, or slide. Use when asked for an illustration, a hand-drawn or Excalidraw-style visual, or a picture that makes one engineering idea click. Do NOT use for answering in-chat with a text diagram (use show-me) or for charts of real data (use dataviz).Votes: 0GitHub stars: 2
- Skill CuratorAudit a skill library for duplicated guidance, contradictions, bloat, dead references, and defects. Use when cleaning, consolidating, or de-duplicating a skills tree.Votes: 0GitHub stars: 2
- Test WritingWrites, reviews, and prunes tests so the committed suite protects contracts and invariants rather than implementation. Use when writing or reviewing tests, choosing a test seam, scope, or mocks, adding property, fuzz, or regression tests, fixing brittle tests, auditing a bloated suite, or deciding whether a failing test means the code or the test is wrong. Do NOT use for TLA+ model checking (use tla-model).Votes: 0GitHub stars: 2
- Web RecapSearch browser history for URLs by topic or visit statistics. Use when asked about visited sites, browsing history, or recent online activity. Do NOT use for project/git recaps or agent-session history.Votes: 0GitHub stars: 2
- Write DocsWrite or critique prose that ships with a codebase — READMEs, developer guides and runbooks, CLI text, code comments, agent guides, and commit or PR descriptions. Use when drafting, improving, or reviewing these artifacts. Do NOT use for design docs or internal wikis.Votes: 0GitHub stars: 2
- Write SkillAuthor or update compact agent skills under skills/<name>/SKILL.md. Use when asked to write, add, or change a skill; not to audit a skill library.Votes: 0GitHub stars: 2
- Tla ModelModels concurrent and distributed designs in TLA+ or PlusCal and checks them with the TLC model checker. Use when asked to write, review, or debug a TLA+ spec, .tla/.cfg files, or TLC output, or to model-check or formally verify a protocol, lock, lease, consensus, replication, WAL, retry, or race condition. Do NOT use for unit or property-based tests (use test-writing) or for Lean, Coq, Dafny, or Verus proofs.Votes: 0GitHub stars: 2