테스트·보안 스킬

Strengthen existing tests with fast-check by checking properties across generated inputs. Find bugs that example tests miss and reduce failing inputs to small, reproducible cases. Property testing is available; the other listed workflows remain planned.

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

• Checking parser behavior across generated inputs
• Testing serialization and deserialization round trips
• Finding pure functions covered only by example tests

Build repeatable DeepEval tests for AI agents, chatbots, and applications that retrieve documents to answer questions. Reuse or generate evaluation datasets, inspect failures, and improve prompts, tools, or retrieval through repeated evaluation runs.

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

• Add repeatable quality tests for an AI agent
• Evaluate chatbot behavior across multiple conversation turns
• Generate evaluation datasets from documentation

Test LangBot through its WebUI and compare visible results with backend logs or network behavior. Use it to verify chat, model settings, bots, knowledge bases, and plugins, with recorded evidence for test results.

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

• Verify pipeline replies in Debug Chat
• Check model provider setup and test buttons
• Test bot, knowledge base, and plugin UI flows

Helps review application code, authentication, access controls, and dependencies for security flaws. Uses OWASP guidance and CVE reports, records of known vulnerabilities, to assess impact and recommend practical fixes.

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

• Reviewing application code for security flaws
• Assessing known vulnerabilities in dependencies
• Checking authentication and data access controls

Plan encryption, TLS connections, digital signatures, and key management using established cryptographic libraries. Get guidance on choosing algorithms, storing passwords, rotating keys, and avoiding implementation mistakes such as reused nonces or comparisons that reveal information through timing.

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

• Choosing encryption methods for stored data
• Reviewing TLS settings for encrypted connections
• Designing password storage and token signatures

Test and debug REST and GraphQL APIs using curl, httpie, Postman collections, or scripted tests. Check authentication, invalid inputs, pagination, and response details to identify failures that a successful status code alone may miss.

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

• Checking authentication and access permissions
• Testing invalid inputs and boundary conditions
• Debugging failed HTTP requests

Plan compliance work for SOC 2, GDPR, HIPAA, and PCI-DSS by connecting requirements to technical safeguards, responsible teams, policies, and audit evidence. Get practical guidance for ongoing operations and audit preparation.

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

• Planning a SOC 2 compliance program
• Designing personal data retention and deletion rules
• Organizing audit evidence and access reviews

Design evaluation systems that measure agent results across accuracy, completeness, citations, and tool efficiency. Build repeatable tests, compare changes against a baseline, and define quality checks that catch regressions before deployment and monitor production performance.

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

• Compare agent configurations against a baseline
• Catch quality regressions before deployment
• Measure the effects of context strategies

Check a paper's numerical consistency using fixed rules, then record blocking or warning decisions and outstanding findings. The workflow preserves a traceable correction history, while explicitly leaving broader semantic review unavailable in its Codex mode.

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

• Check numerical consistency before submitting a paper
• Record audit findings and required corrections
• Detect outdated audit reports after paper changes

Choose and run checks that cover a Verdaccio change, including affected packages, dependent packages, API tests, and relevant client or UI flows. Rebuild first and report coverage limits so passing results reflect the edited code.

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

• Verifying changes before committing or pushing
• Selecting tests for affected packages and their dependents
• Checking package manager or UI behavior

Guides developers in restricting server file access to approved directories. It covers validated download paths, agent file tools, local data connectors, and sandbox settings to address path traversal, where supplied paths escape their allowed location.

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

• Reviewing file download routes
• Restricting agent file access to a workspace
• Checking local file connectors for cloud deployment

Test local web applications with Python scripts using Playwright, a browser automation tool. Verify interface behavior, investigate problems, capture screenshots, and inspect browser logs, with a helper that manages one or more application servers.

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

• Verify buttons, links, and form behavior
• Investigate problems in dynamic web interfaces
• Capture screenshots of local applications

Review Python, JavaScript/TypeScript, and Go code for security issues using guidance for the project's languages and frameworks. Get prioritized findings, suggested improvements, or help writing new code with safer defaults.

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

• Review an existing application's security
• Create a report organized by severity
• Write new code with safer defaults

Analyze git history to map contributors to security-sensitive files, identify reliance on too few people, and find stale areas. Export CSV and JSON results for ownership reviews, graph exploration, and comparison with CODEOWNERS.

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

• Find stale security-sensitive code with few maintainers
• Check reliance on individual authentication or cryptography maintainers
• Compare CODEOWNERS with actual contribution history

Test local web applications with Python scripts using Playwright, a browser automation tool. Inspect rendered pages, exercise interface controls, capture screenshots and console logs, and use a helper to manage one or more application servers during tests.

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

• Verifying buttons, links, and form inputs in a local app
• Investigating unexpected interface behavior
• Capturing screenshots and browser console logs

Analyze a codebase to identify valuable assets, attack entry points, and realistic abuse paths. Produce a concise Markdown threat model that explains risk priorities, distinguishes existing protections from proposed mitigations, and makes assumptions explicit.

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

• Map attack entry points in a codebase
• Assess threats within a specific project directory
• Prioritize risks to sensitive data and credentials

Run MNN checks and regression tests on a host computer or Android device, with stage summaries and failure logs. A separate workflow benchmarks LLM prompt processing and token generation on real iPhones and iPads, including branch comparisons.

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

• Run static checks and host regression tests
• Verify selected backends on an Android device
• Benchmark LLM speed and compare branches on iPhone or iPad

Prepare a clean Doris package and run Docker regression tests, which check whether changes break existing behavior. Restore configuration and startup files from Git, build the test image, and investigate failures using configuration checks and runtime logs.

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

• Run Docker regression tests before submitting Doris changes
• Test without local configuration changes affecting results
• Investigate missing test suites or startup failures

Run clang-tidy static analysis, which checks code without executing it, on added or modified BE and Cloud C++ files. Focus diagnostics on changed lines, investigate bug, performance, and readability warnings, and verify fixes with another check.

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

• Check changed C++ code before committing
• Investigate clang-tidy warnings reported by CI
• Review changes against a specific branch

Validate OpenHarness through real model API calls on an unfamiliar project. Tests cover conversations across multiple turns, actual tool execution, and combined features, with guidance for distinguishing setup problems from product failures.

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

• Validate agent behavior with real model API calls
• Check context reuse across multiple conversation turns
• Test hooks, skills, and plugins together

Run repeatable, read-only checks on an Obsidian wiki to find broken or ambiguous links, isolated pages, missing metadata, empty sections, outdated index entries, and source-record issues. Review findings with paths, line numbers, and counts.

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

• Finding broken links and isolated pages
• Auditing note metadata and source records
• Reviewing empty sections and outdated index entries

Review source code, dependencies, and infrastructure settings for security issues. Find exposed credentials, unsafe input handling, and access control gaps, then organize findings into a report with severity levels, affected locations, and recommended fixes.

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

• Review code security before deployment
• Find API keys and passwords embedded in files
• Check dependencies for known vulnerabilities

Request a new API key or login through a single-use, expiring link. The submitted credential is encrypted and saved to the person's keychain, keeping secrets out of chat and making them available to the task.

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

• Collecting an API key that has not been saved
• Requesting an email and password through a form
• Creating a credential submission link for a teammate

Verify desktop UI changes through the Chrome DevTools Protocol, a connection for controlling the running app. Reproduce the user’s actual steps and compare screenshots, measured state, and console errors to establish evidence before and after a fix.

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

• Reproducing reported bugs in the running app
• Comparing UI behavior before and after a fix
• Checking state across navigation and reopening