165 件 ・ 関連度順
概要と使いどころ
Geospatial risk modeling including catastrophe models, exposure analysis, and underwriting. Use when assessing spatial risk, building catastrophe models, analyzing exposure/hazard/vulnerability, or computing portfolio risk metrics.
日本語の概要は準備中です。原文の説明を表示しています。
Structures catastrophe risk assessment with model output interpretation and accumulation monitoring. Use when analyzing cat risk, interpreting cat model results, or managing cat exposure.
日本語の概要は準備中です。原文の説明を表示しています。
Astro is a modern web framework for building content-driven websites. It ships zero JavaScript by default, supports multiple UI frameworks (React, Vue, Svelte, Solid), and provides islands architecture for optimal performance.
日本語の概要は準備中です。原文の説明を表示しています。
Astro content-first framework - islands architecture, content collections, file-based routing, SSR/SSG hybrid rendering, View Transitions, server islands, multi-framework component support
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of an astronomer — calculating exposure time or signal-to-noise for a target, writing the feasibility math for a telescope-time proposal, reducing photometric or spectroscopic data, distinguishing a systematic error floor from statistical noise, or reviewing an observational result for calibration or upper-limit red flags.
日本語の概要は準備中です。原文の説明を表示しています。
Expert guidance across solar physics, planetary science, stellar evolution, cosmology, and observational techniques with 2025 mission data
日本語の概要は準備中です。原文の説明を表示しています。
Analyze catastrophe modeling systems for natural disaster exposure, PML estimation, and reinsurance optimization. Use when: 'assess cat model', 'evaluate disaster exposure', 'review PML calculations', 'audit reinsurance program', 'check exposure data quality', 'analyze hurricane/earthquake risk models', 'evaluate Oasis or RMS setup'.
日本語の概要は準備中です。原文の説明を表示しています。
Prospective failure imagination for a plan, decision, or running system. Operates in two modes — **plan mode** (a plan has not yet been committed to; imagine its catastrophic failure broadly) and **scenario mode** (a specific catastrophic scenario is posed against an existing system; investigate causes against the actual code and architecture). Spawns parallel pre-mortemers in isolation across three categories of lens: standard failure classes (technical, operational, estimation, scope, adoption, dependency, team, incentive, detection, reversibility, adversarial), 0-3 ad-hoc target-specific lenses the orchestrator names when warranted, and a first-principles lens that always runs to catch what the prescribed taxonomy misses. Synthesizes into a prioritized risk register with early-warning signals. Produces feedback only — no code, no tickets, no artifacts.
日本語の概要は準備中です。原文の説明を表示しています。
Expert in Astro framework with static generation and partial hydration patterns
日本語の概要は準備中です。原文の説明を表示しています。
Working with FITS astronomical data — headers, WCS, image calibration, and stacking with astropy.
日本語の概要は準備中です。原文の説明を表示しています。
塔罗牌占星：把「抽三张塔罗牌」与「西方占星本命盘」合为一次解读。 用户带着一个具体问题来 → 抽三张牌（可复现的 seed）→ 若愿意提供生日，则用脚本 确定性地排出星座与星盘 → 用黄金黎明的塔罗↔占星对应把两者接起来（牌落在黄道哪一旬， 你的哪颗行星正站在那里）→ 给出一张交叉对照表、对所问之事的审慎取向与可执行建议。 塔罗层：牌阵位置语义、牌与牌的组合叙事、元素尊贵、正逆位、直觉对话、治疗性解读。 占星层：本命盘、相位与宫位、必然尊贵、行运盘推运、比较盘/组合盘（合盘）、太阳弧推运。 当用户说：塔罗、塔罗牌、抽牌、抽三张牌、占卜、算一卦（西洋）、牌阵、正逆位、 星盘、本命盘、星座、上升星座、月亮星座、占星、行运、流年、合盘、比较盘、 太阳弧、推运、我该不该……、这段关系会怎样、我适不适合换工作 时使用。 English triggers: "tarot", "tarot reading", "draw three cards", "what do the cards say", "spread", "reversed card", "natal chart", "birth chart", "astrology", "rising sign", "transits", "synastry", "composite chart", "solar arc", "progressions", "should I take this job", "what does my chart say". 内置离线脚本：抽牌洗牌（可复现 seed）、本命盘（行星/四轴/宫位/相位/元素统计）、 必然尊贵、牌↔盘共鸣、元素数字统计、行运盘、比较盘+组合盘、太阳弧+次限推运。 边界：要**周公解梦**请用 `zhougong-dream-interpretation`；要**四柱八字**请用 `bazi`； 要**中式黄历择日/测吉凶**请用 `zhanshi-jixiong`。本技能只做西洋塔罗与西洋占星。 即使用户只是随口说「帮我抽张牌看看」「我最近水逆吗」，也应主动使用本技能。
日本語の概要は準備中です。原文の説明を表示しています。
Expert-level planetary science covering solar system formation, planetary interiors, atmospheres, surface processes, astrobiology, and planetary exploration missions.
日本語の概要は準備中です。原文の説明を表示しています。
Validate all JSON-LD scripts in Astro pages — check parsability, @context, @type, and Layout.astro auto-inject compatibility.
日本語の概要は準備中です。原文の説明を表示しています。
Build content-focused websites with Astro — zero JS by default, islands architecture, multi-framework components, and Markdown/MDX support.
日本語の概要は準備中です。原文の説明を表示しています。
Provides expert knowledge for building Astro 5+ sites with Islands Architecture, Content Collections, TypeScript, and performance-first rendering strategies.
日本語の概要は準備中です。原文の説明を表示しています。
Fetch personalized daily horoscope forecasts from zodiac-today.com API based on natal chart calculations. Use when a user wants: (1) daily guidance on what activities to pursue or avoid, (2) life planning help — best days for interviews, travel, romance, important decisions, (3) energy/focus/luck/romance forecasts to optimize their schedule, (4) lucky colors and numbers for the day, (5) future date analysis for planning events, trips, or milestones (paid tiers). Triggers: horoscope, zodiac, star sign forecast, daily guidance, lucky day, best day to, astrology advice, what should I do today, is today a good day for, plan my week astrology. Required env: ZODIAC_API_KEY (hsk_ API key), ZODIAC_PROFILE_ID (birth chart profile ID). Collects sensitive PII (email, birth date, birth city) for natal chart — requires user consent.
日本語の概要は準備中です。原文の説明を表示しています。
Discovers and evaluates scientific datasets, models, methodology posts, and Spaces through the Hugging Science catalog. Used when selecting scientific ML resources in biology, chemistry, genomics, materials, climate, physics, astronomy, medicine, mathematics, protein design, single-cell analysis, or PDE modeling, and when checking their actual datasets, Transformers, native-runtime, Inference Providers, or Gradio interfaces.
日本語の概要は準備中です。原文の説明を表示しています。
Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include "Vercel Sandbox browser", "microVM Chrome", "agent-browser in sandbox", "browser automation on Vercel", or any task requiring Chrome in a Vercel Sandbox.
日本語の概要は準備中です。原文の説明を表示しています。
Use for Vercel cost and performance optimization on deployed projects, especially Next.js, SvelteKit, Nuxt, and limited Astro apps. Collect Vercel metrics, usage, project config, and code scan results first; investigate only metric-backed candidates; produce ranked recommendations grounded in verified files and version-aware Vercel/framework docs. Trigger for Vercel bill reduction, slow or expensive routes, caching opportunities, Function Invocations, Build Minutes, Fast Data Transfer, Core Web Vitals, Bot Management, Fluid compute, or cost breakdown requests.
日本語の概要は準備中です。原文の説明を表示しています。
Configure a shared guard against catastrophic shell commands in local AI agents. Use when changing block patterns, adding an agent or machine, or investigating why a command was or wasn't blocked.
日本語の概要は準備中です。原文の説明を表示しています。
⚠️ CRITICAL USER EXPERIENCE-BASED SKILL - ALWAYS CONSULT BEFORE DATA PREPROCESSING ⚠️ Prevents catastrophic errors (88.9% error rate in V1.0 case study) through multi-level feature analysis, data leakage detection, and semantic validation. MANDATORY for: data preprocessing, feature engineering, standardization, normalization, interpolation, missing value handling, feature selection, or ANY data transformation task. Covers grouped time-series, cross-sectional, panel data. Detects: time travel leakage, causal inversion, ID misuse, semantic-numeric fallacies, distribution blindness. User's hard-won lessons from real project failures.
日本語の概要は準備中です。原文の説明を表示しています。
Migrates vibe-coded web applications to AWS. Handles the full workflow from analysis through migration to deployment, producing deployable AWS Blocks infrastructure code. Supports full-stack apps built with vibe-coding platforms (Lovable, Bolt.new, Replit) and frontend web applications and websites: React, Vue, Angular, Next.js, Nuxt, Astro, SvelteKit, Gatsby, Vite, Svelte, Solid, Docusaurus, and others (static sites, SPAs, and SSR frameworks with static export). Triggers on: launch with AWS, launch on AWS, deploy to AWS, migrate to AWS, host my app on AWS, move my app to AWS, transfer my app to AWS. Activates when the user wants to migrate a vibe-coded app or frontend web app to AWS, even if they don't say 'migrate' explicitly.
日本語の概要は準備中です。原文の説明を表示しています。
Use when doing ANY task involving Supabase. Triggers: Supabase products (Database, Auth, Edge Functions, Realtime, Storage, Vectors, Cron, Queues); client libraries and SSR integrations (supabase-js, @supabase/ssr) in Next.js, React, SvelteKit, Astro, Remix; auth issues (login, logout, sessions, JWT, cookies, getSession, getUser, getClaims, RLS); Supabase CLI or MCP server; schema changes, migrations, declarative schemas, security audits, Postgres extensions (pg_graphql, pg_cron, pg_vector); debugging and troubleshooting errors or unexpected behavior on Supabase projects (HTTP errors, Postgres errors, RLS surprises, permission denied, schema cache issues, timeouts, Edge Function crashes, Realtime drops, Storage failures) and reading or querying logs (Logs Explorer, ClickHouse).
日本語の概要は準備中です。原文の説明を表示しています。
Use when building or maintaining a personal LLM-powered knowledge base. Triggers: ingesting sources into a wiki, querying wiki knowledge, linting wiki quality, 'add to wiki', 'what do I know about', or any mention of 'LLM wiki' or 'Karpathy wiki'.
日本語の概要は準備中です。原文の説明を表示しています。