「failure」の検索結果

Work with the @upstash/workflow TypeScript/JavaScript SDK for durable, long-running workflows in serverless functions, multi-step processes that survive timeouts, retries, and restarts (built on QStash). Use when defining a workflow endpoint with serve(), running steps with context.run, sleeping for minutes to days without holding a function open, calling external APIs with context.call, waiting for an external event or webhook, invoking other workflows, configuring retries, failure callbacks, and a DLQ, controlling concurrency, rate, and parallelism, triggering, cancelling, or inspecting runs with the Workflow client, building AI agents and orchestrators, human-in-the-loop approvals, realtime updates, local development with the QStash dev server, adding middleware, or migrating workflows safely. Also use when the user asks for durable execution, step functions, saga or orchestration patterns, background jobs with checkpoints, or long-running tasks on Vercel, Next.js, Cloudflare Workers, or other serverless platforms.

日本語の概要は準備中です。原文の説明を表示しています。

Use when cutting, debugging, or verifying a pythinker-code (TSC monorepo) release — changesets flow, the ci release-packages version PR, release.yml anatomy, npm Trusted Publishing OIDC, native assets, brew tap, CDN redeploy, and their failure modes. Invoked by /release.

日本語の概要は準備中です。原文の説明を表示しています。

Design incident response for AI system failures. TRIGGERS - Use when user needs help with ai-incident-response related tasks.

日本語の概要は準備中です。原文の説明を表示しています。

Execute a plan file — parse phases, spawn parallel subagents, handle failures.

日本語の概要は準備中です。原文の説明を表示しています。

Execute git commits using the Conventional Commits specification. Use this skill whenever the user says "commit", "git commit", "/commit", "stage and commit", "make a commit", "save my changes", or asks to commit specific files or all changes. Also triggers on phrases like "push my changes" (commit first), "commit everything", "commit with message X", or whenever git diff/status suggests uncommitted work the user wants to save. Handles auto-staging, diff analysis, message generation, breaking change detection, batch splitting of unrelated changes, safe pushes, and pre-commit hook failures gracefully. Always use this skill rather than ad-hoc git commit commands.

日本語の概要は準備中です。原文の説明を表示しています。

Use when creating new skills, editing existing skills, or verifying skills work before deployment. Applies Test-Driven Development to process documentation — watch agents fail without the skill, write the skill that addresses those failures, then close loopholes.

日本語の概要は準備中です。原文の説明を表示しています。

Investigate stuck runs and execution failures by tracing Symphony agent-provider logs with issue/session identifiers; use when runs stall, retry repeatedly, or fail unexpectedly.

日本語の概要は準備中です。原文の説明を表示しています。

Investigate stuck runs and execution failures by tracing Symphony and Codex logs with issue/session identifiers; use when runs stall, retry repeatedly, or fail unexpectedly.

日本語の概要は準備中です。原文の説明を表示しています。

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

日本語の概要は準備中です。原文の説明を表示しています。

Master context engineering for AI agent systems. Use when designing agent architectures, debugging context failures, optimizing token usage, implementing memory systems, building multi-agent coordination, evaluating agent performance, or developing LLM-powered pipelines. Covers context fundamentals, degradation patterns, optimization techniques (compaction, masking, caching), compression strategies, memory architectures, multi-agent patterns, LLM-as-Judge evaluation, tool design, and project development.

日本語の概要は準備中です。原文の説明を表示しています。

Agent-browser usage guide. Read this before running any agent-browser commands. Covers the snapshot-and-ref workflow, navigating pages, interacting with elements (click, fill, type, select), extracting text and data, taking screenshots, managing tabs, handling forms and auth, waiting for content, running multiple browser sessions in parallel, and troubleshooting common failures. Use when the user asks to interact with a website, fill a form, click something, extract data, take a screenshot, log into a site, test a web app, or automate any browser task.

日本語の概要は準備中です。原文の説明を表示しています。

