165 skills · sorted by relevance
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.
Handle shipment delays, damage, loss, and shortages with workflows for gathering evidence, filing compensation claims, and negotiating with carriers. Prioritize cases by financial exposure and customer impact, and assess when to absorb costs or pursue recovery.
Write and review Java services using conventions for naming, immutable data, exception handling, project structure, and tests. Detects Spring Boot or Quarkus from build files and applies the relevant framework rules.
Write, review, and refactor modern C++ using the C++ Core Guidelines. Covers type safety, automatic resource cleanup, class design, exceptions, concurrency, and naming conventions, with examples and a checklist for identifying unsafe or inconsistent code.
Review multi-step forms to find information users must enter more than once. Suggest automatic filling, reuse options, and preserving data between steps, while explaining relevant accessibility requirements and exceptions for security or validity.
Review forms for autofocus that moves users past introductory content when a page loads. Suggest removing it or moving focus after user interaction, while considering exceptions for login pages and pages dedicated to search.
Create integration tests for syncable metadata entities in Twenty itself. Cover invalid inputs, validation errors, and successful data operations, using reusable GraphQL request helpers, error snapshots, and cleanup routines to organize the test suite.
Implement validation and migration action builders for syncable entities, data types handled by Twenty's synchronization system. This skill covers required fields, uniqueness, reference checks, and orchestration wiring, with validators that return errors without throwing exceptions or changing data.
Turn past classrooms and chat history into a reusable personal skill for course creation. It examines varied examples, checks recurring patterns and exceptions, and asks for corrections before saving instructions that reflect the user's workflow and quality expectations.
Write and refine Javadoc comments for Java types and members. Apply consistent summaries and tags for parameters, return values, exceptions, inherited behavior, code examples, version information, and deprecated members with suggested alternatives.
Write focused Java unit tests with JUnit 5, including tests that repeat checks across different inputs. Covers clear test structure, exception checks, mock objects that replace dependencies, and ways to organize test suites.
Review punctuation in code, comments, and text files using a policy that favors the plain hyphen over em and en dashes, while accounting for exceptions involving existing data and explicitly requested literary or news text.
Write C# unit tests with NUnit using clear naming, focused assertions, and independent test cases. Covers project setup, testing with multiple input values, exception checks, and replacing dependencies with mocks to test components in isolation.
Write focused C# unit tests with XUnit, including tests that run against multiple input datasets. Apply consistent naming, setup, assertions, shared fixtures, and mock dependencies to keep tests readable, independent, and organized.
Write consistent XML documentation comments for C# types and public members. Follow specific rules for summaries, parameters, return values, properties, exceptions, examples, and inherited documentation so API behavior and usage are clearly described alongside the code.
Keeps customer-facing CopilotKit Intelligence documentation consistent by applying an approved vocabulary to prose, navigation, buttons, and image descriptions. Checks disallowed alternatives and exceptions while preserving code identifiers and the labels users actually see in product controls.
Rewrite lengthy prompts, tool descriptions, and agent instructions into compact text while preserving requirements, exceptions, and exact values. The process records removed content and compares token counts, the units models use to measure text length.
Create and tune Falco rules to detect possible container escapes, where a container gains access to its host. Define detection conditions, alert priorities, and output fields, then refine exceptions to reduce false positives.
Build a repeatable process for Microsoft monthly security updates, from reviewing advisories and ranking vulnerabilities to testing, staged deployment, and verification. Helps teams set response deadlines based on risk and report remaining unpatched systems.
Build a tracking system for vulnerabilities that cannot be fixed on time. Define exception requests, approval workflows, alternative protective measures, expiration checks, and audit records so teams can track accepted risks and support compliance reviews.
Troubleshoot WxJava failures using logs, exceptions, and request details. The skill helps isolate configuration, access token, signature, payment certificate, callback, and network issues, then proposes a minimal fix with steps to verify the result.
Screens incoming nondisclosure agreements against an organization's criteria or stated defaults. Classifies each agreement into three review levels and produces a report covering flagged clauses, risks, suggested fixes, and recommended next steps.
Review SOC 2 Type II audit readiness through six questions about controls, the organizational safeguards assessed over an observation period. Identify evidence gaps, control changes, and exceptions, then organize readiness findings and three concrete next actions.
Find repeated tasks in recorded activity or starred examples, then describe their steps, exceptions, and human decisions. Assess a small automation candidate using captured evidence, available tools, permissions, and clear completion criteria.