'taxonomy' 검색 결과

Answer NemoClaw maintainer questions using policy references covering issue and pull request assessment, labels, project fields, releases, and competing contributions. It explains the relevant rules in plain language through a read-only workflow.

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

• Checking issue and pull request assessment rules
• Understanding labels and project fields
• Checking release inclusion and cutoff rules

Import existing notes and agent instructions into LifeOS by splitting content into sections and proposing destinations. Review uncertain classifications, approve selected groups, and retain source information alongside the imported material.

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

• Importing Obsidian or Notion exports into LifeOS
• Moving notes from an older LifeOS installation
• Reviewing and importing CLAUDE.md or Cursor rules

Build probability estimates from historical frequencies and supporting or opposing evidence. Structure forecasts with explicit assumptions and outcome criteria, update them as evidence changes, and assess past predictions using accuracy and confidence calibration.

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

• Estimating probabilities for technology or economic developments
• Weighing evidence for and against a forecast
• Updating forecast probabilities when new evidence appears

Select existing labels for Verdaccio pull requests based on the target release line and the substance of the change. Apply them when authorized, or report exact recommendations when reviewing someone else's PR or lacking permission.

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

• Adding labels immediately after creating a PR
• Reviewing missing or incorrect PR labels
• Choosing labels for a release-line port

Assess Verdaccio issues against the code, affected release lines, and related reports. Distinguish bugs from configuration problems or duplicates, then propose existing labels, next steps, and a reply draft backed by evidence.

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

• Classifying a newly reported issue
• Checking which release lines a bug affects
• Finding duplicates and related fixes

Audit server-side advertising measurement by comparing browser and server events, checking duplicate handling, consent, and data quality. Reconcile platform diagnostics with source logs and business conversions, then return prioritized findings, owners, and verification steps.

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

• Investigate missing or duplicated conversion events
• Compare browser and server event data
• Review consent and data handling before transmission

Analyze rejected plans and reviewer feedback to identify recurring concerns, changing expectations, and concrete prompt improvements. Produce an HTML dashboard from Plannotator archives, or use Claude Code plan rejection reasons when those archives are unavailable.

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

• Finding recurring reasons for plan rejection
• Understanding how review expectations changed
• Deriving planning instructions from past feedback

Collect product listings from Etsy category and subcategory pages, including prices, ratings, shop names, images, and advertising or shipping labels. Follow pagination to gather products for competitor comparisons, category research, or potential supplier discovery.

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

• Compare competing products in an Etsy category
• Research seasonal product listings
• Find potential suppliers by category

Find changes in observable behavior that existing tests could miss. Map public results to test assertions, identify gaps in boundaries, permissions, and calculations, and propose focused tests, with optional verification when requested.

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

• Check whether existing tests would catch a bug
• Find missing boundary and permission-denial tests
• Review exact amounts and rounding in financial calculations

Review existing tests using 19 research-backed test smell categories, meaning patterns that can weaken test quality. Get findings ranked by demonstrated risk, with precise code evidence and fixes suited to the test framework in use.

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

• Request a test review using formal academic categories
• Prioritize test problems by their demonstrated risk
• Find causes of flaky tests or misleading passes

Create UTM links, which identify traffic sources, and GA4 event specifications for marketing campaigns. Standardize names across advertising and email channels, with platform-specific parameter templates, implementation notes, and recommendations for checking tracking before launch.

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

• Create tracking links for campaigns across multiple channels
• Standardize campaign naming rules across a team
• Define GA4 events for purchases and form submissions

Investigate authentication gaps across single sign-on, APIs, and legacy login endpoints. The skill helps map entry points, compare their protections, test token trust between portals, and document whether a flaw grants access to protected accounts or functions.

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

• Checking legacy login endpoints left outside SSO controls
• Reviewing token trust between partner and admin portals
• Mapping authentication paths across websites and APIs

Prepare a /hunt security assessment by loading skills for the selected mode and, for red team work, detected platforms. Summarize the loaded set, select reporting formats, and check supplied credentials before authenticated testing.

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

• Preparing skills for a red team assessment
• Loading a web application security testing skill set
• Prioritizing platform skills across multiple hosts

Assess account takeover risks across password resets, email changes, JWT tokens, SSO, and recovery flows. The skill connects individual weaknesses into testable scenarios and requires proof that an attacker session can gain access to a separate test account.

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

