Use when a batch (desktop or mobile) release reaches awaiting_verdict or was rolled back - read-only checks that the published artifact really exists and is served, and the exact yank step for a bad tag
日本語の概要は準備中です。原文の説明を表示しています。
4,455 件 ・ 関連度順
概要と使いどころ
Use when a batch (desktop or mobile) release reaches awaiting_verdict or was rolled back - read-only checks that the published artifact really exists and is served, and the exact yank step for a bad tag
日本語の概要は準備中です。原文の説明を表示しています。
Write board comments the way a colleague does — lead with the finding, a few lines, no preamble or process narration. Use when about to call add_task_comment or comment_on_pull_request, or when deciding whether something deserves a comment at all.
日本語の概要は準備中です。原文の説明を表示しています。
Guide for Kimix opencode-style HTTP server (FastAPI + SSE), including route definitions, builtin endpoints, and app.post usage.
日本語の概要は準備中です。原文の説明を表示しています。
Guide for using KimiX API utilities covering kimix, kimix.utils, kimix.base, kimix.dag, kimix.network, kimix.server, kimix.parser, kimix.cot, kimix.retrieval, kimix.summarize, and kimi_agent_sdk.
日本語の概要は準備中です。原文の説明を表示しています。
Build, modify, audit, repair, optimize, debug, and deploy agents with Agentforce Agent Script. TRIGGER when: user creates, reviews, or changes .agent files or aiAuthoringBundle metadata; asks to fix AgentScript, audit an existing agent, run an AgentScript health check, common-pitfall review, or baseline-versus-candidate repair loop; changes a response, action, subagent, route, state flow, or Agent Spec; previews, debugs, deploys, publishes, or tests agents; uses sf agent generate/preview/publish/test; or manages Agentforce MCP servers, tools, assets, or authentication. DO NOT TRIGGER when: Apex, Flow, Prompt Template, Experience Cloud, or general Salesforce CLI work is unrelated to Agent Script; or the primary input is a production session or trace ID rather than an agent artifact.
日本語の概要は準備中です。原文の説明を表示しています。
Write, run, and analyze structured test suites for Agentforce agents — functional AND security. TRIGGER when: user writes or modifies test spec YAML (AiEvaluationDefinition); runs sf agent test create, run, run-eval, or results commands; asks about test coverage strategy, metric selection, or custom evaluations; interprets test results or diagnoses test failures; asks about batch testing, regression suites, or CI/CD test integration; requests security testing, OWASP LLM Top 10, red-teaming, penetration testing, prompt-injection tests, a security grade, or a vulnerability assessment of an agent. DO NOT TRIGGER when: user creates, modifies, previews, or debugs .agent files (use agentforce-generate); deploys or publishes agents; writes Agent Script code; uses sf agent preview for development iteration; analyzes production session traces (use agentforce-observe); performs a static safety review of .agent file content (use agentforce-generate Section 15).
日本語の概要は準備中です。原文の説明を表示しています。
Analyze production Agentforce agent behavior using session traces and Data Cloud, and manage Agent Health Monitoring (AHM) alerts. TRIGGER when: user queries STDM session data or Data Cloud trace records; investigates production agent failures, regressions, or performance issues; asks about session traces, conversation logs, or agent metrics; wants to reproduce a reported production issue in preview; runs findSessions or trace analysis queries; creates, lists, updates, or deletes an AHM data alert on an agent metric (escalation rate, deflection, etc.); asks why an alert is not firing or wants to check whether alerts have fired (notification counts, or the per-alert Incidents view). DO NOT TRIGGER when: user creates, modifies, or debugs .agent files during development (use agentforce-generate); writes or runs test specs (use agentforce-test); uses sf agent preview for local development iteration; deploys or publishes agents.
日本語の概要は準備中です。原文の説明を表示しています。
Phase G of a WinForms-to-Avalonia migration: decompose oversized UI state and orchestration, harden asynchronous workflows and external boundaries, preserve composition lifetimes, keep Headless tests process-isolated, and update ownership documentation. Use only when an explicit migration has post-port structural or resilience debt, or when the orchestrator routes here. Baseline input security belongs in the phase that introduces the boundary, not only here.
日本語の概要は準備中です。原文の説明を表示しています。
Guides and best practices for working with Neon Serverless Postgres. Covers getting started, local development with Neon, choosing a connection method, Neon features, authentication (@neondatabase/auth), PostgREST-style data API (@neondatabase/neon-js), Neon CLI, and Neon's Platform API/SDKs. Use for any Neon-related questions.
日本語の概要は準備中です。原文の説明を表示しています。
Build production-grade components for React, Vue 3, and Svelte 5 with all states (loading, empty, error, success, idle), TypeScript strict, WCAG 2.2 accessibility, server components (RSC), and compound component patterns. Includes scaffold script, reference patterns, and template files for React and Vue. Use when user asks to create a UI component, frontend module, or design system component. Do NOT use for page layouts (use landing-craft), routing, or state management architecture (global stores).
日本語の概要は準備中です。原文の説明を表示しています。
Run 150+ AI apps via inference.sh CLI - image generation, video creation, LLMs, search, 3D, Twitter automation. Models: FLUX, Veo, Gemini, Grok, Claude, Seedance, OmniHuman, Tavily, Exa, OpenRouter, and many more. Use when running AI apps, generating images/videos, calling LLMs, web search, or automating Twitter. Triggers: inference.sh, infsh, ai model, run ai, serverless ai, ai api, flux, veo, claude api, image generation, video generation, openrouter, tavily, exa search, twitter api, grok
日本語の概要は準備中です。原文の説明を表示しています。
Use only after explicit Codex `$superloopy:superloopy-backend` or Claude Code `/superloopy:superloopy-backend` invocation, a backend task beginning with leading `loopy` or `루피`, or an active Superloopy loop routes backend work here. Relevant work includes backend application boundaries, APIs, persistence, migrations, transactions, background jobs, caches, events, reliability, security, and runtime database-agent tools. Plain API, server, database, SQL, or agent vocabulary does not activate this workflow.
日本語の概要は準備中です。原文の説明を表示しています。
Audit and improve website readiness for AI agents using the Cloudflare "Is It Agent Ready?" scanner (isitagentready.com). Covers scanning via API, interpreting results, generating implementation prompts, and fixing every check. Use when the user mentions "agent ready", "isitagentready", "AI agent scan", "agent readiness", "agent-ready score", "MCP server card", "agent skills index", "markdown for agents", "content signals", "web bot auth", "agent discovery", "RFC 9727", "RFC 8288", "RFC 9728", "SEP-1649", "WebMCP", "ARD", "ai-catalog", "x402", "UCP", "ACP", or wants to make a website discoverable and usable by AI agents.
日本語の概要は準備中です。原文の説明を表示しています。
Sub-skill: Implement ARD (Agentic Resource Discovery). Publish /.well-known/ai-catalog.json so agents can discover MCP servers, A2A agents, skills and API tools (agenticresourcediscovery.org / ai-catalog).
日本語の概要は準備中です。原文の説明を表示しています。
Master Coolify operator for self-hosted deployment platform. Use when the user mentions 'coolify', 'deploy on coolify', 'list/restart/redeploy applications', 'view coolify logs', 'coolify API/CLI', 'manage coolify servers/databases/apps', or 'coolify context'. Automates deployments and management via REST API or official CLI.
日本語の概要は準備中です。原文の説明を表示しています。
Audit, score, and compare repositories containing portable Agent Plugins against the official Agent Plugins specification. Use when asked to review a plugin repo, check plugin.json or mcp.json conformance, assess bundled skills and MCP servers, produce an evidence-cited 0–100 plugin scorecard, identify release blockers, or compare two agent plugins side by side.
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive skill for building, migrating, and maintaining Astro v7 projects. Covers best practices from the official AGENTS.md, the v6→v7 migration path, validation of breaking/deprecated patterns, AI-enhanced dev server usage (background mode, JSON logging), advanced routing with src/fetch.ts, route caching, Sätteri Markdown, and the Rust compiler. Use when the user mentions 'Astro', '.astro files', 'astro dev', 'astro build', 'islands architecture', 'content collections', 'SSG', 'SSR adapter', 'upgrade to Astro 7', 'migrate Astro', 'Astro v7', 'Astro v6', 'Sätteri', 'route caching', 'Astro.cache', 'astro dev --background', 'src/fetch.ts', 'advanced routing', 'Hono + Astro', 'Rolldown', 'Vite 8', 'queued rendering', 'CDN cache provider', 'Astro AI', 'related content', 'related posts', 'vector embeddings Astro', 'astro-related-content', or asks about static site generation with Astro.
日本語の概要は準備中です。原文の説明を表示しています。
Art-direct and generate one high-craft minimal-zine bitmap from a landscape, portrait, person, object, product, food, plant, building, interior, photograph, mood, sentence, or article concept. Use when the user wants a standalone poetic poster, editorial cover, visual concept, aesthetic photo upgrade, photo-to-zine restyle, or a subject-aware minimal-zine image without the overhead of a social carousel. Chooses adaptive composition and a physically coherent print process, preserves subject identity, saves the final prompt, invokes the runtime-native image generator, and audits the raster result.
日本語の概要は準備中です。原文の説明を表示しています。
Plan, art-direct, generate, edit, and quality-check tactile minimal-zine bitmap imagery from almost any subject: landscapes, portraits, objects, products, architecture, interiors, existing photographs, moods, article ideas, cultural essays, data, reviews, and social-media card series. Use for 小红书图片, Instagram carousels, poetic posters, editorial covers, photo restyling, visual essays, evidence-aware explainers, or any request for aged paper, photocopy, risograph, letterpress, sparse type, and restrained single-ink character. Routes the subject before choosing composition, preserves identity and factual content when editing, saves reproducible prompts, invokes the runtime-native image generator, and audits the real raster output. Do not use for glossy commercial ads, deterministic UI/vector assets, or exact diagram rendering.
日本語の概要は準備中です。原文の説明を表示しています。
All-in-one ComPDF workflow for document conversion, OCR, data extraction, PDF editing, protection, compression, and watermarking. Use for any ComPDF Server API request that processes PDF, Office, HTML, CSV, RTF, TXT, or image files.
日本語の概要は準備中です。原文の説明を表示しています。
Scan a live web app with Playwright, extract all features, generate PRD/epics/stories with priorities and dependencies, export to Notion. Checks required MCP servers before starting.
日本語の概要は準備中です。原文の説明を表示しています。
Tmux skill for running background tasks. Use this skill when: 1. Before any tasks that can potentially run for more than 2 minutes (e.g.: package install, many tests, model training) 2. Before any tasks that are expected to run indefinitely in background (e.g.: web servers, port forwarding) 3. Bash tool reports `timeout after 120000ms` 4. User request to run tasks in background
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used for web search and content scraping via DuckDuckGo MCP Server.
日本語の概要は準備中です。原文の説明を表示しています。
S6 of see-it-ship-it: put it at a public URL. Secret scan first; static builds go to GitHub Pages at no cost (sign-up guide, device-code login, one question: it will be public); a server only when a backend is needed, cost asked once; then open the URL, rerun the acceptance on the live page, bind a domain if they want one.
日本語の概要は準備中です。原文の説明を表示しています。