'tool' 검색 결과

Investigate unexpected costs in the ECC Tools GitHub App by tracing events, queued jobs, analysis workers, and billing logic. Identifies repeated pull request creation, usage-limit bypasses, unintended premium-model calls, and duplicate retries, then verifies targeted fixes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigate excessive pull request creation
• Find races that bypass usage limits
• Check free-tier access to premium models

Test browser interfaces through Chrome DevTools MCP, a connection that lets an agent inspect a live browser. Check screenshots, errors, network traffic, accessibility, and performance to diagnose problems and verify fixes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Diagnosing layout and styling problems
• Investigating browser errors and failed API requests
• Comparing screenshots before and after a fix

Find agent skills for installed coding tools such as Claude Code and Codex. Use OmniRoute to detect available tools, review relevant GitHub matches, and guide installation into each tool’s skill directory.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Find skills for installed coding tools
• Review GitHub matches by relevance
• Install a skill into multiple tools

Check and control OmniRoute’s MCP server, which connects agents to tools. Inspect tool permission scopes, enable or restart the server, and invoke tools with JSON arguments from the command line.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Check the MCP server’s operating status
• Enable, disable, or restart the server
• Inspect permission scopes for a tool

Automate supported Amazon operations through Rube MCP, a connection for agent tools. Search for available actions and their required inputs, verify the Amazon connection, and execute individual or bulk tasks using the discovered tools.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Discovering operations supported by the Amazon toolkit
• Checking the Amazon connection before running tasks
• Running supported Amazon operations in bulk

Review tooltips so keyboard and screen reader users can access their explanations. Check the rendered HTML, accessible associations, hover and focus behavior, Escape dismissal, and contrast, then identify the elements and attributes that need fixes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking keyboard access to tooltips
• Reviewing tooltip associations for screen readers
• Checking hover, focus, and Escape behavior

Find and install command-line tools that let AI agents operate professional software. Search by task or category, check which workflow capabilities are available locally, and install the specific tools needed for a multi-tool project.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Find command-line tools for image editing or 3D modeling
• Check available tools for a video production workflow
• Install only the capabilities needed for a task

Document the tools an AI agent may call, including input rules, caller permissions, execution limits, and retry conditions. Produce a tool register and verification plan for reviewing registrations or MCP routing designs.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Defining which tools an agent may call
• Reviewing a proposed tool registration
• Documenting timeout and retry rules

Configure tools and skills for sub-agents before dispatching development tasks. Role presets cover implementation, planning, reviews, testing, and verification, with defined boundaries for what each agent should do and whether it may modify files.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Setting tool permissions before spawning a sub-agent
• Separating implementation, planning, and review roles
• Configuring agents for review without file changes

Design and build name generators, personality quizzes, avatars, and similar interactive tools. Plan simple inputs, result logic, and visually clear result cards that people can share through social buttons or screenshots.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Building name and text generators
• Designing personality quizzes and scoring rules
• Creating result cards for sharing on social media

Implement or change behavior in Composio’s TypeScript SDK, the library used to integrate Composio into applications. Covers tools, sessions, authentication settings, connected accounts, and generated interfaces in @composio/core and shared TypeScript packages.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Change tool or toolkit behavior
• Implement session or authentication changes
• Update connected account handling

Customize a project's Docker environment with personal tools such as vim, ripgrep, or jq. The skill prepares user override files, adds requested packages, and provides rebuild commands while keeping personal configuration out of Git.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Adding an editor or search tools to a container
• Keeping personal settings separate from shared files
• Customizing a source-built development environment

Automate supported Amazon operations through Rube MCP, a connection for agent tools. Search for available actions and their required inputs, verify the Amazon connection, and execute individual or bulk tasks using the discovered tools.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Discovering operations supported by the Amazon toolkit
• Checking the Amazon connection before running tasks
• Running supported Amazon operations in bulk

Manage Superset plugins from installation and updates to account connections and removal. Check which external tools each plugin provides, call them through Superset, and investigate missing connections or other reasons tools are unavailable.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Install or update a Superset plugin
• Connect an account required by a plugin
• Inspect and call a plugin's tools

