843 skills · sorted by relevance
Recover from failed file and directory operations by switching to run_shell, a shell command tool. Create nested folders, write files, and verify each result before continuing with tasks that depend on those files.
Extract text, tables, and headings from Word documents when standard file reading tools fail. The workflow uses Python and python-docx through run_shell to recover document content for further review or analysis.
When Python execution repeatedly fails in execute_code_sandbox, use a file-based alternative: save the script, run it through the shell, and capture results or errors. The guidance covers paths, imports, timeouts, structured output, and optional cleanup.
Recover from failed code execution by simplifying code, switching to shell commands, or handing complex tasks to shell_agent. Explicit working directories and output checks help keep generated files in the expected location.
Recover document generation tasks by separating Markdown content creation, format conversion, and output checks. Uses pandoc to produce Word, PDF, or HTML files, making it easier to identify which conversion step failed.
Continue Python tasks when the e2b sandbox, an isolated execution environment, is unavailable. Guides switching from execute_code_sandbox to run_shell, preparing dependencies, checking execution results, and saving intermediate data between calls.
Recover from repeated sandbox execution failures by saving Python code to a script and running it through run_shell. Check output, error messages, and exit codes to confirm results or diagnose remaining execution problems.
Build or review SwiftUI interfaces using Liquid Glass on iOS 26 and later. Apply native glass effects to controls, group related elements, check interaction and transitions, and provide fallback visuals for earlier iOS versions.
Check whether a single tool outage, invalid input, or repeated retry can disrupt an entire agent workflow. Use dialogue tests to identify spreading errors, missing fallbacks, and uncontrolled retries, then document confirmed findings.
Choose a visual direction for landing pages using WebGL, a browser graphics technology. Balance brand style with readable copy, clear calls to action, mobile performance, accessibility, and implementation effort, then define fallbacks and build priorities.
Add animated backgrounds such as waves or fog with Vanta.js, which renders graphics through WebGL. Configure effects, integrate them into pages or React components, handle resizing and cleanup, and plan fallbacks for mobile devices.
Make 3D canvas output sharper on Retina and other high-density displays. Coordinate rendering and post-processing resolution, preserve pointer accuracy, and verify fixed 200% rendering or automatic scaling with measured performance and explicit fallbacks.
Set up a persistent Microsoft Testing Platform console host that applies code edits and automatically reruns tests. It covers package setup, test selection, and restarting the host when an edit cannot be applied while running.
Optimize .NET loops with SIMD, which processes multiple values in one operation, or review existing SIMD code. Check behavioral equivalence, memory safety, platform fallbacks, and benchmarks to establish whether the optimization is correct and worthwhile.
Connect Timeline Inspector’s Refine panel to an agent through a chat-based fallback loop. It returns animation adjustments, groups transitions by component and phase, and writes accepted timing changes to source files when apply jobs arrive.
Use when the user asks to "personalize the email", "add merge tags / dynamic content", "set up conditional blocks per segment", or "make first-name and product-recommendation fields fall back safely"; produces a merge-tag map with per-tag fallbacks, conditional-block rules with per-segment variations, a fallback-safety audit, and a PII guard on what may render, informing the SEND E (Engagement/personalization) dimension. Not for building the segments — use list-segment-builder; not for writing the base copy — use email-creative-builder; not for scoring EQS or running vetoes — use email-quality-auditor. 邮件个性化/合并标签/条件内容块/兜底默认值
The English summary is being prepared. Showing the original description.
Implement reliability patterns for Claude API: circuit breakers, graceful degradation, idempotency, and fallback strategies. Trigger with phrases like "anthropic reliability", "claude circuit breaker", "claude fallback", "anthropic fault tolerance".
The English summary is being prepared. Showing the original description.
Prepare the conversations with aging parents that everyone postpones — the driving talk, the money talk, the care-options talk, the moving talk — each with an opener that doesn't ambush, a dignity-first script, rehearsal against realistic resistance, and the fallback when it goes badly. Use when someone says 'I need to talk to my dad about driving', 'my mum won't discuss her finances', 'we need to talk about care', or is dreading a visit for exactly this reason. Produces the conversation plan, a rehearsal, and the small-steps fallback. A preparation tool, not family therapy — and it says so when the situation needs more.
The English summary is being prepared. Showing the original description.
Designing conversational flows for website chatbots and AI agents. Intent recognition architecture, branching logic, fallback handling, escalation to human, conversation analytics. Honest about scripted-bot (rigid trees, fail edge cases), hallucinating-bot (LLM without structure, makes things up), and structured-guided-conversation (LLM-powered with intent architecture and fallback discipline) patterns. Distinguishes chatbot DESIGN (this skill) from chatbot IMPLEMENTATION (engineering and platform work). Triggers on chatbot, conversational AI, AI agent, chat widget, intent design, conversational flow, bot escalation, LLM grounding. Also triggers when a chatbot is hallucinating, when a scripted bot is failing edge cases, or when a chatbot is being scoped for the first time.
The English summary is being prepared. Showing the original description.
What to do when a tool fails, an API hits a rate limit, or a site blocks scraping. Maps every primary tool to its best fallback so a single failure doesn't block the search.
The English summary is being prepared. Showing the original description.
React error boundary hierarchy, fallback UI patterns, offline-first fallback, retry mechanisms, and graceful degradation.
The English summary is being prepared. Showing the original description.
Guidance for .NET MAUI XAML and C# data bindings — compiled bindings, INotifyPropertyChanged / ObservableObject, value converters, binding modes, multi-binding, relative bindings, fallbacks, and MVVM best practices. USE FOR: setting up compiled bindings with x:DataType, implementing INotifyPropertyChanged or CommunityToolkit ObservableObject, creating IValueConverter / IMultiValueConverter, choosing binding modes, configuring BindingContext, relative bindings, binding fallbacks, StringFormat, code-behind SetBinding with lambdas, and enforcing XC0022/XC0025 warnings. DO NOT USE FOR: CollectionView item templates and layouts (use maui-collectionview), Shell navigation data passing (use maui-shell-navigation), dependency injection (use maui-dependency-injection), or animations triggered by property changes (use .NET MAUI animation APIs).
The English summary is being prepared. Showing the original description.
Create error boundaries, error handling, and fallback UIs for React applications. Use when implementing error handling, creating fallback components, or setting up error reporting.
The English summary is being prepared. Showing the original description.
Fix misleading Flutter/Dart test failures where expected data is empty ([]) or default values instead of the mocked response, caused by stale Mockito generated mocks or missing stubs being silently swallowed by try/catch in provider/repository code. Use when: (1) Test expects non-empty data but gets [], (2) Mock stubs for a method are set up but the code under test returns fallback/empty results, (3) A PR added new methods to a service class and tests that previously passed now fail with misleading "expected X, actual: empty" assertions, (4) "Generated files are out of date" CI error alongside test failures. The root cause is MissingStubError thrown by unstubbed mock methods, caught by production try/catch blocks, causing silent fallback to empty state.
The English summary is being prepared. Showing the original description.