'ept' 검색 결과

Accept or apply for a task on OpenAnt. Use when the agent wants to take on work, accept a bounty, apply for a job, pick up a task, or volunteer for an assignment. Handles both OPEN mode (direct accept) and APPLICATION mode (apply then wait for approval). Covers "accept task", "take this task", "apply for", "pick up work", "I want to do this".

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

Design error handling strategies for TypeScript and Python applications — exception hierarchies, Result/Either types, retry patterns, error boundaries, and structured error logging. Use when designing error handling architecture, choosing between exceptions and Result types, implementing retry logic, or building error recovery flows. Activate on "error handling", "exception hierarchy", "Result type", "retry pattern", "circuit breaker", "error boundary", "Pokemon exception". NOT for debugging specific runtime errors, logging infrastructure setup, or monitoring/alerting configuration.

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

Acceptance testing workflow for the Software Metrics Machine CLI e2e suite. Use when writing, extending, debugging, or reviewing bashunit acceptance tests under apps/cli/e2e, including command help checks, cached fixture flows, GitHub MSW-backed flows, local git repository fixtures, SMM_STORE_DATA_AT workspaces, and pnpm run test:cli:acceptance. USE FOR: CLI acceptance tests, e2e tests, bashunit, apps/cli/e2e, command smoke tests, persisted CLI output tests. DO NOT USE FOR: unit tests or Vitest tests (use tdd skill), linting (use lint skill), webapp browser tests.

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

Reads an accounts payable exception list (mismatches, possible duplicates, missing or exhausted purchase orders, missing receipts, vendor or bank detail differences) with any invoice, purchase order and receipt data supplied, and returns a DRAFT action sheet: per line, the exception as stated, the facts as read, the difference where both sides exist, one proposed next action for the accounts payable clerk to perform, who or what it needs, and a draft query, with UNKNOWN wherever the data is silent. Use when the user asks to "review these invoice exceptions", "work through the AP exception queue", "what should I do with these blocked invoices", "propose next steps for the three-way match failures" or "sort out the duplicate and missing PO invoices". Do not use for a purchase order log screened for anomalies, use purchase-order-anomaly-review instead; for an expense claim against policy, use expense-policy-precheck. Drafts for human review; never approves, authorises or signs off.

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

Design error handling strategies for TypeScript and Python applications — exception hierarchies, Result/Either types, retry patterns, error boundaries, and structured error logging. Use when designing error handling architecture, choosing between exceptions and Result types, implementing retry logic, or building error recovery flows. Activate on "error handling", "exception hierarchy", "Result type", "retry pattern", "circuit breaker", "error boundary", "Pokemon exception". NOT for debugging specific runtime errors, logging infrastructure setup, or monitoring/alerting configuration.

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

배송 지연, 파손, 분실, 수량 부족에 대해 증거 수집부터 배상 청구와 운송사 협상까지 정리하고, 손실액과 고객 영향에 따른 대응 판단을 돕습니다.

• 배송 지연이나 분실 대응
• 화물 파손 배상 청구 준비
• 운송사 요금이나 책임에 대한 이의 제기

Hand accepted artifacts to the environment where work will continue, such as a code agent, desktop app, GitHub, or Figma. Record each destination in the artifact manifest, a tracking record that preserves earlier export history.

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

• Hand reviewed artifacts to Cursor, Claude Code, or Codex
• Return edited artifacts to their source Figma file
• Send accepted artifacts to GitHub through a PR

Find recent earthquakes by date and minimum magnitude, then review their location, depth, and USGS source. World Monitor also provides a concern score combining magnitude, depth, and proximity to known nuclear test sites.

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

• Review recent earthquakes above a chosen magnitude
• Check earthquake locations and depths within a date range
• Inspect events near known nuclear test sites

Represent dependency trees, taxonomies, and other hierarchies inside a Poincare ball, a geometric model for hierarchical distances. Use tree depth for radius and text embeddings for direction, then measure distances to examine the encoded structure.

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

• Analyze subtrees in module dependencies
• Examine structural patterns in class hierarchies
• Organize concepts by taxonomic relationships

Manage coding work from issue intake through implementation, review, deployment, and acceptance checks. Track each completion requirement against fresh evidence, with defined retry limits and explicit escalation when progress needs human input.

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

• Taking a ready issue through implementation and verification
• Coordinating implementation, review, and deployment handoffs
• Checking runtime behavior against acceptance criteria

