9.3K skills · sorted by relevance
Plan free calculators, generators, and checkers for marketing. Compare ideas by search demand, competition, and effort, then define the user flow, lead capture, landing page, launch activities, and measurement plan to assess results.
Write JavaScript or Python for the n8n Custom Code Tool (@n8n/n8n-nodes-langchain.toolCode) — the AI-agent-callable tool, NOT the workflow Code node. Use when building a Code Tool attached to an AI Agent, writing code that an LLM will invoke, parsing the `query` input, returning a string result, defining an input schema for structured arguments (specifyInputSchema, jsonSchemaExample, DynamicStructuredTool), or troubleshooting errors like "Wrong output type returned", "No execution data available", "The response property should be a string, but it is an object", "Cannot assign to read only property 'name'", or an AI agent that refuses to call the tool. Covers the critical differences between Code node and Code Tool: return format (string vs `[{json:{...}}]`), unavailability of `$fromAI`/`$input`/`$helpers` in the Code Tool sandbox, naming rules for AI invocation, and when to use `toolWorkflow`/HTTP Request Tool instead.
The English summary is being prepared. Showing the original description.
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," "free resource," "ROI calculator," "grader tool," "audit tool," "should I build a free tool," or "tools for lead gen." Use this whenever someone wants to build something useful and give it away to attract leads or earn links. For downloadable content lead magnets (ebooks, checklists, templates), see lead-magnets.
The English summary is being prepared. Showing the original description.
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," "free resource," "ROI calculator," "grader tool," "audit tool," "should I build a free tool," or "tools for lead gen." Use this whenever someone wants to build something useful and give it away to attract leads or earn links. For downloadable content lead magnets (ebooks, checklists, templates), see lead-magnets.
The English summary is being prepared. Showing the original description.
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," "free resource," "ROI calculator," "grader tool," "audit tool," "should I build a free tool," or "tools for lead gen." Use this whenever someone wants to build something useful and give it away to attract leads or earn links. For downloadable content lead magnets (ebooks, checklists, templates), see lead-magnets.
The English summary is being prepared. Showing the original description.
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," "free resource," "ROI calculator," "grader tool," "audit tool," "should I build a free tool," or "tools for lead gen." Use this whenever someone wants to build something useful and give it away to attract leads or earn links. For downloadable content lead magnets (ebooks, checklists, templates), see lead-magnets.
The English summary is being prepared. Showing the original description.
This metadata record supports the BMad Core Tools module. Use the separate bmad skill to set up the module or report its current state; this record is not intended to be invoked directly.
Investigate Entra ID reconnaissance by searching Graph API logs for tool signatures and unusual directory queries. Use KQL, a log query language, to correlate suspicious requests with sign-ins and turn useful searches into Sentinel detection rules.
Plan and evaluate free calculators, generators, or assessment tools for marketing. Compare ideas by audience needs, search demand, and development effort, then outline essential features, email signup options, promotion, and success metrics.
Connect json-render to Redux or Redux Toolkit so UI state reads and writes use a Redux store. The skill explains how to select the relevant state and dispatch actions that replace it when updates occur.
Provides and generates LangChain4j tool and function calling patterns: annotates methods as tools with @Tool, configures tool executors, registers tools with AiServices, validates tool parameters, and handles tool execution errors. Use when building AI agents that call tools, define function specifications, manage tool responses, or integrate external APIs with LLM-driven applications.
The English summary is being prepared. Showing the original description.
Per-toolkit hardening audit loop for NV oOS Pro tools. Systematically scans each addons/pro/includes/tools/<toolkit> (and its plugins/nvoos-content-graph-pro mirror) for the recurring production failure classes — unguarded shell calls that fatal on exec-disabled hosts, calls to nonexistent client methods, string-assuming parsing of provider responses that may be arrays, provider enum/service mismatches, metric/source column drift that silently returns 0, secondary-table denominator gaps, the Chart.js fixed-height loop, misleading native-source errors, and silent import truncation that reports partial writes as success — then fixes, tests (Docker PHPUnit), and validates (phpcs both standards) before moving to the next toolkit. Use when asked to audit a toolkit, review the X tools for similar issues, do the same for the other toolkits, or continue the toolkit audit loop. The first case study (document-generation) found 3 fatal bugs + 1 broken regex; the food-beverage pass added classes 5–9.
The English summary is being prepared. Showing the original description.
Claude API (platform.claude.com) の tool use / Agent Skills / MCP。 tool definition (JSON Schema), tool_use / tool_result, server tools（code execution, web search, web fetch, memory tool, tool search）, client toolset（computer use, browser use）, Agent Skills (SKILL.md), Skills API GA (/v1/skills), MCP connector, mcp_servers, mcp_tool_listing, MCP tunnels, Tunnels API。
The English summary is being prepared. Showing the original description.
Identify the right tool for a process step. Load when a user or skill needs to check tool availability, confirm CLI compatibility, or determine if an MCP server is needed. Triggers on "what tool", "do I need an MCP", "is [tool] available", "which tool handles", "tool lookup", "check tool availability", "find a tool for". Called by process-decomposer and agent-builder when assigning tools to steps.
The English summary is being prepared. Showing the original description.
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.
Guides agents in choosing Cherry Studio tools for research, document conversion, memory, notifications, and other tasks. It explains when to use app tools or local runtimes, with checks for availability, configuration, and approval.
Design tools that AI agents can understand and call, covering input schemas, clear descriptions, validation, and error handling. The guidance includes JSON Schema, a format for defining inputs, and MCP, a protocol for connecting agent tools.
Choose and implement ways to manage data in React apps, from values held by individual components to shared data and cached server responses. Covers Redux Toolkit, Zustand, Jotai, and React Query, including migration from legacy Redux.
Review and shorten tool instructions for AI agents by testing overlap with parameter schemas, the definitions of accepted inputs. It also guides writing clear usage rules while preserving warnings backed by past failures.
Helps agents choose the right agentmemory tool through MCP, a protocol for connecting agents to tools. It explains tool roles and points to parameter references for saving, retrieving, organizing, and maintaining stored knowledge.
Use n8n-mcp tools to find workflow steps, check settings, and create or update automations. Provides guidance on tool arguments, templates, folders, credentials, and security audits so agents can choose appropriate operations.
Expose REST APIs as tools for AI agents through Google Cloud API Gateway using MCP, a protocol for connecting agents to tools. Covers OpenAPI migration, authentication, client connections, validation, and troubleshooting.
Add and troubleshoot a developer panel in Svelte 5 json-render apps. Inspect JSON screen definitions, edit application state, review action and streaming timelines, browse component catalogs, and select elements directly from the page.
Diagnose why an AI agent skips tools, passes incorrect arguments, or repeats calls. Get guidance on tool descriptions, schemas that define accepted inputs, execution flow, and mock tests before connecting to a real model.