Investigate stuck runs and execution failures by tracing Symphony and Codex logs with issue/session identifiers; use when runs stall, retry repeatedly, or fail unexpectedly.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a task spans multiple steps, files, or unknowns — before planning the order of work, whenever about to report completion or success in any wording, and when picking the next action after a result, failure, or surprise. Also under deadline pressure, or when resuming work built on questionable foundations.

日本語の概要は準備中です。原文の説明を表示しています。

Systematically investigate and fix build errors, TypeScript errors, or test failures with minimal diffs.

日本語の概要は準備中です。原文の説明を表示しています。

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

日本語の概要は準備中です。原文の説明を表示しています。

Fix failing or flaky Playwright tests. Use when user says "fix test", "flaky test", "test failing", "debug test", "test broken", "test passes sometimes", or "intermittent failure".

日本語の概要は準備中です。原文の説明を表示しています。

Production-grade Playwright testing toolkit. Use when the user mentions Playwright tests, end-to-end testing, browser automation, fixing flaky tests, test migration, CI/CD testing, or test suites. Generate tests, fix flaky failures, migrate from Cypress/Selenium, sync with TestRail, run on BrowserStack. 55 templates, 3 agents, smart reporting.

日本語の概要は準備中です。原文の説明を表示しています。

"Apply public choice theory to analyze political decision-making as rational self-interested behavior. Use this skill when the user needs to evaluate government policy failures, rent-seeking costs, voting outcomes, or bureaucratic incentives, especially when the assumption of benevolent government is questionable.".

日本語の概要は準備中です。原文の説明を表示しています。

"Apply organizational ecology (Hannan and Freeman) to analyze population-level dynamics of organizational founding, failure, and selection. Use this skill when the user needs to explain industry-level patterns of birth and death rates, analyze structural inertia and liabilities of newness or aging, evaluate why adaptation is rare relative to selection, or when they ask 'why do most startups fail', 'why is this industry dominated by old firms', or 'why do organizations resist change despite environmental pressure'.".

日本語の概要は準備中です。原文の説明を表示しています。

"Apply information economics to diagnose and remedy market failures caused by asymmetric information. Use this skill when the user needs to analyze adverse selection, moral hazard, or signaling and screening mechanisms, especially in insurance, labor, credit, or product quality markets.".

日本語の概要は準備中です。原文の説明を表示しています。

"Apply AI ethics frameworks (fairness, accountability, transparency, privacy) to evaluate AI systems for algorithmic bias, explainability gaps, and value alignment failures. Use this skill when the user needs to audit an AI system for ethical risks, design fairness constraints, assess explainability requirements, or when they ask 'is this AI system fair', 'how do we detect algorithmic bias', 'what are the ethical implications of this AI deployment', or 'how do we make this model explainable to stakeholders'.".

日本語の概要は準備中です。原文の説明を表示しています。

Evaluate LLM agents and tool-using workflows—task success, tool accuracy, latency/cost, safety, and regression suites. Use when shipping agent features, comparing prompts/models, or debugging agent failures.

日本語の概要は準備中です。原文の説明を表示しています。

Auto-activates when managing agent-to-agent communication for validation failures and recursive fix cycles between validation specialists and main agent.

日本語の概要は準備中です。原文の説明を表示しています。

Detects version drift between machine-readable law YAML files and the binding geldende wettekst on wetten.overheid.nl at the YAML's claimed valid_from. Catches the silent failure where authored content lags behind ingevoerde wijzigingen — a YAML dated 2025-01-01 still carrying pre-Stb.-X text. Activate as Step 0 of every regelrecht-stelselanalyse micro-cycle, before any YAML edit. Strict by design: no bypass, no normalization beyond whitespace within a single paragraph; the geldende wettekst is leading and is mirrored verbatim, including errata. Use proactively when starting a stelselanalyse cycle, before harvest/migrate/extend, or when user mentions "drift", "versie", "geldende tekst", or worries that a YAML may be stale relative to wetten.overheid.nl.

日本語の概要は準備中です。原文の説明を表示しています。