「address」の検索結果

Write a changeset file in the `hyperlane-registry` repo for a PR that adds, updates, or modifies warp route config / chain metadata / addresses. Canonical pattern — never run the interactive `pnpm changeset` CLI; write the file directly. Referenced by any skill that opens a registry PR.

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

EasyPost — shipping labels, rate comparison, package tracking, address verification, and insurance.

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

Provides domain knowledge and guidance for the Flare Data Connector (FDC)—attestation types, request flow, Merkle proofs, verifier/DA Layer, and smart contract integration. Use when working with FDC, cross-chain attestations, EVMTransaction, Web2Json, Payment, AddressValidity, proof-of-reserves, weather insurance, or Flare Developer Hub FDC guides and starter repos.

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

Regulatory compliance guidelines for life insurance policy administration transactions. Use when processing address changes (state-change impacts), beneficiary changes (community property, ERISA, minors), or any transaction that may trigger compliance review. Covers NAIC model regulations, state-specific rules, OFAC screening, and suitability requirements.

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

Operate the Ryuumonbuchi MCP server for headless Ghidra reverse engineering. Use when driving decompilation, disassembly, patching, type and symbol recovery, memory edits, transactions, and Ghidra project analysis through a Ryuumonbuchi server (stdio or streamable HTTP). Covers the safe read-only-first workflow, session and address discipline, mutation and transaction rules, headless.run, task and error recovery, raw ghidra.call/ghidra.eval/ghidra.script escape hatches, and a sleep/timing-gate bypass recipe.

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

Handles PR review comments and feedback resolution. Use when user wants to resolve PR comments, handle review feedback, fix review comments, address PR review, check review status, respond to reviewer, verify PR readiness, review PR comments, analyze review feedback, evaluate PR comments, assess review suggestions, or triage PR comments. Fetches comments via GitHub CLI, classifies by severity, applies fixes with user confirmation, commits with proper format, replies to threads.

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

Use at write time to vector/embedding memory — Grove content-addressed insertion, chroma/pgvector upserts, memory-consolidation promoting session traces to MEMORY.md, or embedding externally-ingested content. Scores each candidate record against a fixed panel of sentinel queries and quarantines any record that would become the nearest neighbor of too many unrelated queries — a hub — whether from adversarial poisoning or accidental over-generality. This is the memory-record-side sibling of skill-injection-guardian (file-side) and the write-side complement of memory-use-warrant (read-side). Quarantine, never silently drop; a human reviews. Backed by the admission-time hubness gate (arxiv 2606.19692v1). Triggers on inserting into vector memory, consolidating memory, and embedding stranger content.

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

Run this appropriateness check the moment you are about to integrate a retrieved long-term memory — a Grove content-addressed hit, a chroma/pgvector neighbour, a memory-consolidation digest, or a MEMORY.md line — into a response, especially anything touching private origins, Fox Companies IP, credentials, or Center Camp / consent-governed content. It answers a question intent-router never asks: not WHAT to fetch or HOW, but WHETHER a correctly-retrieved item should reach output. Relevance is not appropriateness — a perfect similarity match can still be a boundary violation. Default is FAIL-CLOSED: if in-context authorization is uncertain, the memory may inform behaviour but must not be surfaced. Backed by RBI-Eval (arxiv 2606.06055v1). Triggers on surfacing recalled sensitive memory into a response.

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

Follow up on open PRs in skillsaw — fix failing CI, address reviewer feedback, push updates, and validate backward compatibility. Use when an open PR needs maintenance.

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

Scans Cairo/StarkNet smart contracts for 6 critical vulnerabilities including felt252 arithmetic overflow, L1-L2 messaging issues, address conversion problems, and signature replay. Use when auditing StarkNet projects. (project, gitignored)

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

Bridge layer connecting the emerging agentic coordination protocol ecosystem (MCP, A2A, ANP, AGNTCY, AITP, LMOS, AAIF) to the plurigrid/asi skill graph. Maps protocol-level identity mechanisms (W3C DID, OAuth 2.1, IPSIE, Entra Agent ID, Agent Cards, passport.gay) into GF(3)-classified skills. The central unsolved problem — no unified identity across MCP+A2A+A2UI — is directly addressed by the bisimulation oracle composition.

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

Assess and address review feedback on GitHub PRs, GitLab MRs, or in conversation. Use when checking new reviews, responding to comments, rechecking after a push, or following up on approvals and change requests.

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