Analyze a custom protocol in a CTF sandbox and reproduce an accepted exchange. Recover message boundaries, checksums, and session state, then build a small replay program that preserves the required message order.

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

• Recover message boundaries in an unknown protocol
• Reconstruct handshake steps and session state
• Build a replay program for a captured exchange

Trace OAuth and OIDC sign-in flows in a CTF sandbox, from redirects through token exchange to application acceptance. Show where tokens become a recognized identity or permission, and preserve the smallest reproducible flow.

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

• Trace sign-in redirects and callback parameters
• Inspect state, nonce, and PKCE validation
• Check how tokens become application identity or permissions

Trace how JWT, JWS, and JWE tokens become accepted identities or privileges in a CTF sandbox. Examine headers, key selection, and claims, the token's attributes, then preserve a minimal reproducible path demonstrating validation confusion.

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

• Inspect token headers and key selection in a CTF sandbox
• Trace how token claims become application permissions
• Build a minimal reproduction of token acceptance confusion

Investigate Kerberos delegation, which lets services act on another identity, in a CTF sandbox. Trace delegation settings, issued tickets, and service acceptance to document a reproducible trust path and the privileges it actually grants.

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

• Identifying constrained, unconstrained, or resource-based delegation
• Tracing S4U steps and issued authentication tickets
• Verifying ticket acceptance and resulting privileges

Trace server-side request forgery, where a server fetches a supplied URL, through internal services and metadata endpoints in a CTF sandbox. Document credential scope and distinguish successful token extraction from access actually accepted by another service.

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

• Tracing server-side requests to internal services
• Checking metadata access and token scope
• Distinguishing token extraction from accepted access

Implement Python error handling with early input checks, appropriate exception types, and clear messages. Handle individual failures in batch jobs, preserve error context for debugging, and use Pydantic models to validate structured input.

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

• Validating user input and API parameters
• Designing exception types and clear error messages
• Continuing batch jobs after individual failures

Plan an OpenMAIC lesson or course series backward from lasting understanding and evidence of learning. Connect central questions, practical assessment tasks, and learning activities so students can apply concepts in new situations.

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

• Design a lesson backward from learning goals
• Plan a course series around a shared concept
• Create practical tasks that demonstrate understanding

Trace how one idea developed across stored notes and records. Identify its earliest documented mention, clearest expression, changes of stance, contradictions, abandoned branches, and current form, with dated evidence and explicit gaps where sources are missing.

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

• Trace an idea to its earliest documented mention
• Review changes and contradictions in your thinking
• Clarify your current view on a topic

Update CRM opportunity fields such as stage, close date, amount, and next steps. See the exact before-and-after values, apply only requested or accepted changes, and verify the saved record through a link.

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

• Advance an opportunity to another stage
• Change a close date or deal amount
• Update next steps or forecast category

Turn a new feature into user stories: short descriptions of what people need and why. Each story includes a design reference and testable acceptance criteria, with scope intended to fit within one sprint.

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

• Breaking a new feature into backlog items
• Defining testable acceptance criteria
• Sharing user needs alongside design references

Check whether development tasks are ready for implementation by reviewing acceptance criteria, design decisions, dependencies, and required evidence. Receive one of four verdicts for each task, with specific gaps and suggested fixes.

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

• Checking a task before assigning implementation
• Reviewing all tasks in the current sprint
• Finding ambiguous acceptance criteria

Document a technical decision in an architecture decision record, or ADR. Capture its context, alternatives, and consequences, assign a record number, and distinguish a proposed decision from an accepted one so dependent work reflects its actual status.

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

• Recording the reasons behind a technical choice
• Documenting alternatives and consequences of a design decision
• Creating numbered records alongside existing architecture decisions

Break a game concept into the systems it needs, including supporting systems that are easy to overlook. Map dependencies, assign priorities by development stage, and create an index showing the recommended order for detailed design.

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

• Identifying the systems a game concept requires
• Finding dependency cycles and bottleneck systems
• Choosing systems for the minimum playable version

Evaluate a machine learning GPU cluster during a cloud trial or acceptance test. Measure GPU computing performance, communication within and between machines, and local and shared storage, then compile the results into a dated Markdown report.

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

• Evaluating trial GPU machines from a cloud provider
• Running acceptance tests for a GPU cluster
• Measuring GPU performance under load from neighboring GPUs