skill-first

Check for relevant skills before starting any task. Triggers on task start, new requests, beginning work, or implementation.

⭐13stars🔀0forks📁View on GitHub🕐Updated Jan 3, 2026⬇️1downloads

When & Why to Use This Skill

The Skill-First Discipline skill is a meta-orchestration tool designed to optimize AI agent performance by mandating a systematic check for specialized skills before task execution. It ensures that Claude leverages the most relevant, purpose-built workflows for every request, significantly enhancing accuracy, consistency, and adherence to established technical or business standards while preventing generic or suboptimal responses.

Use Cases

  • Automated Tool Selection: Automatically scanning and loading specialized skills for complex coding, debugging, or research tasks to ensure the highest quality output rather than relying on generic model knowledge.
  • Workflow Standardization: Enforcing the use of specific SOPs and organizational playbooks across different agent sessions to maintain operational consistency and professional rigor.
  • Reliability Engineering: Preventing 'lazy' AI behavior by requiring the agent to utilize dedicated testing, validation, and documentation skills for every implementation task.
  • Agentic Efficiency: Streamlining multi-tool environments by providing a clear decision-making framework for when and how to trigger specialized sub-agents or skill sets.
nameskill-first
descriptionCheck for relevant skills before starting any task. Triggers on task start, new requests, beginning work, or implementation.

Skill-First Discipline

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

Checklist

  1. Scan available skills - Review the Skill tool's available skills listing
  2. Match request to skill - Does any skill cover this task type?
  3. Load if matched - Use Skill tool to load it
  4. Announce usage - Tell the user: "I'm using [skill-name] to [action]"
  5. 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.