'invoke' 검색 결과

Migrate existing PowerShell Pester tests through major versions from v3 to v6. The skill guides assertion updates, setup restructuring, mock changes, and execution configuration, using before-and-after test results to investigate failures while preserving what each test checks.

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

• Migrating Pester tests one major version at a time
• Fixing tests broken by a Pester upgrade
• Updating legacy Should and Invoke-Pester syntax

**[DEPRECATED in v1.3 — common path uses bb-invoke-yosys' embedded ABC]** 独立调用 ABC（Berkeley Logic Synthesis）做逻辑优化，仅 `mapping_effort=high` 等高级调优场景使用。触发场景：(1) bb-invoke-yosys `chain_to_abc=true` 时；(2) 显式 /bb-invoke-abc 调试。

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

Learn to create, discover, invoke, secure, evaluate, package, and port Agent Skills through one interactive lesson at a time. Practical checkpoints and quizzes track demonstrated progress in a local file, so later sessions resume where you stopped.

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

• Learn to build and invoke a minimal Agent Skill
• Understand discovery and automatic routing
• Check permission, sandbox, and trust boundaries

Discover what a paired phone or wearable currently supports, then run the requested device, app, camera, media, or smart-home action. Check each device's published capabilities and permissions, and report the actual outcome or any execution errors.

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

• Check which actions a paired device supports
• Run supported device controls or app actions
• Use available camera or media actions

Search Windows PowerShell logs for traces of Empire, a framework used after a system is compromised. Identify characteristic launch commands, encoded code, module calls, and communication paths, then report suspicious events with timelines and severity scores.

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

• Investigating suspected Empire activity
• Checking encoded commands and communication paths
• Building detection rules from Empire indicators

Correctly call native (C/C++) libraries from .NET using P/Invoke and LibraryImport. Covers function signatures, string marshalling, memory lifetime, SafeHandle, and cross-platform patterns. USE FOR: writing new P/Invoke or LibraryImport declarations, reviewing or debugging existing native interop code, wrapping a C or C++ library for use in .NET, diagnosing crashes, memory leaks, or corruption at the managed/native boundary. DO NOT USE FOR: COM interop, C++/CLI mixed-mode assemblies, or pure managed code with no native dependencies.

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

ALWAYS invoke this skill before asking the user any technical question or offering options, and whenever they ask to be asked in plain words - "ask simple", "ask me simply", "ask me in plain words" - in any language. ALWAYS invoke it too when the user asks for your view on a technical choice: whether it is worth doing, more than the problem needs, or replaceable by something simpler, and which option you would take. Invoke it even when the code makes the answer look obvious: the checks are what make the answer more than a guess. Rewrites the question in plain words and always ends with one marked recommendation. A structural choice first passes six checks, shown as a table: effort now, simpler substitute, extra work later, lock-in, over-engineering, easy to undo. Doing nothing is always weighed.

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

Diagnose and fix parfor errors in MATLAB. Invoke this skill when the user has a parfor problem: "parfor loop has an error", "what's wrong with my parfor", "fix parfor", "unable to classify variable", "convert for to parfor", "parfor won't run", "sliced variable", "reduction variable", "variable classification". Also invoke when you read a .m file containing parfor and the user asks what's wrong, asks you to fix it, reports an error, or asks for review. Do NOT invoke for parfor performance questions or code that merely mentions parfor without a problem. ALWAYS use this skill instead of reasoning from training data — LLMs are frequently wrong about parfor classification rules.

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

Correctly call native (C/C++) libraries from .NET using P/Invoke and LibraryImport. Covers function signatures, string marshalling, memory lifetime, SafeHandle, and cross-platform patterns. USE FOR: writing new P/Invoke or LibraryImport declarations, reviewing or debugging existing native interop code, wrapping a C or C++ library for use in .NET, diagnosing crashes, memory leaks, or corruption at the managed/native boundary. DO NOT USE FOR: COM interop, C++/CLI mixed-mode assemblies, or pure managed code with no native dependencies.

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

Auto-invoked 7-phase workflow for complex-feature intent. Includes fasttrack mode for pre-approved specs. NOT for explicit user-invoked single tasks (see mk:cook); NOT for green-field autonomous builds (see mk:autobuild); NOT for simple bug fixes (see mk:fix).

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

Python Invoke task automation for DTX website. This skill should be used when running repo commands, backend tests via Docker, database migrations, updating invoke tasks, Docker operations, or workflow automation. Supports dev/test/prod environments with run, exec, up, down commands. References docs/development/invoke-tasks.md for complete command reference.

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

Create reusable agent skills from recurring tasks, or improve existing ones through test prompts and user feedback. Compare outputs with and without a skill, measure performance, and refine descriptions so skills are invoked for the right requests.

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

• Turning a recurring workflow into a reusable skill
• Improving an existing skill using feedback
• Comparing results with and without a skill

Choose the right engineering skills for a task and decide their order, from clarifying requirements to deployment. This guide also defines shared practices for stating assumptions, resolving uncertainty, keeping scope focused, and verifying completed work.

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

• Choosing a skill at the start of a development session
• Organizing the workflow for a new feature
• Selecting steps for debugging and code review

Manage command-line tools connected to OmniRoute through its API. Inspect tool status, read or change settings, manage Codex profiles and backups, and invoke tool plugins for automation tasks.

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

• Reviewing settings across connected tools
• Managing Codex profiles
• Checking tool status and logs

Check and control OmniRoute’s MCP server, which connects agents to tools. Inspect tool permission scopes, enable or restart the server, and invoke tools with JSON arguments from the command line.

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

• Check the MCP server’s operating status
• Enable, disable, or restart the server
• Inspect permission scopes for a tool

This metadata record supports the BMad Core Tools module. Use the separate bmad skill to set up the module or report its current state; this record is not intended to be invoked directly.

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

• Setting up the BMad Core Tools module through bmad
• Checking the module's current state through bmad
• Identifying the required setup entry point

Create reusable agent skills or improve existing ones through test prompts and user feedback. Compare output quality, execution time, and token usage against a baseline, then refine instructions and descriptions so the skill is invoked in appropriate situations.

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

• Turn a recurring workflow into a reusable skill
• Improve an existing skill using test results
• Compare quality, runtime, and token usage across versions

Assess claims when a request pushes for agreement, invokes authority, or creates artificial urgency. The skill guides responses that separate evidence from persuasion, present strong counter-evidence first, and clearly state what remains uncertain.

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

• Evaluating claims under deadline pressure
• Reviewing requests that invoke authority
• Responding to demands to endorse unsupported claims

Learn how to structure a user-invoked slash command through a small example. It shows where to place SKILL.md, how arguments reach the command, and which settings control tool access and model selection.

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

• Learning the file layout for a slash command
• Checking how command arguments are passed
• Reviewing tool permissions and model settings

Try the hello-codewhale example to receive a short greeting in your language. The response includes an exact identifying string, making the invoked example recognizable, and uses only the conversation without tools or external services.

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

• Try the hello-codewhale greeting example
• Check that the response identifies the invoked example
• Try a greeting in the language used in the conversation

Organize multi-step research and project work in Continue using Markdown files for plans, findings, and progress. When invoked, the skill reads saved planning context to support resuming work and reviewing earlier decisions.

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

• Resuming interrupted work in Continue
• Recording findings during research
• Tracking project phases and decisions

Access the equivalent of Claude Code's /pua:pro command from Codex CLI. The alias invokes the pro protocol for self-improvement, KPI performance measures, and configuration commands, with all processing kept local.

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

• Calling the equivalent of /pua:pro from Codex CLI
• Using the pro protocol for self-improvement and KPI commands
• Managing PUA settings locally

Internal — invoked headlessly by the peon eval server; humans should run `peon eval <pack>` instead. Execute one PeonPing reroll job — invoked headlessly by the peon eval server as: "Use the peon-ping-remix skill to execute the reroll job at <path>". Reads the job JSON (scope, category, index, caption), rewrites the affected sound prompt(s) to honor the caption, re-renders via scripts/pack-render.py, and logs the change to eval-log.json.

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

Internal — invoked headlessly by `peon create`; humans should run `peon create` instead. Author and render a brand-new PeonPing draft pack — invoked headlessly as: "Use the peon-ping-create-pack skill to draft a pack: name=<n> flavor=<f> vibe=<v> draft_root=<dir>. Follow the skill exactly." Authors all 7 CESP categories honoring the vibe, writes openpeon.json (draft-stamped) and prompts.json, renders every sound via scripts/pack-render.py, and always ends by telling the human to run `peon eval <name>`.

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