What is the 1% rule mentioned in the skill?

The 1% rule ensures that even if a skill's relevance seems unlikely, it is invoked to verify applicability, preventing the accidental omission of critical guidance.

When should the Skill Activation Protocol be used?

It should be invoked at the very start of every conversation to determine which other specialized skills are needed for the task at hand.

Can I skip a skill if it is found to be irrelevant after invocation?

Yes. If a skill is invoked and the agent determines it does not apply to the current context, the agent is not required to follow its instructions.

How does this skill handle multiple applicable skills?

It follows a strict priority order: process-oriented skills (like brainstorming or debugging) are invoked first, followed by implementation-specific skills.

Skill Activation Protocol

Name: Skill Activation Protocol
Author: claudiodearaujo

byclaudiodearaujo

0•

Productivity & Workflow

Enforces a disciplined workflow by requiring the invocation of relevant skills before any response or action.

The Skill Activation Protocol (using-superpowers) is a meta-skill designed to eliminate shortcuts and ensure maximum efficiency when using Claude Code. It mandates that the AI agent checks for and invokes relevant domain-specific skills at the very beginning of a task, even if the applicability seems marginal. By preventing premature action and forcing a 'skills-first' mindset, it ensures that best practices, checklists, and specialized workflows are never overlooked, leading to higher quality and more consistent code outcomes.

Key Features

01Anti-rationalization framework to prevent process skipping

02Prioritization logic for process and implementation skills

030 GitHub stars

04Standardized announcement protocol for skill invocation

05Visual workflow integration via automated Todo lists

06Mandatory skill discovery before task execution

Use Cases

01Ensuring project standards are met before starting any coding task

02Preventing 'simple' tasks from bypassing critical architectural patterns

03Standardizing brainstorming and debugging workflows across development teams

Key Features

01Anti-rationalization framework to prevent process skipping

02Prioritization logic for process and implementation skills

030 GitHub stars

04Standardized announcement protocol for skill invocation

05Visual workflow integration via automated Todo lists

06Mandatory skill discovery before task execution

Use Cases

01Ensuring project standards are met before starting any coding task

02Preventing 'simple' tasks from bypassing critical architectural patterns

03Standardizing brainstorming and debugging workflows across development teams