Expert guide for using n8n-mcp MCP tools effectively. Use when searching for nodes, validating configurations, accessing templates, managing workflows, organizing workflows into folders, managing credentials, auditing instance security, or using any n8n-mcp tool. Provides tool selection guidance, parameter formats, and common patterns. IMPORTANT — Always consult this skill before calling any n8n-mcp tool — it prevents common mistakes like wrong nodeType formats, incorrect parameter structures, and inefficient tool usage. If the user mentions n8n, workflows, nodes, or automation and you have n8n MCP tools available, use this skill first.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when connecting your agent to external APIs, tools, or services via Gateway, or restricting tool access with Cedar policies. Handles gateway setup, target types, outbound auth (OAuth, API key, IAM), credentials, and Cedar policy authoring. Triggers on: "connect to API", "add gateway", "connect to MCP server", "Lambda tools", "OpenAPI", "gateway target", "Cedar policy", "restrict tools", "policy engine", "gateway auth error", "store API key", "outbound credential", "env var API key", "API key None after deploy", "credential not available after deploy", "should this be a gateway target", "give my agent tools", "add tools to agent". Not for inbound auth (who can call your agent) — use agents-harden. Not for debugging agent behavior — use agents-debug. Not for VPC networking errors (agent can't reach APIs due to VPC) — use agents-build. Not for creating or hosting a new MCP server project — use agents-get-started.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

When the user wants to plan, evaluate, or build a free tool for marketing purposes — lead generation, SEO value, or brand awareness. Also use when the user mentions "engineering as marketing," "free tool," "marketing tool," "calculator," "generator," "interactive tool," "lead gen tool," "build a tool for leads," or "free resource." This skill bridges engineering and marketing — useful for founders and technical marketers.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Defines how to add Operately MCP tools (API-first wrappers). Use when creating, changing, or reviewing MCP tools under app/lib/operately_web/mcp/tools/, when the user mentions MCP tools, tool catalog, @expected_tool_names, or when exposing a new Operately capability to ChatGPT/Claude MCP clients.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert in building custom tools that solve your own problems first. The best products often start as personal tools - scratch your own itch, build for yourself, then discover others have the same itch. Covers rapid prototyping, local-first apps, CLI tools, scripts that grow into products, and the art of dogfooding. Use when "build a tool, personal tool, scratch my itch, solve my problem, CLI tool, local app, automate my, build for myself, " mentioned.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Select, define, create, inspect, update, attach, detach, and verify reusable Vapi tools through the public API. Use for native call-control tools, supported provider integrations, API Request tools, custom function tools, MCP tools, tool messages, credentials, or configuration-preserving assistant attachment changes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

When the user wants to plan, evaluate, or build a free tool for marketing purposes — lead generation, SEO value, or brand awareness. Also use when the user mentions "engineering as marketing," "free tool," "marketing tool," "calculator," "generator," "interactive tool," "lead gen tool," "build a tool for leads," or "free resource." This skill bridges engineering and marketing — useful for founders and technical marketers.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Tools are how AI agents interact with the world. A well-designed tool is the difference between an agent that works and one that hallucinates, fails silently, or costs 10x more tokens than necessary. This skill covers tool design from schema to error handling. JSON Schema best practices, description writing that actually helps the LLM, validation, and the emerging MCP standard that's becoming the lingua franca for AI tools. Key insight: Tool descriptions are more important than tool implementa

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Plans free tools, calculators, generators, and interactive widgets that attract target audience through search and social sharing. Engineering as marketing — build something useful, capture leads. Use when someone wants to build a free tool for marketing, says 'free tool', 'calculator', 'generator', 'engineering as marketing', 'side project marketing', 'interactive widget', 'lead generation tool', 'SEO tool', 'growth hack', 'build something to attract users', or wants to attract users through utility rather than content. Also use when someone asks 'how do I get more signups', 'what should I build for marketing', or 'content marketing alternative' — a free tool is often the best answer. Includes search volume validation, UX flow templates, and conversion hook design.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Scan a project to detect configured quality and testing tools across JVM (Gradle/Maven), Android (AGP/Compose/KMP), Node.js/TypeScript, and Python ecosystems. Cross-reference against research-backed recommendations and assist with setup. Auto-detects project type(s) including monorepos with mixed ecosystems. Use when user asks to "audit tooling", "recommend tools", "quality stack", "what tools am I missing", "setup eslint", "setup detekt", "add coverage", "add ruff", "configure CI quality pipeline", "scan project tools", "tooling audit", "android tooling", "android quality", "compose testing", "kmp testing", or "screenshot testing".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.