Skill

skill-first

Checks for and loads relevant skills before starting tasks, new requests, beginning work, or implementation, enforcing skill-first discipline.

developer-tools

npx claudepluginhub majesticlabs-dev/majestic-marketplace --plugin majestic-tools

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Before responding to ANY user request, check if a matching skill exists.

SKILL.md

Similar Skills

using-superpowers

Enforces skill check before any Claude Code response: invoke if 1% relevant, follow flowchart and red flags to avoid rationalizing skips. Use at conversation starts.

claude-commands

using-skills

Enforces mandatory Skill tool invocation before any response or clarifying questions at conversation start to discover and apply relevant skills.

amplify

using-superpowers

37.1k

Mandates skill invocation before any response if even 1% relevant, including clarifications. Guides accessing and using skills via Skill tool in Claude Code.

antigravity-awesome-skills

Stats

Parent Repo Stars38

Parent Repo Forks7

Last CommitNov 27, 2025

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Skill-First Discipline

Before responding to ANY user request, check if a matching skill exists.

Checklist

Scan available skills - Review the Skill tool's available skills listing

Match request to skill - Does any skill cover this task type?

Load if matched - Use Skill tool to load it

Announce usage - Tell the user: "I'm using [skill-name] to [action]"

Follow exactly - Execute the skill's guidance without deviation

Rationalizations to Reject

If you catch yourself considering these, stop and check for skills:

"This is simple, I don't need a skill"

"I'll just do this quickly"

"The skill is overkill"

"I already know how to do this"

These are failure modes. If a skill exists for your task, use it.

Discovering Available Skills

The Skill tool shows all installed skills in its "Available Skills" section. Skills are organized by source:

majestic-engineer: Code search, TDD, diagrams, CI, git worktrees

majestic-rails: Ruby/Rails coding, RSpec, Minitest, gem building

majestic-tools: Brainstorming, skill creation, skill-first

majestic-marketing: Copy editing

To list skills programmatically:

find ~/.claude -path "*/skills/*/SKILL.md" 2>/dev/null | xargs -I{} grep "^name:" {}

When to Skip

Skip only when:

Answering factual questions (no task involved)

Simple clarifications

User explicitly declines skill usage

For everything else, skill-first is mandatory.

Skill-First Discipline

Before responding to ANY user request, check if a matching skill exists.

Checklist

Scan available skills - Review the Skill tool's available skills listing
Match request to skill - Does any skill cover this task type?
Load if matched - Use Skill tool to load it
Announce usage - Tell the user: "I'm using [skill-name] to [action]"
Follow exactly - Execute the skill's guidance without deviation

Rationalizations to Reject

If you catch yourself considering these, stop and check for skills:

"This is simple, I don't need a skill"
"I'll just do this quickly"
"The skill is overkill"
"I already know how to do this"

These are failure modes. If a skill exists for your task, use it.

Discovering Available Skills

The Skill tool shows all installed skills in its "Available Skills" section. Skills are organized by source:

majestic-engineer: Code search, TDD, diagrams, CI, git worktrees
majestic-rails: Ruby/Rails coding, RSpec, Minitest, gem building
majestic-tools: Brainstorming, skill creation, skill-first
majestic-marketing: Copy editing

To list skills programmatically:

find ~/.claude -path "*/skills/*/SKILL.md" 2>/dev/null | xargs -I{} grep "^name:" {}

When to Skip

Skip only when:

Answering factual questions (no task involved)
Simple clarifications
User explicitly declines skill usage

For everything else, skill-first is mandatory.