Loading...
Loading...
Found 335 Skills
Forensic diagnostic report for LOCI — collects environment state, runs health checks, and writes a timestamped report when analysis fails or doesn't trigger. Invoke when: "bug report", "LOCI isn't working", "exec-trace didn't run", "skill didn't trigger", "MCP not connecting", "results are wrong", "results missing", "generate diagnostic", "something is broken", "debug LOCI", or any LOCI failure the user wants investigated.
Manage host-mode duoduo runtime settings and diagnostics. Use when the user asks to inspect or change daemon status, daemon config, daemon logs, Codex runtime enablement, debug log level, telemetry persistence, cadence frequency, or other persistent host-mode settings stored in ~/.config/duoduo/.env. Also trigger for Chinese requests such as 帮我启用 codex runtime, 打开 debug log, 关闭 telemetry, 调 cadence 频率, or 看看 duoduo daemon 配置.
Groundwater time series analysis and modelling using transfer function noise models. Use when Claude needs to: (1) Analyze groundwater level time series, (2) Model well responses to precipitation/pumping, (3) Calibrate aquifer parameters from head data, (4) Forecast or hindcast groundwater levels, (5) Decompose hydrological signals into components, (6) Compare response functions, (7) Perform model diagnostics and uncertainty analysis.
Guides hands-on actuarial analyst work for insurance, reinsurance, and pension—reserving and loss development (IBNR, triangles, chain-ladder diagnostics), pricing and rate indication support (experience, trend, credibility, basic GLM at spec level), data validation and model I/O review, reporting packs and workpapers, assumption application under actuary direction, and statutory tie-outs at analyst depth. Use when the user mentions actuarial analyst, loss development, IBNR, reserve analysis, rate indication, pricing support, actuarial workpaper, triangle analysis, credibility, experience study, actuarial reporting, or reserve roll-forward—not actuary sign-off (actuary), consulting engagements (actuarial-consulting), assumption governance (assumption-setting), ALM strategy (asset-liability-management), P&C legal depth (property-casualty-insurance), charts only (data-visualization), or ETL-only pipelines (data-scrubbing).
Analyze audio recording quality - echo detection, loudness, speech intelligibility, SNR, spectral analysis. Use when the user wants to check a recording's quality, detect echo or duplication in audio files, measure speech clarity, compare original vs processed audio, diagnose why a recording sounds bad, or analyze audio tracks from Blackbox or any call recording app. Triggers on audio quality, recording analysis, echo detection, check recording, sound quality, analyze audio, speech quality, PESQ, STOI, loudness, SNR, audio diagnostics, recording sounds bad, echo in recording, audio duplication.
Code-reviews Pluggy API integrations against Pluggy's official documentation (queried in real time via the Pluggy MCP, with a web fallback to docs.pluggy.ai when the MCP isn't connected) and returns a diagnostic report (✅/❌/⚠️) with file, line, and the code fix for each issue. Use WHENEVER the dev uploads integration files and asks to review, analyze, diagnose, or validate their Pluggy integration — or says things like "review my integration", "check my Pluggy code", "is this ready for production?", "Pluggy Doctor", "check my webhooks", "is my integration secure?", or the Portuguese variants "analisa minha integração", "revisa meu código da Pluggy", "tá tudo certo pra ir pra produção?", "checa meus webhooks", "minha integração tá segura?". Also trigger when the dev pastes/uploads code that clearly calls the Pluggy API (connect_token, GET /items, item/created webhooks, clientUserId, etc.) and wants to know if it's correct, even without saying "Pluggy Doctor". This skill is for REVIEWING existing code, not writing an integration from scratch.
Execute deterministic, reproducible historical backtests from a start date, end date, and strategy concept using the Alpaca CLI plus agent-written workspace code. Use when the user wants to backtest a strategy, simulate historical trades, or return trades, diagnostics, and reproducibility artifacts.
Pre-sprint diagnostic that determines whether a team should run a Foundation Sprint now, postpone it, or do prerequisite work first. Produces a Go / Conditional Go / Wait verdict with diagnosis, recommended preconditions, attendee list, and pre-sprint activities. Use when a team is considering starting a Foundation Sprint and wants a fast yes/no diagnosis before committing two days of facilitated work.
Use when the user needs to understand, diagnose, or prevent Protheus record locks and deadlocks -- covering RecLock/MsUnlock/SoftLock/LockByName semantics, BeginTran/EndTran transaction scoping, lock leak and deadlock diagnostics (TopMemoStatus, MonitorActiveLocks, DBAccess monitor, SQL Server/PostgreSQL/Oracle lock queries), and prevention patterns (BEGIN SEQUENCE/RECOVER, lock ordering). Also triggers on Portuguese phrasing like "registro travado", "trava de registro", "deadlock", "erro de lock", "travamento no Protheus", "quem esta travando o registro", or "RecLock nao libera".
UiPath causal investigation across every product, runtime, and activity package. Use when the primary outcome is an explanation, diagnosis, or root cause for undesirable existing behavior: faults, hangs, regressions, slowdowns, access loss, unexpected state changes, wrong or empty results, silent no-ops, or raw errors. Diagnostic intent outranks surface ownership for runtime behavior; invoke even when the prompt names only a job, folder, queue item, connector, connection, activity, trace, flow, agent, or other resource and another UiPath skill supplies inspection commands. Correlates runtime, configuration, history, and source evidence to find the originating fault and fix. Also covers UiPath Assistant desktop-app failures from a shared diagnostic archive (combined.log, Robot.log). For operating resources without causal investigation→uipath-platform; for applying a known source fix→the artifact owner; for build-time/CLI faults of a local artifact (pack, build, validate, bindings)→the artifact's skill.
【Resume】Pull up the last saved diagnostic archive and lay it out, so the user can continue from the last conclusions. Use together with xy-archive. Trigger when the user says “continue from last time”, “where did we leave off last time”, “what was the conclusion before”, “resume”, “pull up the archive”. Trigger: /xy-resume, "pick up where we left off", "what did we conclude last time"｜by Xiaoye
[Synthetic Report] Synthesize multiple xy-archive files accumulated under a project into a markdown diagnostic report arranged by timeline - one that can be sent to partners, archived, and reviewed three months later. Used when the user says "give me a report", "package these up", "put together one for the partners", "combine the conclusions from these sessions". Trigger: /xy-brief, "make me a report", "package these up"｜Made by Xiaoye