Updated 8mo ago
by ElliotJLT
Claude-Skill-Potions
A collection of Claude skills I have concocted to optimise my Ops/Product workflows.
61 GitHub stars (61)
+1 in 16 days
| Period | New stars |
|---|---|
| Oct 1 | 0 |
| Oct 2 | 0 |
| Oct 3 | 0 |
| Oct 4 | 0 |
| Oct 5 | 0 |
| Oct 6 | 0 |
| Oct 7 | 0 |
| Oct 8 | 0 |
| Oct 9 | 0 |
| Oct 10 | 0 |
| Oct 11 | +1 |
| Oct 12 | 0 |
| Oct 13 | 0 |
| Oct 14 | 0 |
| Oct 15 | 0 |
| Oct 16 | 0 |
- 30 skills (30 skills found in its SKILL.md files)
- 2 forks (2 forks)
- 8mo ago last update (Last updated 8mo ago)
Install
Skills CLI
npx skills add ElliotJLT/Claude-Skill-Potions
Asks which skills and agents to install. Just one: npx skills add ElliotJLT/Claude-Skill-Potions --skill agent-audit — add -g for every project.
Claude Code
git clone https://github.com/ElliotJLT/Claude-Skill-Potionscp -r "Claude-Skill-Potions/skills/agent-audit" ~/.claude/skills/
Copies the agent-audit skill into ~/.claude/skills/ for every project (use .claude/skills/ for one project). Repeat for the other skills listed below.
Plugin
/plugin marketplace add ElliotJLT/Claude-Skill-Potions
Run inside Claude Code if the repository ships a plugin marketplace, then pick plugins from /plugin.
Skills can run code on your machine — read the SKILL.md first.
What it does
In the author's own words, from each skill's SKILL.md — showing the first 30 of 39 files.
-
agent-audit
When reviewing, optimizing, or inheriting an LLM agent, systematically identify what's actually load-bearing vs. cruft. Instruments usage, ablates components, and strips the agent to minimum viable form. Answers: "What can we remove without degrading quality?" The goal is the leanest agent that still works.
skills/agent-audit/SKILL.md on GitHub (opens in a new tab) -
battle-plan
Before ANY significant development task (new feature, refactor, integration, migration), run a complete planning ritual by orchestrating other skills in sequence: rubber-duck (clarify scope) -> pre-mortem (assess risks) -> eta (estimate time) -> final confirmation. Do not start coding until the battle plan is approved.
skills/battle-plan/SKILL.md on GitHub (opens in a new tab) -
breadcrumbs
Leaves notes for future Claude sessions in .claude/breadcrumbs.md. At session end or after significant work, records what was tried, what worked, what failed, and context for next time. On session start, reads breadcrumbs to understand history. Session-to-session memory without manual updates.
skills/breadcrumbs/SKILL.md on GitHub (opens in a new tab) -
careful-delete
Before any destructive or irreversible operation (rm -rf, DROP TABLE, DELETE, force push, branch deletion, truncate), orchestrate a safety cycle: assess blast radius → confirm explicitly → document what happened. Chains pre-mortem and you-sure with built-in documentation. No dangerous operation executes without ceremony.
skills/careful-delete/SKILL.md on GitHub (opens in a new tab) -
debug-to-fix
When debugging frustration appears ("why isn't this working?", "it should work", "I don't understand"), orchestrate the full debug cycle: clarify → investigate → fix → verify. Prevents the common failure of jumping to fixes before understanding the problem. An elixir that chains rubber-duck and prove-it with investigation.
skills/debug-to-fix/SKILL.md on GitHub (opens in a new tab) -
dont-be-greedy
When a user uploads or references a data file (CSV, JSON, XLSX, TXT, LOG) or any file larger than 100KB, immediately estimate token cost using scripts/estimate_size.py. If >30k tokens, chunk the file and summarize each chunk. If smaller, run quick inspection. Return a safe preview and summary without asking the user what to do.
skills/dont-be-greedy/SKILL.md on GitHub (opens in a new tab) -
drip
Track and surface the estimated water cost of Claude interactions. Every query has a physical footprint - data centers need cooling, electricity needs generation. This skill adds environmental accountability by estimating water consumption per session and surfacing it at meaningful moments. Not to induce guilt, but to create awareness of the physical cost of intelligence.
skills/drip/SKILL.md on GitHub (opens in a new tab) -
eta
When a user asks how long a task will take, requests a time estimate, or before starting any non-trivial coding task, immediately run scripts/estimate_task.py to analyze the codebase scope and provide a data-driven time estimate. Show the estimate breakdown, risk factors, and checkpoint recommendations without asking.
skills/eta/SKILL.md on GitHub (opens in a new tab) -
fan-out
Orchestration pattern for parallelizable tasks. When facing work that can be split into independent subtasks (research multiple topics, analyze multiple files, test multiple scenarios), spawn parallel agents and aggregate results. Use when subtasks have no dependencies on each other.
skills/fan-out/SKILL.md on GitHub (opens in a new tab) -
geordie
When activated, respond entirely in Geordie dialect from Newcastle upon Tyne. Use proper Geordie words, phrases, and grammar. Reference Newcastle United players, legends, and lore when making analogies or celebrating wins. Channel the spirit of St James' Park, The Entertainers, and Wor Jackie himself. Howay the lads!
skills/geordie/SKILL.md on GitHub (opens in a new tab) -
granola-sync
Syncs Granola meeting notes to Obsidian vault. Reads from Granola's local cache to extract meeting metadata and notes, then creates properly formatted markdown files with frontmatter. Also handles manual transcript formatting when cache doesn't have content.
skills/granola-sync/SKILL.md on GitHub (opens in a new tab) -
keep-it-simple
Before adding abstraction, asks "do we need this now?" Activates when proposing factories, abstract classes, config-driven behavior, or "for future extensibility." Resists over-engineering. Three similar lines are better than a premature abstraction.
skills/keep-it-simple/SKILL.md on GitHub (opens in a new tab) -
learn-from-this
When a session contains a significant failure, misunderstanding, or repeated mistake, analyse the root cause and draft a new skill that would have prevented it. The skill library should grow from real failures, not hypothetical improvements. Every painful debugging session is a skill waiting to be written.
skills/learn-from-this/SKILL.md on GitHub (opens in a new tab) -
loose-ends
Before declaring work complete, checks for loose ends: unused imports, TODO comments created, missing tests, stale references, incomplete error handling. Activates after implementing features or fixes. The cleanup that always gets skipped.
skills/loose-ends/SKILL.md on GitHub (opens in a new tab) -
map-reduce
Orchestration pattern for large-scale processing where work is distributed, processed independently, then combined. Map phase splits and processes, Reduce phase aggregates results. Use for codebase-wide analysis, bulk transformations, or any task where "do X to everything, then summarize."
skills/map-reduce/SKILL.md on GitHub (opens in a new tab) -
obsidian-base-create
Generates Obsidian .base files from natural language descriptions. Translates requests like "show me all active project notes sorted by date" into valid .base YAML with filters, formulas, views, and summaries. Activates on "create base", "make a view", "show me all notes where", "dashboard", or when user wants structured views of their vault.
skills/obsidian-base-create/SKILL.md on GitHub (opens in a new tab) -
obsidian-canvas-create
Generates Obsidian .canvas files from intent. Takes a description of what you want to visualise and produces valid JSON Canvas — mind maps, flowcharts, kanban boards, research canvases, project overviews. Activates on "create canvas", "make a board", "visualise", "map out", "mind map", or when spatial organisation of ideas is needed.
skills/obsidian-canvas-create/SKILL.md on GitHub (opens in a new tab) -
obsidian-daily-driver
Manages daily notes workflow in Obsidian. Appends tasks, session logs, and learnings to today's daily note. Creates the daily note if it doesn't exist. Bridges Claude Code sessions to your daily note so nothing gets lost. Activates on "add to daily", "log this", "daily note", or end of session when daily notes are enabled.
skills/obsidian-daily-driver/SKILL.md on GitHub (opens in a new tab) -
obsidian-note-create
Creates well-structured Obsidian notes with proper frontmatter, wikilinks, and template adherence. Detects available CLI (official, Yakitrak, or direct file write) and uses the best option. Reads vault conventions from CLAUDE.md before creating. Activates on "create note", "new note", "add to obsidian", or when creating markdown files in an Obsidian vault.
skills/obsidian-note-create/SKILL.md on GitHub (opens in a new tab) -
obsidian-session-sync
End-of-session ritual that syncs Claude Code session artifacts to an Obsidian vault. Chains breadcrumbs, retrospective, note creation, and daily driver into a single flow. Creates session notes, updates daily note, and leaves breadcrumbs. Activates on "sync to obsidian", "save session", "end session", or when user wraps up significant work in a vault-connected project.
skills/obsidian-session-sync/SKILL.md on GitHub (opens in a new tab) -
obsidian-vault-init
Initialises an Obsidian vault for Claude Code workflows. Sets up folder structure, frontmatter conventions, templates, starter .base views, and a CLAUDE.md that describes the vault so future sessions understand it instantly. Activates on "set up obsidian", "init vault", "new vault", or first contact with an Obsidian project that has no CLAUDE.md.
skills/obsidian-vault-init/SKILL.md on GitHub (opens in a new tab) -
obsidian-vault-search
Searches an Obsidian vault intelligently — combines CLI search, frontmatter filtering, content grep, and wikilink traversal. Goes beyond keyword search to find notes by property, by link, by folder, and by content. Activates on "find in vault", "search vault", "which note has", "where did I write about", or when looking for specific notes in Obsidian.
skills/obsidian-vault-search/SKILL.md on GitHub (opens in a new tab) -
pair-mode
When activated, Claude becomes a pair programming partner rather than a code-generation tool. Explains reasoning, teaches patterns, asks questions that build understanding, and adjusts depth based on the person's goals. Balances getting work done with building lasting knowledge. Activate with "let's pair on this" or by setting a learning focus at session start.
skills/pair-mode/SKILL.md on GitHub (opens in a new tab) -
pipeline
Orchestration pattern for sequential, dependent tasks. When work must flow through stages where each stage depends on the previous (design → implement → test → review), structure as a pipeline with explicit handoffs. Each stage completes before the next begins.
skills/pipeline/SKILL.md on GitHub (opens in a new tab) -
pre-mortem
Before starting ANY significant task (feature build, refactor, integration, migration, or architectural change), first imagine the project has failed. Generate 3-5 specific failure scenarios, assess risk levels, identify mitigations, then adjust the implementation plan to address high-risk items FIRST. Do not start coding until the pre-mortem is acknowledged.
skills/pre-mortem/SKILL.md on GitHub (opens in a new tab) -
prove-it
Before declaring any task complete, actually verify the outcome. Run the code. Test the fix. Check the output. Claude's training optimizes for plausible-looking output, not verified-correct output. This skill forces the verification step that doesn't come naturally. No victory laps without proof.
skills/prove-it/SKILL.md on GitHub (opens in a new tab) -
retrospective
After completing a significant task or experiment, documents what worked, what failed, and key learnings. Activates when a multi-step task finishes or when user says "done", "finished", "that worked", or asks for a summary. Failed attempts get documented first - they're read more than successes.
skills/retrospective/SKILL.md on GitHub (opens in a new tab) -
rubber-duck
When a user is stuck, frustrated, or describing a problem vaguely, do NOT immediately suggest solutions. First, force structured problem articulation through targeted questions: What did you expect? What happened instead? What have you tried? Only after the problem is clearly defined, propose solutions.
skills/rubber-duck/SKILL.md on GitHub (opens in a new tab) -
safe-refactor
When refactoring, rewriting, or migrating critical code paths, orchestrate a safe cycle: assess risks → implement → verify → document. Chains pre-mortem and prove-it with built-in implementation phase. Prevents "refactor broke production" disasters. Activates on "refactor", "rewrite", "migrate", or "clean up" for non-trivial code.
skills/safe-refactor/SKILL.md on GitHub (opens in a new tab) -
sanity-check
Before building on assumptions, validates them first. Activates when making claims about how code works, what exists, or why something happens. Prevents assumption cascades where one wrong guess leads to a completely wrong solution.
skills/sanity-check/SKILL.md on GitHub (opens in a new tab)
No skill matches that filter.
Review before you install
A skill is a set of instructions and scripts your agent will follow, and it can run code on your machine. Read the SKILL.md and any scripts first — this listing is not a security review.