2,482 件 ・ 関連度順
概要と使いどころ
Compare two images pixel-by-pixel and get a visual diff. Use when the user wants to compare their implementation against a design, spot differences between two screenshots, or verify visual regression.
日本語の概要は準備中です。原文の説明を表示しています。
Check color contrast ratios against WCAG AA and AAA accessibility standards. Use when the user wants to verify if their color combinations are accessible, check contrast between text and background colors, or audit a palette for accessibility.
日本語の概要は準備中です。原文の説明を表示しています。
Stop and consult this skill whenever your response would include specific facts about Anthropic's products. Covers: Claude Code (how to install, Node.js requirements, platform/OS support, MCP server integration, configuration), Claude API (function calling/tool use, batch processing, SDK usage, rate limits, pricing, models, streaming), and Claude.ai (Pro vs Team vs Enterprise plans, feature limits). Trigger this even for coding tasks that use the Anthropic SDK, content creation mentioning Claude capabilities or pricing, or LLM provider comparisons. Any time you would otherwise rely on memory for Anthropic product details, verify here instead — your training data may be outdated or wrong.
日本語の概要は準備中です。原文の説明を表示しています。
Guide 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.
日本語の概要は準備中です。原文の説明を表示しています。
Verify HitKeep tracking setup and automatic event collection. Use when installation status, missing pageviews or events, WordPress or script installs, automatic outbound clicks, downloads, form submissions, hostname mismatches, blockers, consent, CSP, or the difference between tracker failure and analytics interpretation is in question.
日本語の概要は準備中です。原文の説明を表示しています。
Improve existing code without changing behavior: scan smells, simplify, dedupe, reuse utilities, and verify after edits. Use for refactor, cleanup, simplify, reduce duplication, extract method, dead code, or code smells. No PR.
日本語の概要は準備中です。原文の説明を表示しています。
Ship completed work: verify locally, commit related changes, push, create or update the PR, watch CI/reviews, and fix until merge-ready or escalated. Use for "ship it", "create PR", "handoff", or finished code needing delivery.
日本語の概要は準備中です。原文の説明を表示しています。
Verifying system resilience via load testing, contract testing, chaos engineering, and mutation testing. Use for limit verification, non-functional testing, or reliability validation.
日本語の概要は準備中です。原文の説明を表示しています。
Verifying YAGNI, cutting scope, and proposing complexity reductions. A 'subtraction' agent questioning the justification for every feature, dependency, doc, and config. Does not write code.
日本語の概要は準備中です。原文の説明を表示しています。
Verifying spec compliance: extracts ACs from specs, adversarially checks conformance, generates BDD scenarios and traceability matrices. Use when impl must be proven to match a PRD/SRS/AC.
日本語の概要は準備中です。原文の説明を表示しています。
Web search, online retrieval, real-time information query, search engine search, Reddit and other community platform discussions, external site posts and trending topics. Trigger when users need to search for the latest information online, look up recent news or trends, query real-time data, research topics via search engines, browse Reddit or community discussions, discover external site posts and trending topics, obtain any online content, web search, online lookup, real-time information, news search, Reddit, trending topics, search engine. Even if the user does not explicitly say "search", trigger this skill whenever their intent involves obtaining real-time web information or verifying current facts.
日本語の概要は準備中です。原文の説明を表示しています。
A harness that makes Opus (or any Claude model) behave like Fable — it enforces seeing a task through to the end, with evidence and verification, as procedure. Use when starting a multi-step task (2+ sequential stories), long autonomous work, debugging or root-cause investigation, building render/executable artifacts (HTML, SVG, games, charts), or when the user says "fablize", "see it through", "verify as you go", "split into goals".
日本語の概要は準備中です。原文の説明を表示しています。
Write or fix a profile.yml — pick the right resource kind for each file, bind operating references, and verify the install layout before publishing. Use when creating a ForgeCat profile, adding a skill/agent/rule/hook to one, or when `forgecat validate` or `plan` reports something unexpected.
日本語の概要は準備中です。原文の説明を表示しています。
Design a fact-checking protocol for AI-generated text, extending SIFT with AI-specific adaptations for hallucination detection. Use when students need to verify AI claims and citations.
日本語の概要は準備中です。原文の説明を表示しています。
Grounds every implementation decision in official documentation. Use when you want to verify an approach against the official docs before implementing it, or when you want authoritative, source-cited code free from outdated patterns. Use when building with any framework or library where correctness matters.
日本語の概要は準備中です。原文の説明を表示しています。
Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MCP server to be configured.
日本語の概要は準備中です。原文の説明を表示しています。
Subjects every non-trivial decision to a fresh-context adversarial review before it stands. Use when you want every assumption cross-examined before proceeding, when stress-testing a plan for hidden failure modes, when correctness matters more than speed, when working in unfamiliar code, when stakes are high (production auth, security-sensitive logic, a high-stakes migration, irreversible operations), or any time a confident output would be cheaper to verify now than to debug later.
日本語の概要は準備中です。原文の説明を表示しています。
Validate built features through conversational UAT
日本語の概要は準備中です。原文の説明を表示しています。
Retroactively verify threat mitigations for a completed phase
日本語の概要は準備中です。原文の説明を表示しています。
Search the live web and read full pages with You.com. Use whenever a task needs information newer than training data or from outside the codebase: current library docs and API references, changelogs and release notes, breaking changes, error messages, package versions, pricing, news, or any claim to verify with cited sources. Works keyless through the free MCP profile when no You.com credentials are configured.
日本語の概要は準備中です。原文の説明を表示しています。
Apply evidence-first engineering discipline to any agent-built software project: fact discovery before action, evidence-calibrated status reporting, explicit change boundaries and stage gates, controlled confirmation for risky or external actions, sensitive-information redaction for anything shared publicly, and resumable continuity after interruptions. Use when users ask an agent to take over an existing codebase, deliver a feature across stages, verify whether work is actually complete, judge release readiness, or keep conclusions honest about what is proven versus assumed. This foundation skill is domain-neutral; vertical suites (for example mini-program engineering) build on it by adding domain facts and platform rules.
日本語の概要は準備中です。原文の説明を表示しています。
Verify mini-program implementations and fixes with risk-calibrated evidence across static checks, unit tests, integration tests, state matrices, simulators, real devices, cloud environments, and release artifacts. Use when users ask to test, validate, accept, regression-check, quality-check, confirm readiness, or determine whether a mini-program feature is actually complete. Binds results to a source and build fingerprint, records commands and observable evidence, separates passed, failed, blocked, and not-run layers, prioritizes the next highest-information check, and never converts local success into device, cloud, release, or formal acceptance claims.
日本語の概要は準備中です。原文の説明を表示しています。
Acquire and verify finite environment, data, weight, and baseline inputs.
日本語の概要は準備中です。原文の説明を表示しています。
Post-deploy monitoring. Use when verifying a deployed app is healthy after deploy or launch — auto-fires from launch/deploy. Checks HTTP status, response times, error detection, and smoke test report.
日本語の概要は準備中です。原文の説明を表示しています。