테스트·보안 스킬

Coordinate eval, benchmark, load-test or batch campaigns on authorized SSH hosts or short-lived rented hosts, with isolated jobs, configured-path canaries, telemetry and evidence. Use manage-remote-resources for paid resource ownership and run-remote-builds for build-only offload.

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

Offload builds, tests, or artifact verification to authorized SSH hosts and isolated worktrees; synchronize remote fixes into dedicated coordinator commits and preserve reproducible build provenance. Use for spare development capacity and remote build troubleshooting. Paid provisioning requires a separate resource lifecycle contract.

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

Select established CTF and security-research tools for authorized artifact triage, web inspection, reversing, crypto, forensics, networking, and exploit validation. Use when a user provides a CTF-style tool catalog, asks which tools to use, or needs safe usage instructions for common offensive/security tools.

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

Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.

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

Passive code-review lane for authorized repositories, local checkouts, uploaded source archives, and diffs. Use when the security research agent needs deterministic candidate discovery before expensive AI investigation, scoped PR-style review, append-only evidence records, or independent revalidation of code findings.

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

Use common CLI, Kali, and shell tools to inspect web Targets, captured assets, logs, HAR/PCAP files, packages, and generated artifacts, then turn observations into Evidence, Security Signals, and ranked Hypotheses. Use when the user asks for web bug-hunting inspection, digital records, URL maps, crawling, endpoint discovery, JS bundle/package analysis, light forensics, or command-line investigation workflows.

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

Plan vulnerability research using conventional bug-hunting and pentest stage names, specialty playbooks, and a research-hypothesis-experiment loop. Use when designing a bug bounty workflow, selecting tools and strategies, building a decision tree, or turning a target/scope into a staged hunting plan.

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

Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.

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

