Skill Gate

Before starting any significant task, force explicit evaluation of available skills. For each potentially relevant skill, state YES/NO with reasoning. Only proceed to implementation after skills have been consciously evaluated and activated. Prevents the ~50% "coin flip" activation rate that occurs when skills are passively available but not deliberately considered.

62 stars 2 forksProductivity & Notes

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add ElliotJLT/Claude-Skill-Potions --skill skill-gate
Manual install
git clone --depth 1 https://github.com/ElliotJLT/Claude-Skill-Potions.git /tmp/Claude-Skill-Potions
mkdir -p ~/.claude/skills
cp -r /tmp/Claude-Skill-Potions/skills/skill-gate ~/.claude/skills/skill-gate

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Skill Gate

<purpose>
Skills don't help if they're not activated. Research shows passive skill
availability leads to ~50% activation (coin flip). Forced evaluation achieves
80-84% activation. This skill is the gate: no significant work begins until
skills have been explicitly evaluated and relevant ones activated.
</purpose>

## When To Activate

Trigger at the START of:

- Any task that will take more than a few minutes
- Any task involving architecture, refactoring, or significant decisions
- Any task where mistakes would be costly
- When user asks for help with a non-trivial problem
- Before writing any significant amount of code

Do NOT trigger for:

- Quick questions or explanations
- Trivial edits (typo fixes, small changes)
- When user explicitly says "just do it" or "skip the process"

## Instructions

### Step 1: Identify the Task Type

Categorize the incoming task:

```
Task: [Brief description]
Type: [Planning | Debugging | Implementation | Refactoring | Decision | Review | Other]
Complexity: [Trivial | Standard | Significant | Critical]
```

If Trivial, skip the gate. Otherwise, proceed.

### Step 2: Scan Available Skills

List potentially relevant skills for this task type:

```
Potentially relevant skills for [task type]:

| Skill | Relevant? | Reason |
|-------|-----------|--------|
| [skill-name] | YES/NO | [One sentence why] |
| [skill-name] | YES/NO | [One sentence why] |
| ... | ... | ... |
```

### Step 3: Activate Relevant Skills
Read the full skill on GitHub

Details

Skill name
skill-gate
Path
skills/skill-gate/SKILL.md
License
MIT
Repo updated
12 February 2026

FAQ

What does the Skill Gate skill do?

Before starting any significant task, force explicit evaluation of available skills. For each potentially relevant skill, state YES/NO with reasoning. Only proceed to implementation after skills have been consciously evaluated and activated. Prevents the ~50% "coin flip" activation rate that occurs when skills are passively available but not deliberately considered.

How do I install the Skill Gate skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add ElliotJLT/Claude-Skill-Potions --skill skill-gate. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Skill Gate popular?

It lives in ElliotJLT/Claude-Skill-Potions, which has 62 GitHub stars and 2 forks.

Related skills

Agent Audit

62

ElliotJLT/Claude-Skill-Potions

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.

AI, LLMs & Agents

Battle Plan

62

ElliotJLT/Claude-Skill-Potions

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.

Software Development

Breadcrumbs

62

ElliotJLT/Claude-Skill-Potions

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.

Productivity & Notes

External Comms

45

Azure-Samples/agent-skills-dotnet-demo

PAO workflow for scanning, drafting, and presenting community responses with human review gate

Productivity & Notes11

Retrospective

62

ElliotJLT/Claude-Skill-Potions

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.

Productivity & Notes

Manage Amp Context

48

amplitude/mcp-marketplace

Lists projects for an employee-accessible organization or writes organization/project AI context with `manage_amp_context`; use `get_amplitude_context` for reads.

Productivity & Notes12

Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.