905 件 ・ 関連度順
概要と使いどころ
Subscribe to live Hyperliquid data over WebSocket from the desk computer - mids, order book, trades, candles, best bid/offer, and per-account fills, order updates and events - with raw JSON, Python SDK and TypeScript examples, plus how to run a supervised watch that logs to a file and alerts. Read-only. Use for monitoring, fill notifications and any watch that polling would make expensive.
日本語の概要は準備中です。原文の説明を表示しています。
Prepare the desk computer to work with Hyperliquid - install the SDKs, pick testnet or mainnet, verify connectivity, and (only when the user asks) provision a trade-only API wallet through the secure secret store and verify it is approved. Use during desk setup, when moving between research, testnet and mainnet levels, when a key is rotated, or when any Hyperliquid call fails with an environment problem.
日本語の概要は準備中です。原文の説明を表示しています。
Place, cancel and modify Hyperliquid orders correctly from the desk computer - limit and IOC (market-style) orders, take-profit and stop-loss trigger orders with grouping, client order ids, reduce-only, batch actions, price and size rounding, and how to read every response status. Write path - Execution Trader only, on an approved ticket. Use for any order action and for reconciling by cloid.
日本語の概要は準備中です。原文の説明を表示しています。
Read live Hyperliquid market data from the desk computer with curl or the Python SDK - mid, mark and oracle prices, order book depth, funding (current, predicted, historical), open interest, volume, candles, perp and spot metadata, margin tiers, and how to save datasets for the strategy lab. Read-only, no key. Use for any market brief, depth read, funding question or data pull.
日本語の概要は準備中です。原文の説明を表示しています。
Manage Hyperliquid perp positions and margin from the desk computer - read positions and margin, set leverage and cross/isolated mode, add isolated margin, understand margin tiers and liquidation price, close a position with a reduce-only IOC, and clean up orphaned orders. Write actions are Execution Trader only, on an approved ticket. Use for leverage changes, closes, protection checks and margin questions.
日本語の概要は準備中です。原文の説明を表示しています。
Read a Hyperliquid account from the desk computer - positions and margin, spot balances, open orders including trigger details, fills, funding paid, ledger updates, order status by oid or cloid, historical orders, portfolio history, fee tier and rate-limit budget - with curl and Python SDK examples. Read-only, needs only the account address. Use for sizing inputs, book checks, reconciliation and reviews.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user asks to "write a LinkedIn post", "draft a post about", "help me post on LinkedIn", "create LinkedIn content", or when Genesis proactively generates post ideas during surplus compute. Also triggered by content calendar execution or when the user shares a topic they want to write about.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user asks to "plan my LinkedIn content", "create a content calendar", "what should I post about this week", "plan my posting schedule", or when Genesis proactively suggests a weekly content plan during surplus compute. Also triggered by "I need post ideas" or "I don't know what to write about".
日本語の概要は準備中です。原文の説明を表示しています。
Read this skill before the first step that uses the built-in browser, the browser pane inside the Claude desktop app (also called the in-app browser, the browser pane, Claude's browser, or "your own browser"), whose tools are named mcp__Claude_Browser__* when the session runs in the desktop app and mcp__remote-devices__Claude_Browser__* when a cloud session is linked to the person's computer; before those tools are turned on there may be a single enable__mcp__remote-devices__Claude_Browser tool instead. It covers the pane's persistent sign-ins, tabs and preview_start, reading pages as text, site approvals, what the pane cannot open, and what to do when it cannot be reached. It is not for Claude in Chrome (mcp__claude-in-chrome__* tools), which has its own skill, and it does not decide which browser to use.
日本語の概要は準備中です。原文の説明を表示しています。
Submit expense reimbursements through Benepass (app.getbenepass.com). For users whose employer uses Benepass as their benefits platform. Handles login, benefit selection, form filling, receipt upload, and submission. Requires browser/computer-use capabilities.
日本語の概要は準備中です。原文の説明を表示しています。
Computes availability for redundant and series designs, failover, SPOFs, fault trees, FMEA, Weibull, and error budgets. Use when asking what uptime a design gives.
日本語の概要は準備中です。原文の説明を表示しています。
Sizes models and token budgets using Kaplan/Chinchilla scaling laws. Use when reasoning about compute-optimal N and D, tokens-per-parameter ratios, or over-training tradeoffs.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze a warehouse for stale, unused, or redundant tables via the analyze_storage_costs MCP tool. Classifies waste patterns and table categories, computes safety tiers, and handles category drill-downs and lineage follow-ups.
日本語の概要は準備中です。原文の説明を表示しています。
Overview of the Neon platform for apps and agents, spanning Postgres, Auth, Data API, and the new services: Object Storage, Compute Functions, and AI Gateway. Use whenever "Neon" is mentioned for an overview of how to work with Neon and how to get started. Otherwise, the individual capabilities are the triggers: "object storage" or "S3-compatible storage", "serverless functions", "background jobs", or "run code near my database", "AI gateway", "LLM proxy", "model routing", or "call an LLM" → AI Gateway; "database", "Postgres", or "authentication" → Postgres and Auth.
日本語の概要は準備中です。原文の説明を表示しています。
Use Pierre Computer Company's `@pierre/trees` (path-first file tree) and `@pierre/diffs` (shiki-based code/diff renderer) in Kolu. Pierre ships Preact/vanilla cores with optional React wrappers — Kolu consumes the vanilla classes and wraps them in thin SolidJS components. Trigger when: wiring up a file tree, rendering unified diffs or syntax-highlighted files, replacing `@git-diff-view`, or any mention of `@pierre/trees` / `@pierre/diffs` / "pierre library".
日本語の概要は準備中です。原文の説明を表示しています。
Create a Datagrok Compute2 workflow (pipeline configuration with steps, links, and actions)
日本語の概要は準備中です。原文の説明を表示しています。
Google Cloud Platform CLI - manage GCP resources. Use when working with Compute Engine, Cloud Run, GKE, Cloud Functions, Storage, BigQuery, or other GCP services.
日本語の概要は準備中です。原文の説明を表示しています。
Beads Viewer - Graph-aware triage engine for Beads projects. Computes PageRank, betweenness, critical path, and cycles. Use --robot-* flags for AI agents.
日本語の概要は準備中です。原文の説明を表示しています。
Understanding how digital systems actually work -- hardware, operating systems, networks, and information representation -- at a depth sufficient to reason about them rather than just use them. Covers CPU/RAM/storage/GPU roles, what an OS does, how packets travel the internet, and how computers represent numbers, text, images, and sound as binary. Use when a learner needs to build a mental model of computing rather than memorize menu paths.
日本語の概要は準備中です。原文の説明を表示しています。
Before dispatching a multi-agent team, run a spectral diagnostic on the proposed communication graph and emit a (ρ, Δ, κ) coordination signature plus a pass/fail verdict against per-task-class thresholds. Builds the row-stochastic operator P from the team graph, computes the successor representation M = (I − γP)⁻¹, and ranks the topology for robustness (κ, condition number), consensus (Δ, spectral gap), and drift (ρ, spectral radius). Per Parks & Alharthi (arxiv 2605.11453), rank order on (κ, Δ, ρ) predicts coordination quality pre-execution with rank correlations of 1.0 / 0.5 / −1.0. Triggers: "dispatch the team", "team topology check", "before running the agents", "is this team configuration OK", "team pre-flight".
日本語の概要は準備中です。原文の説明を表示しています。
OpenStack capacity planning operations skill for resource planning, quota management, and scaling decisions. Covers compute capacity (allocation ratios, vCPU/RAM utilization, host aggregates, availability zones), storage capacity (Cinder pool sizing, thin provisioning, Glance storage, Swift rings), network capacity (floating IP pools, port quotas, subnet sizing), project quota management (templates for small/medium/large profiles), flavor sizing strategy, utilization analysis with placement service, growth forecasting from historical metrics, and right-sizing recommendations for underutilized resources.
日本語の概要は準備中です。原文の説明を表示しています。
Calculus and continuous transformation — derivatives, integrals, ODEs, Taylor series, and optimization. Computes rates of change, accumulates quantities over intervals, solves differential equations, and classifies critical points. Use when computing derivatives or integrals, solving ordinary differential equations, performing Taylor series approximations, finding critical points, or analyzing continuous change and motion.
日本語の概要は準備中です。原文の説明を表示しています。
Kolla-Ansible day-2 operations skill for post-deployment infrastructure lifecycle management. Covers service reconfiguration (globals.yml changes, config overrides, prechecks, targeted reconfigure with --tags), minor and major OpenStack upgrades (image pull, upgrade procedure, rollback), container management (restart, logs, health inspection), maintenance mode (compute disable, instance drain, host maintenance), password rotation, certificate renewal, and rolling updates. This skill is for operations after initial deployment -- the kolla-ansible deployment skill covers initial bootstrap and deploy.
日本語の概要は準備中です。原文の説明を表示しています。
Run a custom computer-vision prompt against an image with a local vision LLM. Wraps kuzco's tool_llm_image_custom() ellmer tool. Use when none of the specialized kuzco image skills (classification, OCR, recognition, sentiment, alt text) fit the task.
日本語の概要は準備中です。原文の説明を表示しています。