Up-to-date Zig programming language patterns for version 0.17.0-dev (0.16.0 stable APIs plus the 0.17 deltas). Use when writing, reviewing, or debugging Zig code, working with build.zig and build.zig.zon files, or using comptime metaprogramming. Critical for avoiding outdated patterns from training data - especially std.net→std.Io.net (requires Io instance), std.time timestamps removed (use clock_gettime), std.Thread.Mutex/Condition/sleep removed (use pthreads), std.crypto.random removed, build system APIs (root_module, Compile methods→Module methods), I/O APIs (buffered writer pattern), container initialization (.empty/.init), allocator selection (DebugAllocator), ArrayList now unmanaged by default, @typeInfo lowercase fields (.@"struct" not .Struct), and removed language features (async/await, usingnamespace). Also covers 0.17.0-dev deltas: b.args→run_cmd.addPassthruArgs(), std.gpu→std.spirv, @bitCast logical-bit (endian-agnostic) semantics, build configurer/maker split, and the zig-pkg/ package directory. Also covers quality tooling Zig does not ship: coverage with kcov (and why in-file tests wreck the denominator), detecting unused private functions (neither the compiler nor zlint's unused-decls finds them), duplicate detection with jscpd, zlint (NOT the same-named X.509 linter in Homebrew), and the built-in fuzzer whose testOne now takes *std.testing.Smith rather than []const u8.

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

Review the current branch for bugs, intent fit, and test coverage; run or write tests; commit focused work; open or update a PR.

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

Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.

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

End-to-end smoke against the local rembric dev server (`pnpm run dev`, host Next.js dev on :3000). Apply when the user says "smoke", "probar contra docker", "dev:up", or after applying an OpenSpec change that touches HTTP (`apps/web/src/app/api/`), MCP tools (`packages/mcp/src/`), or DB migrations (`packages/db/src/migrations/`). Encodes bring-up, readiness verification, probe pattern and teardown — not the probes themselves.

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

Pragmatic testing guidance focused on confidence, behavior over implementation details, and integration-first coverage. Use when designing a test strategy, writing or reviewing tests, reducing brittle mocks, or deciding what is worth testing in an application or library.

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

Apply npm/pnpm supply-chain hardening when adding a dependency, editing package.json/.npmrc/pnpm-workspace.yaml, reviewing a lockfile change, or configuring CI install steps. Covers the 17 practices from lirantal/npm-security-best-practices.

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

Runnable end-to-end validation playbook for the Rembric TUI installer — catch breakage before merging/deploying, AND a sandboxed manual walkthrough to evaluate/iterate its UI/UX without polluting your real env. Apply before shipping any change touching `apps/plugin/install.sh`, the repo-root `install.sh` shim, any per-client `install.sh`/`uninstall.sh`, or distribution docs, or when you want to preview/try/demo the installer and polish how it looks and feels. Layered: CI-safe headless (vitest + `sh -n`), local install round-trips, operator interactive pty smoke, an optional full Docker `up` smoke, plus a sandboxed manual UX walkthrough. For the installer contract/what-not-to-break, see `rembric-tui-installer`.

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

Apply when creating, modifying, or reviewing any Rembric agent plugin. Triggers on changes under `apps/plugin/`, on new clients added alongside Claude Code / Codex CLI / Hermes Agent / opencode / Pi, on edits to `apps/plugin/mcp-bridge/`, `apps/plugin/bin/rembric-plugin-core.mjs`, per-client manifest changes, or plugin install/uninstall scripts. End-to-end validation against a local dev server (`pnpm run dev`, host Next.js on :3000) is mandatory whenever local testing is feasible.

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

Create and scaffold plugin directories for Codex with a required `.codex-plugin/plugin.json`, optional plugin folders/files, and baseline placeholders you can edit before publishing or testing. Use when Codex needs to create a new local plugin, add optional plugin structure, or generate or update repo-root `.agents/plugins/marketplace.json` entries for plugin ordering and availability metadata.

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

The Rembric TUI installer contract — the single, canonical install/setup/upgrade/uninstall path (`apps/plugin/install.sh`, fronted by the repo-root `install.sh` shim). Apply when touching `install.sh`, the root shim, any per-client `install.sh`/`uninstall.sh`, `marketplace.json`, or distribution docs (README, `docs/agents.md`, plugin/client READMEs). Covers the orchestrator model, what must not break, and where the source of truth lives. For running the validation suite, use `rembric-tui-installer-e2e`.

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

If CGM is not available, continue monitoring blood glucose with point-of-care testing as an alternative option. Trigger phrases include: "CGM is not available, what should we use for glucose monitoring?

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

Recommends real-time CGM with confirmatory bedside POC-BG monitoring for insulin dosing adjustments rather than POC-BG testing alone in adults with insulin-treated diabetes at high risk of hypoglycemia. Consider this approach for patients aged ≥65 years, BMI ≤27 kg/m², total daily insulin dose ≥0.6 units/kg, CKD stage ≥3, or recent hypoglycemia.

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

Evaluates basal insulin rates through basal rate testing across different time periods and adjusts as indicated. Triggered by clinician orders to 'Perform basal rate test to verify pump settings' or 'Check basal rates during periodic pump review'.

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

This skill recommends discontinuing glucocorticoid when the response to HPA axis recovery tests (morning cortisol, ACTH stimulation, or insulin-induced hypoglycemia) is normal, indicating adequate adrenal function recovery. Use in postoperative Cushing’s syndrome patients with at least one intact adrenal gland when test results are available.

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

Work up a patient with confirmed hypercalcemia using the PTH-dependent vs. PTH-independent algorithm — order the right second-tier tests (PTHrP, 25(OH)D, 1,25(OH)2D, SPEP/UPEP, urinary calcium/creatinine clearance ratio, TSH) to reach a diagnosis. Trigger when a clinician asks "what's causing this hypercalcemia", "how to work up high calcium", "what tests to order for hypercalcemia", "PTH is normal what next", "differential diagnosis of hypercalcemia", or shares a confirmed hypercalcemia and asks for the workup.

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

This skill recommends using biochemical tests to screen for hypercortisolism to detect recurrence in patients with ACTH-dependent Cushing's syndrome after surgical remission. It is triggered during postoperative follow-up when the HPA axis has recovered, annually, or sooner if clinical signs of hypercortisolism (e.g., weight gain, hypertension, glucose intolerance) or abnormal late-night salivary cortisol/UFC appear.

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