lidge-jun/codexclaw / plugins/codexclaw/skills/search
cxc-search
VerifiedUse for web/current lookups. Triggers: search, look up, latest, news, prices, docs, status, X/Twitter, deep research, 검색, 검색해, 찾아봐, 찾아줘, 알아봐, 웹검색, 딥리서치, 심층 조사.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 3.7 KB |
| agents/openai.yaml | config | 157 B |
| references/blocked-url-reader.md | markdown | 1.9 KB |
| references/deep-research-entry.md | markdown | 1.7 KB |
| references/deep-research.md | markdown | 9.0 KB |
| references/discovery-boundaries.md | markdown | 887 B |
| references/divergence-grounding.md | markdown | 1.3 KB |
| references/hosted-discovery.md | markdown | 559 B |
| references/intent-guard.md | markdown | 1.8 KB |
| references/query-rewrite.md | markdown | 1.5 KB |
| references/source-open-proof.md | markdown | 1.7 KB |
| references/subagent-attachment.md | markdown | 2.7 KB |
| references/tool-notes.md | markdown | 887 B |
| scripts/agbrowse_helper.py | script | 3.9 KB |
references/intent-guard.md
View on GitHub## Korean Intent Guard (8 rules)
When the user says **검색 / 검색해 / 찾아봐 / 찾아줘 / 알아봐 / 웹검색** (or English
*search / look up / latest / current / news*) without naming local files or code:
1. **Classify the target first**: external/public/current info -> the ladder
above; programming library/framework/API docs -> official docs or the active
documentation retrieval path, then source-open proof; this repository's
code/logs/config -> file search (`rg`, `rg --files`, local code tools).
**"Figure out how this specific system/app/AI tool/API works"** (로직 파악,
뜯어봐) is not a web lookup by default — route to `dev-debugging`
[logic-analysis.md](../../dev-debugging/references/logic-analysis.md) (the observation loop) and use this ladder
only for its external-evidence steps (docs, CVEs, prior writeups).
2. **Do not send the full natural-language sentence as the only query.** Rewrite
it into 1-3 focused keyword queries (see `query-rewrite.md`).
3. **Preserve anchors** in the rewrite: entities, source hints (official, Naver,
GitHub), dates, locale, and content type.
4. **Treat results as candidate URLs**, not final evidence — fetch/open the
original page when factual accuracy, recency, or attribution matters.
5. **Repository targets use file search**, never web search. Do not misroute a
code/log/config lookup to the web.
6. **Docs queries prefer official documentation** (or the active docs retrieval
path) before general web search, then open the source for proof.
7. **Bare ambiguous "검색"** (no local-file and no clear web target) -> ask ONE
short clarification before launching either a repo-wide grep or a web search.
8. **No hidden fallback** between web, docs, and file search. State the
classification you chose; never silently chain web -> docs -> grep.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file). | Stars: 198k | Updated | Claude CodeCodex | Unverified | Install |
| doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |