Use when current web info needed, verifying APIs still work, checking latest versions, or avoiding outdated implementations
Automatically researches current API docs, version changes, and best practices when you need up-to-date information. Triggers on version errors, security-critical code, or when libraries may have evolved.
/plugin marketplace add TechNickAI/ai-coding-config/plugin install ai-coding-config@ai-coding-configThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Examples: "Is useEffect still the way to handle this in React 18?", "Did Stripe change their webhook payload?", "What's the current Node LTS version?"
Just search, grab the answer, keep coding. No storage, no ceremony, no permission needed. </quick-check>
<deep-dive> When: The decision really matters Time: 5-15 minutesExamples: Choosing between competing technologies, understanding a new architectural pattern, debugging something that doesn't match documentation.
Always ask first: "This needs deeper research (5-15 min). Should I dig into this now?" Let the user decide if they want to pause for research or continue with existing knowledge.
Research thoroughly, save findings in research/[topic].md for team reference. </deep-dive>
<tool-selection> Always use the best available web search. Priority order:MCP servers (preferred when available):
Built-in tools (fallback):
Tell the user which you're using:
This transparency helps users understand tool selection and configure MCP servers if desired. </tool-selection>
<search-strategy> Start with official sources - docs, changelogs, GitHub releases. Then expand to community discussions if needed. </search-strategy> <output-format> Output should be scannable and actionable. Skip the fluff, get to what matters.Good pattern:
Breaking change: redirectToCheckout() removed in v4
New pattern:
Migration: [Specific code example]
Source: Stripe docs v2024.11.15 </output-format>
<key-principles> Recognize patterns: When you see version-specific errors, deprecated methods, or post-2023 technologies, that signals research is needed.Be transparent: Say "I should verify this" or "Let me check current best practices" rather than guessing.
Speed over perfection: For quick checks, first good answer wins. For deep dives, thoroughness matters.
No unnecessary storage: Quick research lives in the conversation. Only save deep research that others might reference. </key-principles>
<common-pitfall> Don't research everything. If your React knowledge from 2023 still works and the user isn't hitting issues, just build. Research is a tool, not a crutch. </common-pitfall>This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.