• Review password reset links and token handling
• Check reauthentication for email and password changes
• Assess takeover risks involving JWT and SSO

Understand common web application vulnerabilities through organized explanations of their causes, impacts, and mitigations. Use the reference to review authentication, APIs, access controls, and configuration issues, or build checklists for security assessments.

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

• Learning vulnerability types and their causes
• Building a web security assessment checklist
• Reviewing authentication and API weaknesses

Manage a connected WordPress site through NotFair MCP, a connection for agent tools. Work with posts, pages, media, and comments, and carry out approved changes to design, settings, plugins, themes, or HTML files.

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

• Manage posts and pages on a connected site
• Work with media, comments, and taxonomy terms
• Make approved changes to site design and settings

Turn rough moderation requirements or existing policies into custom safety rules for NVIDIA Nemotron models. Produce a Markdown policy, a JSON category structure, and ready-to-use classification prompts with definitions, exceptions, examples, and rules for keeping conversations on topic.

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

• Turning moderation notes into a structured safety policy
• Adding custom categories and exceptions to an existing policy
• Defining labeling criteria with safe, unsafe, and ambiguous examples

Check installed DOCA versions across package metadata, application files, runtime tools, and BlueField system information. Use the results to investigate build and runtime mismatches, check feature availability, and understand NGC container version tags.

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

• Check whether installed DOCA versions agree
• Investigate build and runtime version mismatches
• Check feature support for a specific release

Run and supervise DOCA applications directly on an x86 host or BlueField Arm hardware. Covers process launch, hardware resource assignment, isolation between workloads, and troubleshooting application failures or BlueField recovery problems.

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

• Launching a DOCA application directly on hardware
• Investigating systemd restart loops
• Assigning CPU and device resources to multiple workloads

Run DOCA service containers on BlueField using YAML deployment files and standalone kubelet, the agent that starts containers. Check service readiness and troubleshoot startup failures, image downloads, missing mounts, and repeated restarts.

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

• Starting a DOCA service container on BlueField
• Investigating image download failures or restart loops
• Checking whether a running container's service is ready

Investigate DOCA build failures, runtime errors, and silent tools by checking each system layer. Get guidance on increasing log detail and collecting reproducible evidence for troubleshooting or a Developer Forum question.

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

• Identify the layer behind a DOCA build or runtime failure
• Increase log detail for a silent DOCA tool
• Collect reproducible evidence for a forum question

Monitors task execution for skill improvement opportunities: logs patterns, user corrections and methodology worth preserving to the workspace, turns them into skill updates in a weekly review, and flags repeating work as new skills. Use during ANY multi-step task, agentic workflow, or work session. Also triggers in post-task feedback discussions and when the user mentions skill observations, the observation log, or skill taxonomy. Also known as "One Skill to Rule Them All" — trigger on this phrase too. IMPORTANT: invoke this skill before the FIRST tool call of any session and before writing or proposing a plan — any turn that will involve a tool call counts. This sentence is the session-start trigger and the only activation layer that survives an unreachable config file; pair it with a CLAUDE.md instruction or a session-start hook (references/environments.md). A subagent dispatched by a session already running it does not run it: it writes nothing and puts its findings in its report.

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

Access protein metadata, function, taxonomy, and sequences across UniProtKB, UniParc, and UniRef. Use when searching for proteins, mapping identifiers, or retrieving functional annotations and publications. Don't use for sequence alignment, protein folding, or sequence similarity search (use specialized skills for those tasks).

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

Use when the user asks to "triage our comments, DMs, and mentions", "draft replies to this thread", "can we repost this fan post", or "set up inbox SLAs and an escalation path"; produces a ranked triage queue with register detection (sincere / ironic / performative / parasocial, sentiment-inversion table included — "this is so bad" under a comedy register is praise), a commenter taxonomy (troll monitor-only / rager / misguided / unhappy-customer / advocate) with a response-tier ladder and per-channel SLAs, an escalation matrix ending at the crisis path, a moderation ladder plus house rules for owned spaces, and a UGC curation-and-rights mode whose dated permission entries route to the channel registry — every reply is a ranked DRAFT a human posts; nothing is ever auto-sent. Not for launch-window feedback triage — use launch-feedback-synthesizer. 评论私信提及分诊/语域识别/回复草稿/UGC授权

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