Use for web/current lookups. Triggers: search, look up, latest, news, prices, docs, status, X/Twitter, deep research, 검색, 검색해, 찾아봐, 찾아줘, 알아봐, 웹검색, 딥리서치, 심층 조사.
The English summary is being prepared. Showing the original description.
Review the instructions the agent will receive before you install.
Search discipline for any lookup that leaves the repository. This skill is
implicit-visible as metadata (allow_implicit_invocation: true); load the
full body on explicit trigger or dev-hub routing, never by an external
dispatcher.
Search results are candidate URLs, not evidence. Snippets, summaries, and search-result consensus discover where a fact might live; they never settle it. When recency, factual accuracy, version/compatibility, or source attribution matters, open the original page and confirm it before you treat the answer as sufficient. This invariant precedes every sufficiency rule below — no tier may declare an answer final on snippet text alone.
Before climbing the ladder, name the depth — it is distinct from the target classifier in the Korean Intent Guard (which picks web vs docs vs repo):
Classify external/public/current information, official-doc behavior, or this repository's code/logs/config before choosing tools; system comprehension routes to cxc-dev-debugging.
Before querying, read Korean Intent Guard and query rewrite.
| Condition | Reference |
|---|---|
| Before every query | Korean Intent Guard, query rewrite |
| Discovering candidate URLs (Tier 1) | Hosted discovery |
| Opening a source to settle a claim (Tier 2) | Source-open proof (SEARCH-BROWSE-01) |
| Blocked, JS, PDF or table source | Blocked-URL reader |
| Explicit deep-research request or host mode (Tier 3) | Entry boundaries, then Deep research |
| Any search subagent, including audit/reviewer or Luna lanes | Skill attachment (SEARCH-ATTACH-01) |
| PABCD divergence candidates | Candidate grounding |
| Luna discovery or assessing available backends | Discovery boundaries |
| Host/tool capability or search integration questions | Tool notes |
Stop escalating when any holds: a sufficient primary source is found and confirmed; all candidate URLs are dead or unreachable; or the task needs a user clarification. Do not keep climbing tiers past a confirmed answer, and do not spend Tier 3 subagents on a question Tier 1+2 already settled.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use for AST search and codemods. Triggers: ast-grep, sg, function/call/class/import, empty catch, missing await, YAML rules.
The English summary is being prepared. Showing the original description.
Use for coding, PR delivery, scaffolding and QA. Triggers: develop, fix, refactor, test, review, docs, browse, stacked PR, 개발, 수정, 검토, 스택 PR.
The English summary is being prepared. Showing the original description.
Use for module boundaries and dependencies. Triggers: circular import, coupling, barrel, re-export, validation placement, 모듈 경계, 순환 참조.
The English summary is being prepared. Showing the original description.
Use for APIs, servers and app databases. Triggers: REST, GraphQL, migration, query optimization, middleware, caching, queues, 백엔드, API 작업, 마이그레이션, 쿼리 최적화.
The English summary is being prepared. Showing the original description.
Use for code/PR/diff review and refactor audits. Triggers: review this, before merge, antipattern, 리뷰, 코드 리뷰, 머지 전에 확인.
The English summary is being prepared. Showing the original description.
Use for analytics and data pipelines. Triggers: ETL, ELT, data quality, SQL optimization, schema drift, backfill, 데이터 파이프라인, 데이터 품질, 백필.
The English summary is being prepared. Showing the original description.