smithery/chkim-su

skill-activation-patterns

Design patterns for automatic skill activation at plugin or project level. Use when implementing keyword-based skill suggestions.

Installation

$ npx skills add smithery/chkim-su --skill skill-activation-patterns

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/chkim-su · top by installs.

npx skills add smithery/chkim-su

Browse all from smithery/chkim-su

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Skill metadata

Parsed from SKILL.md frontmatter.

Allowed toolsRead, Write, Grep, Glob
Declared agents claude-code

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,885 B
  • docs SUMMARY.md 162 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Skill Activation Patterns

Automatic skill suggestions based on user prompt keywords.

Two Scopes

Scope Location Purpose Who Sets It
Plugin-level $CLAUDEPLUGINROOT/.claude/skills/skill-rules.json Plugin recommends its own skills Plugin author
Project-level $CLAUDEPROJECTDIR/.claude/skills/skill-rules.json User configures for their project End user

Plugin-level (Recommended for plugins with multiple skills)

Plugins with related skills SHOULD include skill-activation to help users discover relevant skills:

my-plugin/
├── hooks/hooks.json              ← UserPromptSubmit hook
├── scripts/skill-activation.py   ← Hook script
├── .claude/skills/skill-rules.json  ← Plugin's own rules
└── skills/
    ├── skill-a/
    └── skill-b/

Example: skillmaker uses plugin-level activation to suggest skill-design when user mentions "create skill".

Project-level (User-configured)

Users can add skill-activation to their own projects independently:

my-project/
├── .claude/
│   └── skills/
│       └── skill-rules.json   ← User's rules
└── settings.json              ← UserPromptSubmit hook

Quick Start

  1. Create .claude/skills/skill-rules.json
  2. Add UserPromptSubmit hook
  3. Hook reads rules, matches triggers, suggests skills

Core Concept

User Prompt → [Hook] → skill-rules.json → Match triggers → Suggest skills

skill-rules.json (Minimal)

{
  "version": "1.0",
  "skills": {
    "backend-patterns": {
      "type": "domain",
      "enforcement": "suggest",
      "promptTriggers": {
        "keywords": ["backend", "API"]
      }
    }
  }
}

Skill Types

Type Purpose
domain Expertise/knowledge
guardrail Enforce standards

Enforcement Levels

Level Behavior
suggest Recommend
warn Allow + warning
block Must use skill

Best Practices

  1. Start with suggest - Don't block until proven
  2. Specific keywords - Avoid generic over-triggering
  3. Test regex - Verify no false positives
  4. Use skipConditions - Allow escape hatch

References

  • [Full Schema](references/full-schema.md) - Complete skill-rules.json spec
  • [Hook Implementation](references/hook-implementation.md) - TypeScript/Bash code
  • [Real Examples](references/skill-rules-examples.md) - Production configs