162 skills · sorted by relevance
Generate reusable test helpers for Godot, Unity, or Unreal projects. Create utilities for checking results, building test objects, and replacing dependencies, following the project's configured test framework and existing test patterns.
Plan and write tests for changes to agent behavior, favoring integration tests that check components together. Identify key logic changes and user-visible behavior to cover, reuse existing helpers, and keep unit tests in dedicated files.
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.
Guide cross-platform app development with Avalonia UI and Zafiro using consistent architecture and coding conventions. Keep screen logic separate from UI dependencies, handle errors explicitly, and reuse existing helpers with ReactiveUI and DynamicData.
Guide code that consumes PSL parser output by choosing the right syntax tree layer. Use typed AST classes for structure and navigation helpers for positions, while avoiding text parsing shortcuts and direct access to internal storage.
Keep code changes small by checking whether they are needed, reusing existing helpers, and choosing standard or available tools first. It guides planning and implementation while preserving validation, security, accessibility, and the functionality the user requested.
Guide changes and reviews for SGLang’s Scheduler, TokenizerManager, and ModelRunner classes. Keep initialization in small, replaceable helpers and separate computation from coordination so large classes retain clear responsibilities and explicit dependencies.
Apply consistent architecture and coding conventions when building cross-platform apps with Avalonia UI and Zafiro. The skill guides separation of interface and logic, reactive data handling, explicit error results, and reuse of existing helpers.
Write JavaScript for n8n Code nodes to aggregate, filter, and transform workflow data. Guidance covers data access, output formats, execution modes, common errors, and performance choices when processing large numbers of records.
Implement Verdaccio fixes, features, or refactoring after checking whether existing settings or plugins already solve the problem. Place changes in the responsible component, reuse helpers, add tests and release notes, and validate affected packages.
Build Lightweight Charts™ plugins that add custom chart types, annotations, or overlays. The skill guides plugin selection, project setup, implementation with official helpers, testing of drawing and interactions, and preparation for publishing.
Edit and validate Bazel build settings using conventions specific to CodeQL development. Follow established helpers for packaging and operating system differences, add dependencies with checksums, and check changed targets while respecting the standalone build setup.
Help a spawned worker check which date-range helpers and external integrations are available and how to call them. The catalog explains environment settings, local broker access, and availability checks so the worker can choose tools for its task.
Build dashboard panels in plain TypeScript with automatic retries, saved panel settings, and clear error states. Keep panel-specific helper functions in the same file to make each component easier to understand and maintain.
Write JavaScript code in n8n Code nodes. Use when writing JavaScript in n8n, using $input/$json/$node syntax, making HTTP requests with this.helpers / the $helpers global, working with dates using DateTime, troubleshooting Code node errors, choosing between Code node modes, or doing any custom data transformation in n8n. Always use this skill when a workflow needs a Code node — whether for data aggregation, filtering, API calls, format conversion, batch processing logic, or any custom JavaScript. Covers SplitInBatches loop patterns, cross-iteration data, pairedItem, and real-world production patterns. Also use when asked why a Code node or workflow is slow, which execution mode is faster, or how to cut per-item overhead on large datasets. EXCEPTION — for the AI-agent-callable Custom Code Tool (@n8n/n8n-nodes-langchain.toolCode, a tool attached to an AI Agent), use the n8n-code-tool skill instead; it has a different runtime contract.
The English summary is being prepared. Showing the original description.
Provides patterns for testing utility classes, static methods, and helper functions. Validates pure functions, null handling, edge cases, and boundary conditions. Generates AssertJ assertions and @ParameterizedTest for string utils, math utils, validators, and collection helpers. Use when testing utils, test helpers, helper functions, static methods, or verifying utility code correctness.
The English summary is being prepared. Showing the original description.
Generate engine-specific test helper libraries for the project's test suite. Reads existing test patterns and produces tests/helpers/ with assertion utilities, factory functions, and mock objects tailored to the project's systems. Reduces boilerplate in new test files.
The English summary is being prepared. Showing the original description.
Activate for any work in the tests/e2e/ directory: creating or editing test files (tests/*.test.ts), page objects (pages/), helpers (helpers/), or vitest config. Enforces agent-browser conventions specific to this project.
The English summary is being prepared. Showing the original description.
Generate engine-specific test helper libraries for the project's test suite. Reads existing test patterns and produces tests/helpers/ with assertion utilities, factory functions, and mock objects tailored to the project's systems. Reduces boilerplate in new test files.
The English summary is being prepared. Showing the original description.
Reference for notebook manipulation scripts (notebook_helpers.py, notebook_tools.py). Use when working with Jupyter notebooks, analyzing structure, executing cells, or manipulating notebook content.
The English summary is being prepared. Showing the original description.
Dev-only check that a drafted spec for THIS baseline repo won't ship dev-tree references to consumer installs. Catches three failure modes — shipped SKILL.md prose that references paths under `src/`, `tests/`, `scripts/`, `obj/` as runtime invocations (in ```bash fences``` OR `inline backticks`, plus shipped `.mjs`/`.js`/`.sh`/`.py` helper-file imports); new Python helpers added under `.claude/skills/<slug>/` (shipped helpers must be `.sh` or `.mjs`/`.js` going forward); and imports of modules that aren't in `obj/template/.claude/manifest.json` (consumer won't have the file). The aggregate scanner (`scan-shipped-skills.mjs`) walks only baseline-owned skill dirs (via `owner: baseline` frontmatter) at top level — `references/` and other subdirs are documentation, not runtime. BLOCKER findings hard-block implementation entry; ADVISORY surfaces but doesn't block. Read-only — surfaces a punch list; maintainer edits the spec and re-runs until CLEAN.
The English summary is being prepared. Showing the original description.
Audits WordPress plugin or theme PHP code for internationalization (i18n) correctness — text-domain consistency, use of escaped translation helpers (esc_html__, esc_attr__, esc_html_e), correct placeholder helpers (sprintf with translator comments, _n for plurals, _x for context), no variable text-domains, no concatenation inside __() calls, presence of load_plugin_textdomain or load_theme_textdomain, and matching declared Text Domain in the plugin/theme header. Use before plugin/theme release, when reviewing contributor PRs, when adding new strings, when migrating to a new text domain, or when a translator reports issues with the .pot file.
The English summary is being prepared. Showing the original description.
Implement and review Ethereum hashing in JavaScript or TypeScript using Keccak-256. Learn which library helpers to use and avoid confusing it with Node's SHA3 when calculating function identifiers, signature hashes, storage locations, or addresses.
Review recent code changes from four angles: reuse, quality, efficiency, and whether fixes address underlying mechanisms. Combine findings, apply suitable cleanup with tests, and leave changes that could affect behavior for human review.