「address」の検索結果

Address unwanted dog behaviors through desensitization, counter-conditioning, and management. Covers reactivity (to dogs, people, sounds), separation anxiety, resource guarding, excessive barking, and leash pulling using force-free methods with systematic threshold management. Use when a dog shows reactivity toward other dogs, people, or stimuli; when separation anxiety causes destructive behavior or vocalization; when resource guarding is present; or when behaviors like excessive barking or leash pulling interfere with daily life — after basic obedience is established.

日本語の概要は準備中です。原文の説明を表示しています。

Use when building static archives with ar, stripping or converting binaries, mapping crash addresses with addr2line, or demangling C++ symbols. Not for ELF analysis: use elf-inspection.

日本語の概要は準備中です。原文の説明を表示しています。

Use when addressing review feedback in analyze or reception mode, or handling GitHub PR feedback in autonomous, interactive, or summary mode for a named PR target. Classifies, applies, replies, or summarizes comments.

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user asks to fix P0s, address critical issues, or work on priorities from the weekly product briefing. Don't use for non-P0 issues or local bug fixes.

日本語の概要は準備中です。原文の説明を表示しています。

Geocode an address, find places nearby, or compute a route.

日本語の概要は準備中です。原文の説明を表示しています。

Reads, searches and counts Claude Code session transcripts (the .jsonl files under ~/.claude/projects, subagents too) with the csift command-line tool, and ships hooks that re-inject compacted turns or record pending questions. Use when asked what a past or running session said, did, edited, spent or is doing now; when about to grep, jq or script over a transcript jsonl (a type=="user" filter overcounts the person's messages), count how many messages the person typed, tool calls or tokens, or claim something was never done or decided; to rebuild a lost file or plan from what a session wrote, extract pasted images, restore turns a compaction summary lost, find a subagent's own id when CLAUDE_CODE_SESSION_ID names the parent, wait on or message another session or subagent; or when csift prints "unknown label selector", "show needs an address", "looks like a session/agent id, not a project path" or "0 matches — a DEFINITIVE absence". Not for semantic or embedding search: csift matches regular expressions only.

日本語の概要は準備中です。原文の説明を表示しています。

当用户希望使用 msOpProf（`msprof op` / `msprof op simulator`）对昇腾 AI 算子做上板或仿真性能调优、解释 `aic-metrics`/`trace.json`/`visualize_data.bin`、选择 device vs simulator 路径、排查 `--soc-version`/`--export`/`signal 6`/`Bad address`/热点图或流水图相关问题，或要求生成固定分析报告模板（算子基本信息 / 关键数据 TOP5 / 核心瓶颈 TOP5 / 优化建议 TOP5）时，使用本技能。它负责先判定模式、输入形态与芯片/能力边界，再给出正确命令、结果解读、固定报告输出与高频踩坑规避；不要把经验案例当成通用规则。

日本語の概要は準備中です。原文の説明を表示しています。

Work with the @upstash/redis TypeScript/JavaScript SDK, a serverless HTTP-based Redis client for Next.js, Vercel, Cloudflare Workers, edge runtimes, and Node.js. Use when adding a cache (cache-aside, write-through, TTL and expiration strategies), session storage and user sessions, a key-value store, leaderboards and rankings with sorted sets, counters, distributed locks, queues with lists, streams and consumer groups, sparse index-addressed arrays and ring buffers (ARSET, ARINSERT, ARRING, ARGREP, AROP), embeddings and nearest-neighbour vector search stored inside Redis (VECTOR commands via redis.vector, separate from @upstash/vector), JSON documents, pipelines and MULTI/EXEC transactions, Lua scripting, read replicas, or full-text search, typo-tolerant search, facets, aggregations, and search over Redis stream entries with Upstash Redis Search (different from regular FT.SEARCH; also available for TCP clients via @upstash/search-redis and @upstash/search-ioredis). Also use when migrating from ioredis or node-redis, when a Redis connection is needed from a serverless function without connection pooling, when integrating @upstash/ratelimit, or when the user says Redis cache, KV store, session store, serverless Redis, or Upstash Redis. Also use when building AI agents on Redis with Upstash AgentKit (agent memory, chat history, RAG tools, tool caching, chat persistence, resumable streams, distributed locks) for the Vercel AI SDK, TanStack AI, or Vercel Eve. Supports automatic serialization/deserialization of JavaScript types.

日本語の概要は準備中です。原文の説明を表示しています。

Use when creating new skills, editing existing skills, or verifying skills work before deployment. Applies Test-Driven Development to process documentation — watch agents fail without the skill, write the skill that addresses those failures, then close loopholes.

日本語の概要は準備中です。原文の説明を表示しています。

Use when you need abuse-report history for an IPv4/IPv6 address — confidence score, total reports, distinct reporters, usage type. IP-only. Commonly invoked by /ip-investigation. Retrieval only.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a user asks to investigate, check, enrich, or characterize an IP address (IPv4 or IPv6). Chains VirusTotal, Shodan, AbuseIPDB, GreyNoise, OTX, and optionally Censys in parallel, then consolidates findings and prioritizes follow-up IOCs. Invoked by /cti-orchestrator when the target is an IP.

日本語の概要は準備中です。原文の説明を表示しています。

Triage and address GitHub PR review comments systematically—classify, respond, fix or defer with rationale. Use when a PR has review feedback, requested changes, or unresolved threads.

日本語の概要は準備中です。原文の説明を表示しています。

Deploy an Evil Twin (Rogue Access Point) to clone a legitimate Wi-Fi network's SSID and MAC address. By combining this with targeted deauthentication attacks, an attacker aggressively forces nearby victims to silently connect to the malicious AP, enabling pervasive Man-in-the-Middle (MitM), captive portal phishing, and credentials interception.

日本語の概要は準備中です。原文の説明を表示しています。

Identify and exploit SMTP Open Relays. This skill teaches how to test mail servers to determine if they process email delivery regardless of the sender or recipient domain, enabling attackers to spoof internal addresses and bypass basic anti-phishing controls.

日本語の概要は準備中です。原文の説明を表示しています。

Phase 4 of the feature-pipeline suite. Use this after /fp-review has posted a sandbox review comment — it reads the outstanding checkbox items, applies fixes, then watches CI until green (or exits cleanly so you can retry). Trigger phrases: "address review items", "fix review feedback", "resolve review checklist", "watch CI", "poll CI", "check if CI is green", "iterate on PR", "fp-iterate", "Phase 4", "after review comment", "fix the review issues and watch CI". Always bounded — max 10 poll rounds, never loops forever. Exits with a clear status: green (hands off to /fp-drift), still-pending (re-invoke), or failed (diagnose before touching anything).

日本語の概要は準備中です。原文の説明を表示しています。

Audit essays, reports, literature reviews, dissertations, proposals, and source-backed assignments for high-score academic quality. Use when the user asks whether a paper can get a high grade, wants teacher/rubric feedback addressed, needs a pre-submission review, or needs checks for strict rubric compliance, academic standards, prompt/rubric alignment, argument quality, comparative analysis, evidence hierarchy, table/figure integration, citation specificity, conclusion strength, academic language, source-claim integrity, or evidence boundaries.

日本語の概要は準備中です。原文の説明を表示しています。

Analyzes cryptojacking/coinminer malware by extracting mining pool endpoints (stratum), wallet addresses, algorithm and miner identifiers (XMRig and forks), and persistence or resource-control settings from static strings and config. Activates for requests to analyze a cryptominer, extract mining pool and wallet IOCs, or identify coinminer configuration.

日本語の概要は準備中です。原文の説明を表示しています。

Establishes a disciplined malware sample repository: content-addressed storage by hash, encrypted/password-protected archiving, consistent metadata records, and chain-of-custody tracking so samples are reproducible and safe to handle. Activates for requests to organize a malware repository, manage samples, or track sample metadata and provenance.

日本語の概要は準備中です。原文の説明を表示しています。

Analyzes position-independent code and shellcode by identifying GetPC/PEB-walk techniques, API-hash resolution loops, and relocation-free addressing so the payload can be disassembled at the right base. Activates for requests to analyze position-independent code, identify PIC techniques, or understand how shellcode resolves APIs without imports.

日本語の概要は準備中です。原文の説明を表示しています。

Sweep a PR's automated + human review comments and act on them — especially for material (large / logic-bearing) PRs. Handles "sweep the PR comments", "check PR review feedback", "address review comments", "did the bots flag anything", and the pre-/post-merge review pass on any non-trivial PR.

日本語の概要は準備中です。原文の説明を表示しています。

Prepare a day-one patch for a game launch. Scopes, prioritises, implements, and QA-gates a focused patch addressing known issues discovered after gold master but before or immediately after public launch. Treats the patch as a mini-sprint with its own QA gate and rollback plan.

日本語の概要は準備中です。原文の説明を表示しています。

Unity 6 platform targeting and build guide. Use when building for specific platforms, configuring build profiles, using platform scripting defines (#if UNITY_IOS, #if UNITY_ANDROID), optimizing for mobile, WebGL, or consoles, working with Addressables/asset bundles, or choosing between IL2CPP and Mono. Based on Unity 6.3 LTS documentation.

日本語の概要は準備中です。原文の説明を表示しています。

Unity async and coroutine correctness patterns. Catches common mistakes with Awaitable double-await, missing cancellation tokens, thread context after BackgroundThreadAsync, coroutine error swallowing, batch mode WaitForEndOfFrame, and Addressables handle leaks. PATTERN format: WHEN/WRONG/RIGHT/GOTCHA. Based on Unity 6.3 LTS documentation.

日本語の概要は準備中です。原文の説明を表示しています。

Unity scene and asset architecture decisions. Additive scene composition, Addressables vs Resources, AssetReference workflow, asset lifecycle coordination, loading screens. DECISION format: WHEN/DECISION/SCAFFOLD/GOTCHA. Based on Unity 6.3 LTS.

日本語の概要は準備中です。原文の説明を表示しています。