Auto-selects and enforces the strongest valid Python typing lane for the detected Python version and dependencies — no user input required. Use when adding or tightening type annotations, eliminating Any usage in internal code, designing boundary validators or parsers, choosing between stdlib typing (TypedDict, Protocol, dataclasses), Pydantic models, or Hypothesis property tests, addressing ty or mypy failures, or applying version-specific features (TypeIs, ReadOnly, PEP 695 generics, PEP 649 deferred evaluation). Enforces boundary isolation — raw payloads validated immediately at ingress and returned as typed internal objects.

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

Plan, provision, import, route, update, and verify Vapi phone numbers through the public API. Use for Vapi-hosted US PSTN numbers, explicitly requested SIP addresses, Twilio/Vonage/Telnyx or BYO carrier numbers, secure credential handling, assistant or squad routing, area-code requests, outbound limitations, and phone-provider troubleshooting.

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

Build a Total Addressable Market list: size the audience, source companies from ICP filters, then find contacts at those companies at scale.

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

Organizes an author’s response to peer review. Extracts every referee and editor point, tags severity and type, orders the revision by dependency, flags defensible pushbacks as questions, and builds a numbered comment → response → location letter whose substantive answers the author writes. Use when the user has referee reports, a revise-and-resubmit decision, or an editor’s letter and wants to plan the revision, draft the response letter, or check that every point was addressed. The reviewer-side twin is journal-review.

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

Show the manual page of an ASE skill, addressed by its full name, by any abbreviation of it, or by a description of its purpose, and list the entire skill catalog when no name is given. Use when the user wants the "manual", "man page", "manpage", or "help" of a particular ASE skill, or asks what a certain `ase-xxx-xxx` skill does.

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

Handle PR review feedback - understand reviewer comments, research their concerns, and help the user address them. The LLM explains what reviewers want and why; the user decides how to respond and writes the code. Use when you receive review comments on a submitted PR. Not for opening the PR in the first place, which is oss-submit-pr. If the feedback is a failing CI job, use oss-debug-ci.

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

Verify fix commits address security findings without introducing new bugs or regressions. Analyzes diffs for anti-patterns like removed validation, weakened access control, reduced error handling, reordered external calls, and changed integer operations. Generates structured FIX_REVIEW_REPORT with finding status tracking.

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

Expert coding skill for the full MapTiler platform — Cloud REST APIs, MapTiler SDK JS (built on MapLibre GL JS), native mobile SDKs, on-premise infrastructure, and vector tile schemas. USE WHEN the user wants to add a map to a web or mobile app, show locations or routes, display geographic data, build a store locator, create data visualizations on maps, add geocoding or address search, do reverse geocoding, look up elevation, do IP geolocation, fetch weather data, transform coordinates between CRS/EPSG, embed static map images, work with vector tilesets (Planet v4, Buildings, Contours, Outdoor, Ocean, Landcover, Cadastre), write MapLibre style expressions or data-driven styling, render 3D terrain, globe view, or 3D buildings extrusion, use satellite imagery, add markers, popups, heatmaps, or clustering, integrate maps in React, Vue, Svelte, Angular, Next.js, Leaflet, OpenLayers, Cesium, or deck.gl, build native maps on iOS (Swift), Android (Kotlin), Flutter, or React Native, self-host with MapTiler Server or generate tiles with MapTiler Engine CLI, or upload/manage tilesets via the Admin API. Also USE WHEN the user mentions MapLibre GL JS — the SDK extends MapLibre with built-in cloud services, helpers, and session billing.

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

Review a pull request end-to-end using GitHub CLI. Covers diff analysis, commit history review, CI/CD check verification, severity-leveled feedback (blocking/suggestion/nit/praise), and gh pr review submission. Use when a pull request is assigned for review, performing a self-review before requesting others' input, conducting a second review after feedback is addressed, or auditing a merged PR for post-merge quality assessment.

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

Design sustainable on-call rotations with balanced schedules, clear escalation policies, fatigue management, and handoff procedures. Minimize burnout while maintaining incident response coverage. Use when setting up on-call for the first time, scaling a team from 2-3 to 5+ engineers, addressing on-call burnout or alert fatigue, improving incident response times, or after a post-mortem identifies handoff issues.

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

Design a compliance architecture that maps applicable regulations to computerized systems. Covers system inventory, criticality classification (GxP-critical, GxP-supporting, non-GxP), GAMP 5 category assignment, regulatory requirements traceability, and governance structure definition. Use when establishing a new regulated facility, formalising compliance across multiple systems, addressing a regulatory gap analysis, harmonising compliance after mergers or reorganisations, or preparing a site master file that references computerized systems.

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

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.

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