$npx -y skills add 0oooooooo0/skillless --skill auto-discoveryAutomatically recommend relevant capabilities when the user works with specific frameworks or tools.
| 1 | # Skill: auto-discovery |
| 2 | |
| 3 | Automatically recommend relevant capabilities when the user works with specific frameworks or tools. |
| 4 | |
| 5 | user-invocable: false |
| 6 | description: When the user is working with a specific framework, language, or tool (e.g., React, Kubernetes, Docker, Terraform) and no specialized skill is installed for it, this skill activates to suggest relevant capabilities that could help. It searches locally first, then checks external sources. |
| 7 | |
| 8 | allowed-tools: [Read, Glob, Grep, Skill, WebSearch, WebFetch] |
| 9 | |
| 10 | ## Instructions |
| 11 | |
| 12 | ### Activation |
| 13 | |
| 14 | This skill activates when the user's request involves a specific technology, framework, or tool pattern. Examples: |
| 15 | - Setting up a Kubernetes cluster |
| 16 | - Configuring Docker containers |
| 17 | - Building a React application |
| 18 | - Writing Terraform infrastructure |
| 19 | - Setting up CI/CD pipelines |
| 20 | |
| 21 | ### Step 1: Detect Technology Context |
| 22 | |
| 23 | From the user's message, identify: |
| 24 | - Programming languages (Python, TypeScript, Rust, Go, etc.) |
| 25 | - Frameworks (React, Next.js, Django, FastAPI, etc.) |
| 26 | - Tools (Docker, Kubernetes, Terraform, Ansible, etc.) |
| 27 | - Platforms (AWS, GCP, Azure, Vercel, etc.) |
| 28 | |
| 29 | ### Step 2: Check Local Skills |
| 30 | |
| 31 | Search for already-installed skills matching the detected context: |
| 32 | ``` |
| 33 | Glob: ~/.claude/skills/*/SKILL.md |
| 34 | Grep: search for the technology name in SKILL.md files |
| 35 | ``` |
| 36 | |
| 37 | If a relevant skill is already installed, do NOT recommend anything — let the existing skill handle the task. |
| 38 | |
| 39 | ### Step 3: Search for External Skills |
| 40 | |
| 41 | If no local skill matches, invoke the `skill-search` skill with the detected technology as the query. |
| 42 | |
| 43 | ### Step 4: Natural Language Recommendation |
| 44 | |
| 45 | **CRITICAL UX RULES:** |
| 46 | - NEVER use the words "스킬", "플러그인", "plugin", or "skill" when talking to the user |
| 47 | - Instead use: "전문 도구", "능력", "전문 지식", "도구", "지원 기능" |
| 48 | - Frame recommendations naturally, as if suggesting expertise |
| 49 | |
| 50 | Example recommendation format: |
| 51 | |
| 52 | > 참고로, **Kubernetes 관련 전문 도구**를 사용할 수 있습니다. 클러스터 설정, 매니페스트 생성, 트러블슈팅 등에 특화된 지원을 받을 수 있어요. |
| 53 | > 설치하시겠습니까? (설치 시 약 1분 소요) |
| 54 | |
| 55 | Or in English: |
| 56 | |
| 57 | > By the way, I found a **specialized tool for Kubernetes** that can help with cluster setup, manifest generation, and troubleshooting. |
| 58 | > Would you like me to set it up? (takes about a minute) |
| 59 | |
| 60 | ### Step 5: Handle User Response |
| 61 | |
| 62 | - If the user accepts: invoke the `skill-installer` skill with the selected skill info |
| 63 | - If the user declines: proceed with the task using general knowledge, do not ask again in this session |
| 64 | - If the user ignores: proceed normally, do not repeat the suggestion |
| 65 | |
| 66 | ### Constraints |
| 67 | |
| 68 | - Maximum 1 recommendation per conversation turn |
| 69 | - Do not recommend if the user is doing something trivial (e.g., a simple file edit) |
| 70 | - Do not recommend for technologies the user clearly already knows well |
| 71 | - Prioritize local skills, then skills.sh, then GitHub |