165 skills · sorted by relevance
Turn descriptions and existing notes into a standard operating procedure, a document explaining how work gets done. Capture process flow, responsibilities, detailed steps, exceptions, and metrics so teams can use it for handoffs or audits.
Audit Python SDK logs, exceptions, and telemetry for sensitive data exposure. Trace values to their sources, fix confirmed leaks, and test that redaction hides sensitive information while preserving the caller's expected behavior.
Use when you need to apply Java exception handling best practices — including using specific exception types, managing resources with try-with-resources, securing exception messages, preserving error context via exception chaining, validating inputs early with fail-fast principles, handling thread interruption correctly, documenting exceptions with @throws, enforcing logging policy, translating exceptions at API boundaries, managing retries and idempotency, enforcing timeouts, attaching suppressed exceptions, and propagating failures in async/reactive code. This should trigger for requests such as Exception handling; Use try-with-resources in Java code; Create exception chaining in Java code; Apply fail-fast validation in Java code; Review Java exception taxonomy and propagation. Part of Plinth Toolkit
The English summary is being prepared. Showing the original description.
Review styles written directly in HTML or embedded style blocks, and move suitable rules into external stylesheets. Check layouts across screen sizes and interaction states while preserving justified exceptions for critical styles and dynamic values.
Set up ShellCheck to inspect shell scripts without running them. Understand warnings, configure checks for the intended shell, document exceptions, and integrate analysis into CI, editors, or checks that run before commits.
Design application and API behavior when operations fail. Choose between exceptions and Result types, which explicitly represent success or failure, and improve retries, error messages, logging, and resource cleanup so failures are easier to handle and investigate.
Find answers to employee questions about leave, benefits, expenses, and other company rules using supplied handbooks or connected knowledge bases. Receive plain-language explanations with source references, exceptions, and contacts for questions beyond the documentation.
Review a deal before signing by scoring its margin and risks, flagging problematic contract terms, and recommending named human approvers. It prepares a consistent review packet for discount requests and policy exceptions without automatically approving them.
Design company discount rules across contract value, duration, payment terms, and strategic value. Build a discount matrix, define approval routes and required commitments for exceptions, and check the policy for gaps, contradictions, and margin violations.
Process emailed vendor invoices by extracting details, comparing them with purchase orders and invoice history, and recording duplicates, overcharges, or missing orders. Summarize results in Slack for human review; payment approval and execution remain with people.
Turn existing or proposed business processes into reusable standard operating procedures. Organize steps, roles, conditions, and known exceptions while marking missing details, producing clear handover documents without inventing approvals or responsibilities.
Add Sentry error reporting and performance monitoring to services, scheduled jobs, and database operations. Follow examples for capturing exceptions with useful context and measuring execution time through spans, which record individual operations for investigation.
Investigate and fix production errors reported in Sentry through MCP, a connection to external tools. Analyze error details and execution history, check them against source code, implement fixes, and verify them with tests and regression checks.
Review test files or suites for missing checks, hidden exceptions, unreliable timing, shared state, and maintenance problems. Get a severity-ranked report with specific locations, explanations, and concrete suggestions for improving the tests.
Organize shared build settings, tasks, and package versions across .NET projects. Review Directory.Build file placement and import order, centralize repeated configuration, and retain the settings that belong to individual projects or folders.
Writes a settlement letter on the right footing — and warns you when marking it 'without prejudice' won't actually keep it out of court. A genuine settlement letter is normally protected (the judge can't see it), but only if the substance is a real attempt to settle, and even then there are exceptions. The skill picks the correct footing — without prejudice (WP), without prejudice save as to costs (WPSATC / Calderbank), or open — drafts the finished letter, and surfaces the Unilever v Procter & Gamble exceptions that get WP material admitted despite the label, which a plain template won't flag. Built for juniors and in-house counsel drafting a settlement or Calderbank offer who need the footing right the first time. Use when the user asks to draft a WP letter, a Calderbank, a settlement letter, or wants to know whether material is likely protected from disclosure.
The English summary is being prepared. Showing the original description.
This skill should be used when the user asks about the invoice system (インボイス制度), qualified invoices (適格請求書), registration numbers (登録番号), input tax credits (仕入税額控除), the 20% special measure (2割特例), the 30% special measure (3割特例), tax-exempt businesses (免税事業者), transitional measures (経過措置), small-amount exceptions (少額特例), corrected invoices (修正インボイス), or any related topics. Trigger phrases include: "インボイス", "適格請求書", "登録番号", "仕入税額控除", "2割特例", "3割特例", "免税事業者", "経過措置", "少額特例", "修正インボイス", "返還インボイス", "簡易インボイス", "インボイス登録", "T番号", "適格請求書発行事業者".
The English summary is being prepared. Showing the original description.
Guides assessment and application of GDPR Article 49 derogation conditions for international data transfers in the absence of adequacy decisions or appropriate safeguards. Covers explicit consent, contract necessity, public interest, vital interests, public register, and compelling legitimate interests with restrictive interpretation per EDPB Guidelines 2/2018. Keywords: Art. 49, derogations, transfer exceptions, explicit consent, compelling legitimate interests.
The English summary is being prepared. Showing the original description.
Compare behavior across multiple versions of programs or repositories. Use when you need to analyze how functionality changes between versions, identify regressions, compare outputs and exceptions, or validate upgrades. The skill compares execution behavior, test results, outputs, exceptions, and observable states across versions, generating detailed reports showing behavioral divergences, potential regressions, added/removed functionality, and areas requiring validation. Supports multiple programming languages and can work with test suites or execution traces.
The English summary is being prepared. Showing the original description.
Codified expertise for handling freight exceptions, shipment delays, damages, losses, and carrier disputes. Informed by logistics professionals with 15+ years operational experience. Includes escalation protocols, carrier-specific behaviors, claims procedures, and judgment frameworks. Use when handling shipping exceptions, freight claims, delivery issues, or carrier disputes.
The English summary is being prepared. Showing the original description.
Use when diagnosing frontend build failures, runtime errors, UI anomalies, API/data problems, white screens, request failures, or unexplained production exceptions; Chinese triggers include debugging, debug, troubleshooting, positioning, error reporting, exceptions, white screens, request failures.
The English summary is being prepared. Showing the original description.
Design error handling strategies for TypeScript and Python applications — exception hierarchies, Result/Either types, retry patterns, error boundaries, and structured error logging. Use when designing error handling architecture, choosing between exceptions and Result types, implementing retry logic, or building error recovery flows. Activate on "error handling", "exception hierarchy", "Result type", "retry pattern", "circuit breaker", "error boundary", "Pokemon exception". NOT for debugging specific runtime errors, logging infrastructure setup, or monitoring/alerting configuration.
The English summary is being prepared. Showing the original description.
既存コード・既存関数・既存モジュールの暗黙契約を抽出するスキル。 戻り値型、副作用、例外、前提条件、境界条件、環境依存挙動を確認し、 reuse前のリスクを可視化する。名前やコメントではなく実際の挙動から 契約を読み取り、不一致を分類し、再利用可否を判定する。 Use when reusing legacy code, verifying actual behavior of existing functions, or extracting implicit contracts before implementation. Covers: hidden contract, implicit contract, reuse risk, legacy behavior, 暗黙契約, 既存資産調査. Analyzes return types, side effects, exceptions, preconditions, boundary conditions, and environment-dependent behavior.
The English summary is being prepared. Showing the original description.
Design error handling strategies for TypeScript and Python applications — exception hierarchies, Result/Either types, retry patterns, error boundaries, and structured error logging. Use when designing error handling architecture, choosing between exceptions and Result types, implementing retry logic, or building error recovery flows. Activate on "error handling", "exception hierarchy", "Result type", "retry pattern", "circuit breaker", "error boundary", "Pokemon exception". NOT for debugging specific runtime errors, logging infrastructure setup, or monitoring/alerting configuration.
The English summary is being prepared. Showing the original description.