Plugins

2 plugins

Create Accessible Form

Design and implement a form that minimizes friction, prevents errors, and is accessible.

4 skills · plugin

Bug Finding Pipeline

Install this pack to detect bugs, security issues, and logical errors in your branch changes.

9 skills · plugin

Results for “errors”

13 skills

handling-rust-errors

HASH error handling patterns using error-stack crate. Use when working with Result types, Report types, defining custom errors, propagating errors with change_context, adding context with attach, implementing Error trait, or documenting error conditions in Rust code.

Finds root cause before applying fixes for errors, crashes, regressions, failing tests, broken behavior, and screenshot-reported defects. Use when users report in any language errors, crashes, broken behavior, regressions, failing tests, screenshot evidence, or something that used to work and now fails. Not for code review or new features.

046-love-505e88f9

Provides contact information and contribution guidelines for a project, including repository links and instructions for reporting errors.

Audits type safety documentation against the live codebase and fixes errors, gaps, or stale information to keep docs authoritative.

brycewang-stanford

Compile LaTeX paper to PDF, fix errors, and verify output. Use when user says "编译论文", "compile paper", "build PDF", "生成PDF", or wants to compile LaTeX into a submission-ready PDF.

Audits and rewrites user-facing copy across web and mobile codebases, improving clarity, tone, and actionability of labels, errors, CTAs, and empty states.

More results

matlab-optimize-memory

Guides the 7-step MATLAB memory optimization workflow: baseline, profile, identify, optimize, measure, verify, report. Use when asked to reduce MATLAB memory usage, find memory bottlenecks, fix out-of-memory errors, or optimize memory-intensive code.

brycewang-stanford

Use when compiling a LaTeX paper, debugging LaTeX errors, building a paper PDF, or when a .tex file fails to produce output. Handles engine detection (xelatex vs pdflatex), bibliography systems (biber vs bibtex), and multi-pass compilation.

Find authoritative guidance for installing, configuring, operating, securing, and troubleshooting OpenClaw, including channels, model providers, Gateway operations, tools, plugins, automation, nodes, multi-agent routing, and CLI errors. Use for any question or maintenance task involving an OpenClaw installation.

microsoft-code-reference

Look up Microsoft API references, find working code samples, and verify SDK code is correct. Use when working with Azure SDKs, .NET libraries, or Microsoft APIs to find the right method, check parameters, get working examples, or troubleshoot errors.

Record observable skill test runs for debugging. Use when the user wants to test, dry-run, debug, inspect, or compare how a Codex skill behaves on a concrete request; creates a local non-overwriting Markdown report with the visible process, files read, commands run, changed artifacts, errors, and a brief behavior summary. Does not certify skill quality or replace user judgment.

brycewang-stanford

Correct grammar errors, typos, and improve academic readability in LaTeX, Markdown, or plain-text manuscripts. Scans the document once, then walks through every issue one-by-one asking for approval before applying each fix. Trigger when the user says "readability", "check grammar", "fix typos", "proofread for grammar", "improve readability", "polish wording", "语言润色", "修语法", or asks you to clean up the prose in a paper/chapter/section without wanting full content restructuring.

architectural-analysis

Performs deep architectural analysis of a specified module, directory, or feature area by examining structural coupling, data flow, concurrency patterns, risk, and SOLID alignment. Use when the user wants to assess, evaluate, or review the architecture, design quality, dependency structure, coupling, cohesion, or technical debt of an existing part of the codebase. Not for investigating specific bugs, runtime errors, or failures — use investigate. Not for test planning — use automated-test-planning. Not for file-level code review — use code-review. Not for researching open-ended options, prior art, or how something works — use research. Not for designing a new interface or contract — use design-an-api. Not for writing documentation or architectural decision records.