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
日本語の概要は準備中です。原文の説明を表示しています。
danstrem2/clawdbot-skill-master-pack☆ 22026年2月1日 更新
Complete startup operating system — from idea validation to Series A. Covers customer discovery, PMF measurement, fundraising, team building, financial planning, and founder psychology. Use when building, launching, pivoting, or scaling a startup.
日本語の概要は準備中です。原文の説明を表示しています。
johnalbertini14-glitch/openclaw-skills☆ 22026年2月26日 更新
Knowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."
日本語の概要は準備中です。原文の説明を表示しています。
Scoheart/agentskills☆ 22026年8月4日 更新
Find and validate email addresses using Snov.io via Chrome DevTools MCP. Takes LinkedIn profile URLs and returns verified emails. Replaces ZeroBounce.
日本語の概要は準備中です。原文の説明を表示しています。
ekatasingh1107/b2b-gtm-skills☆ 22026年4月12日 更新
Define and refine ICP segments with persona cards and validation
日本語の概要は準備中です。原文の説明を表示しています。
ekatasingh1107/b2b-gtm-skills☆ 22026年4月12日 更新
Guides an agent through reproducing, root-causing, fixing, and validating flaky tests in the PostHog monorepo. Use when a test fails intermittently in CI but passes on rerun or locally, when `hogli ci:insights` or the debugging-ci-failures skill classifies a failure as a flaky test, when given a GitHub Actions URL for a flaky job, when asked to check Trunk Flaky Tests for a test, PR, or master, or when asked to deflake, stabilize, or fix a flaky Jest, pytest, or Playwright test. Core discipline: reproduce locally before changing anything, fix the root cause (never mask it with sleeps, retries, or bigger timeouts), and prove the fix with an N-run validation loop sized to the observed failure rate. Stabilizing is not the only valid outcome — the skill also gates whether the test should exist, so deleting a test that catches nothing real, or re-leveling one that flakes because of the level it runs at, are first-class endings.
日本語の概要は準備中です。原文の説明を表示しています。
amplifthq/opentag☆ 02026年10月14日 更新