테스트·보안 스킬

Check added lines in a change for information identifying customers, prospects, partners, or outside individuals. Report locations and generic remediation without reproducing identities, and escalate cases where the information is already public.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking changes for customer and partner identities
• Reviewing documents and test data for identifying details
• Reporting disclosure locations without repeating identities

Checks published OpenWork desktop downloads for mac-arm64, verifying developer signatures, Apple notarization, and update metadata. It checks versions, download references, and file hashes, then records evidence to support a release rollout decision.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking signatures and notarization on published downloads
• Verifying update versions, asset references, and hashes
• Recording release verification evidence in a PR or issue

Guides review of pull requests from external forks, covering code ownership, contribution terms, security-sensitive changes, and tests tied to the reviewed commit. It produces a review record and supports moving changes to a maintainer branch when needed.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing external contributions before approval
• Checking code provenance and contribution terms
• Verifying security reviews and tests for a specific commit

Review code changes for newly introduced security issues with a plausible attack path. Produce findings for the Warden security summary, including affected lines, severity, a minimal fix, and observable conditions for confirming the issue is resolved.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking a PR for newly introduced vulnerabilities
• Reviewing CI changes that expose secrets or write access
• Inspecting Electron changes for unsafe permissions

Measure chat layout jumps while a response runs by tracking the Working line through CDP, a browser debugging connection. Count upward movements and compare the same prompt before and after changes to status lines, step rows, or folding behavior.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking layout jumps after changing progress displays
• Measuring jumps caused by collapsing content
• Comparing flicker before and after a UI change

Control a running OpenWork app from the shell to inspect UI changes and reproduce chat states. Start fresh sessions, select models, send prompts, wait for completion, capture screenshots, and run JavaScript, with no visible window by default.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Inspecting an OpenWork UI change
• Reproducing a chat state in a fresh session
• Capturing screenshots after a model finishes

Run Openwork end-to-end tests, which verify complete user journeys, locally or on Daytona. Check the exact commit and runtime, investigate failures or skipped tests, and report results with commands, counts, and an explicit overall verdict.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Running a single end-to-end test
• Verifying the exact commit intended for a PR
• Investigating skipped tests and missing prerequisites

Investigate failed tests, type checks, builds, and CI jobs by recording exact evidence and repeating checks in a clean comparison environment. Use the results to distinguish existing failures, newly introduced problems, environment issues, and unresolved cases.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking whether a failing test was already broken
• Investigating a failure that appears only in CI
• Distinguishing timeouts from environment problems

Reproduce chat errors, retries, parallel tool calls, and app creation in a running desktop application. Check how messages and cards appear, including interrupted replies, grouped steps, and error details.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Check error messages and retry progress
• Inspect text retained after an interrupted reply
• Review grouped parallel tool calls

Test a released archon binary through Homebrew or curl installation on macOS or a Linux VPS. Check version information, bundled workflows, Claude execution, and sensitive environment key removal, then clean up and report the results.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking a newly published release
• Reproducing a bug in a released version
• Verifying a hotfix after updating a release tag

Automate browser actions such as filling forms, clicking buttons, and switching tabs. Inspect page snapshots, network requests, and console messages to check website behavior, record interactions, and support work on Playwright tests.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking form submission and page navigation
• Investigating browser errors and network requests
• Recording browser interactions as video

Interpret n8n validation results and work through fixes for missing settings, broken references, and expression errors. Distinguishes blocking errors from advisory warnings, explains validation profiles, and guides review of automatic fixes and execution failures.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Understanding validation errors
• Deciding which warnings need attention
• Choosing a validation profile

Check mesh files for 3D printing by measuring geometry and comparing it with process-specific design limits. Get findings on wall thickness, overhangs, and supports, plus build orientation options and concrete redesign guidance.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Check whether a mesh meets printing design limits
• Find thin walls and unsupported overhangs
• Compare build orientations to reduce supports

Validate the staging NemoClaw Brev Launchable by checking its web deployment flow, environment access, deployed image, and preinstalled user journey. Report inference results and missing dependencies separately as advisory evidence outside automated end-to-end testing.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Check the staging Launchable web deployment flow
• Verify an existing environment's image and source commit
• Test onboarding and inference in the preinstalled environment

Run NemoClaw live end-to-end tests, which check complete workflows, or inspect existing release evidence. Routes requests to local or trusted GitHub workflows and reports the tested commit, results, workflow link, and relevant job links.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Run end-to-end tests for the latest pull request commit
• Run end-to-end tests for the current main commit
• Test working-tree source in a requested local run

Investigate failing or flaky NemoClaw end-to-end tests, which check complete workflows. Trace each assertion through its inputs and implementation, including cleanup and dependent jobs, and produce an evidence ledger to guide authorized repairs and reruns.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigate a failing end-to-end test
• Audit assertions that execution has not reached
• Review cleanup and dependent job requirements

Review a NemoClaw pull request for security risks by examining changed code, configuration, and dependencies. Assess nine categories and report findings with severity, file locations, and recommended fixes, alongside an overall assessment of whether it is safe to merge.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Review a pull request before merging
• Inspect changes linked to an issue
• Check authentication and credential handling

Continuously monitor automatic end-to-end tests on NemoClaw main, group failures by root cause, and coordinate fixes and peer reviews through GitHub. Track ownership and merge readiness while checking whether later runs confirm each repair.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Continuously monitor automatic test failures on main
• Coordinate repair ownership across maintainers
• Review peer fixes and assess merge readiness

Recheck older NemoClaw bug reports against the reported and newest releases, then prepare evidence-backed recommendations for maintainers. It documents reproduction results and proposed updates for approval without automatically closing issues.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Rechecking older bug reports
• Comparing reported and newest releases
• Preparing evidence-backed issue updates

Test CodexBar against real provider services, check application settings, and verify menu contents. Use command-line checks and visual evidence to distinguish authentication problems, API mismatches, and display issues before a release.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking provider connections before a release
• Investigating missing usage data or authentication failures
• Comparing menu contents with enabled providers

Maintain existing Handsontable browser tests built with Jasmine and Puppeteer. Covers asynchronous operations, simulated user input, assertions that work across themes, targeted test runs, and guidance for moving broken or unreliable tests to Playwright.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Updating an existing Jasmine browser test
• Fixing assertions that fail under different themes
• Checking simulated mouse, keyboard, and touch input

Create and update Playwright tests that check Handsontable interactions in real browsers. The skill guides test organization, reliable waits, element selection, and coverage across themes and bundles, while helping distinguish browser tests from unit tests.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Test keyboard navigation and cell editing
• Add regression coverage for a bug fix
• Check behavior across themes and bundles

Write and update Handsontable unit tests with Jest and type tests with TypeScript. Explains file placement, focused test runs, boundary cases, and checks for public types, while helping choose between isolated logic tests and browser tests.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Adding unit tests for calculations and data transformations
• Covering bug fixes and internal refactoring
• Checking TypeScript declarations and public exports

Create Playwright tests that capture table appearance and compare screenshots with reference images using reg-suit. The skill covers checking each state before capture, adding demo routes, and choosing themes, browsers, and framework variants to test.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking table appearance after UI changes
• Adding screenshot tests for a new feature
• Comparing appearance across themes and browsers