Loading...
Loading...
Found 21 Skills
Analyze MSBuild binary logs to diagnose build failures by replaying binlogs to searchable text logs. Only activate in MSBuild/.NET build context. USE FOR: build errors that are unclear from console output, diagnosing cascading failures across multi-project builds, tracing MSBuild target execution order, investigating common errors like CS0246 (type not found), MSB4019 (imported project not found), NU1605 (package downgrade), MSB3277 (version conflicts), and ResolveProjectReferences failures. Requires an existing .binlog file. DO NOT USE FOR: generating binlogs (use binlog-generation), build performance analysis (use build-perf-diagnostics), non-MSBuild build systems. INVOKES: dotnet msbuild binlog replay, grep, cat, head, tail for log analysis.
Activate this when users need to understand extreme events (bubbles, crashes, mass hysteria, cults, mob behavior), diagnose systemic organizational failures, or assess the risk of multiple psychological/market/institutional forces aligning in the same direction. Typical trigger signals: the phenomenon described by the user "far exceeds what any single factor can explain"; the user attempts to explain an extreme outcome with a single cause; the user is concerned about "multiple adverse factors erupting simultaneously". Not applicable to conventional single-factor decision analysis or assessment of mild incremental changes.
Diagnose why a GAIA question failed — extract trace, classify failure mode, and propose a fix
When something goes wrong during a build, diagnose what type of failure it is before deciding how to respond. Targeted fix, hard reset, or full rethink — the right response depends on the right diagnosis.
Diagnose and fix GitHub Actions CI failures. Inspects workflow runs and logs, identifies root causes, implements minimal fixes, and pushes to a fix branch. Use when CI is failing, red, broken, or needs diagnosis.
Structured self-debugging workflow for AI agent failures using capture, diagnosis, contained recovery, and introspection reports.
Analyze and explain one or two EVM transactions using live Etherscan data and human-verifiable Etherscan evidence links. Use when a user provides a transaction hash or asks what happened, why a transaction failed, which contracts or internal calls were involved, where assets moved, whether a proxy implementation executed, which call reverted, or why two transactions behaved differently. Reconstruct the supported execution path, decode calls and events, summarize asset and permission changes, showcase the relevant Etherscan transaction, contract, token, label, log, and internal-transaction views, and provide plain-English, developer, support, or security-focused explanations with confidence and limitations. Do not use for broad wallet investigations, multi-hop laundering traces, or full contract audits.
Diagnose repeated command failures, stale build caches, branch drift, or contradictory evidence before attempting further code edits. Use when commands fail repeatedly, tests stay red after attempted fixes, build output contradicts source code, or the execution path is confused — even if the user does not explicitly say "fable-recover" (e.g. "still failing", "why did this fail again", "stuck in a failure loop", "diagnose this error"). Do NOT use for routine first-time test failures in fresh TDD (use fable-tdd).
Diagnose and repair reproducible, intermittent, environment-specific, or production-observed software failures by tracing evidence to a root cause. Use when a symptom exists but its cause is uncertain or when a proposed fix needs causal validation. Do not use for feature implementation, speculative cleanup, or a general review without a concrete failure.