What are the different enforcement levels for skill activation?

There are three levels: 'suggest' recommends the skill, 'warn' allows the action but provides a warning, and 'block' requires the skill to be used before proceeding.

How do triggers identify when to suggest a skill?

Triggers use keyword matching and regex patterns within the user prompt to identify intent and map it to the appropriate skill defined in your configuration.

What is the difference between plugin-level and project-level activation?

Plugin-level activation is set by the plugin author to help users discover relevant skills within a plugin, while project-level activation is configured by the end-user for their specific project needs.

Can I prevent certain skills from triggering automatically?

Yes, you can define 'skipConditions' within the skill-rules.json file to create escape hatches or specific scenarios where the activation should be ignored.

Skill Activation Patterns

Name: Skill Activation Patterns
Author: chkim-su

bychkim-su

Productivity & Workflow

Automates the discovery and activation of relevant Claude Code skills through keyword-based triggers and design patterns.

About

Skill Activation Patterns provides a standardized framework for automatically suggesting or enforcing Claude Code skills based on user input. By configuring trigger rules at either the plugin or project level, developers can ensure that specialized domain knowledge, guardrails, and implementation patterns are surfaced precisely when they are needed most. This reduces manual configuration overhead and ensures that the most relevant capabilities are always active during the development lifecycle.

Key Features

Keyword-based automatic skill discovery and suggestions
Support for skipConditions to prevent over-triggering in specific contexts
Multiple enforcement levels including suggest, warn, and block
Dual-scope implementation for plugin-level and project-level configuration
Regex-powered trigger matching for high-precision activation
0 GitHub stars

Use Cases

Automatically suggesting backend architecture skills when 'API' or 'database' keywords are detected
Enforcing security guardrails whenever authentication-related code is being modified
Improving plugin discoverability by recommending relevant sub-skills based on user intent

About

Key Features

Keyword-based automatic skill discovery and suggestions
Support for skipConditions to prevent over-triggering in specific contexts
Multiple enforcement levels including suggest, warn, and block
Dual-scope implementation for plugin-level and project-level configuration
Regex-powered trigger matching for high-precision activation
0 GitHub stars

Use Cases

Automatically suggesting backend architecture skills when 'API' or 'database' keywords are detected
Enforcing security guardrails whenever authentication-related code is being modified
Improving plugin discoverability by recommending relevant sub-skills based on user intent