400 件 ・ 関連度順
概要と使いどころ
Unify metrics, logs, and traces for cohesive debugging. Implement exemplars for log-to-trace linking, build unified dashboards using RED/USE methods, and enable rapid root cause analysis across observability signals. Use when investigating complex incidents spanning multiple systems, reducing mean time to resolution, implementing distributed tracing, or moving from siloed tools to a unified observability platform.
日本語の概要は準備中です。原文の説明を表示しています。
Remove dead code, unused imports, fix lint warnings, and normalize formatting across a codebase without changing business logic or architecture. Use when lint warnings have piled up during rapid development, unused imports and variables clutter files, dead code paths were never removed, formatting is inconsistent, or static analysis tools report fixable hygiene issues.
日本語の概要は準備中です。原文の説明を表示しています。
Appraise gemstone value using the four Cs (color, clarity, cut, carat), origin assessment, treatment detection, and market factor analysis. Advisory educational guidance only — not a certified appraisal. Use when understanding factors that determine a gemstone's value, pre-screening stones before a professional appraisal, evaluating whether a seller's asking price is reasonable, learning gemstone grading methodology, or understanding how treatment status affects value.
日本語の概要は準備中です。原文の説明を表示しています。
Fix docker exec hanging when starting background processes (servers, daemons) inside containers. Use when: (1) docker exec never returns despite using & or nohup, (2) background server started in container causes docker exec to hang indefinitely, (3) env_startup_command in SWE-bench or similar frameworks times out, (4) setsid/disown needed for proper process detachment in Docker. Root cause: docker exec tracks ALL processes in the exec session, not just the top-level PID.
日本語の概要は準備中です。原文の説明を表示しています。
Analiza textos aplicando pensamiento crítico — el marco de los 8 elementos del pensamiento y los estándares intelectuales universales de Richard Paul y Linda Elder — y detecta las falacias lógicas graves presentes. Úsala siempre que el usuario comparta un texto (pegado o en un archivo) y pida analizarlo críticamente, detectar falacias, evaluar argumentos, identificar sesgos, o preguntas como "¿qué problemas tiene este argumento?", "¿es sólido este razonamiento?", "analiza esto", "dame una crítica". También actívala cuando el usuario comparta un artículo de opinión, un post, un discurso, un ensayo o cualquier texto argumentativo y quiera evaluar su calidad argumentativa.
日本語の概要は準備中です。原文の説明を表示しています。
Use when handling external API rate limits (e.g., OpenAI 429s, HubSpot or Stripe rate limits), preventing duplicate work from rapid event bursts (debouncing user actions), spreading load over time, ensuring per-tenant fairness, processing events in batches, limiting concurrent runs of the same operation, or assigning priority to important runs. Covers Inngest flow control: concurrency limits with keys, throttling, rate limiting, debounce, priority, singleton, and event batching.
日本語の概要は準備中です。原文の説明を表示しています。
Meta-agent for creating new custom agents, skills, and MCP integrations. Expert in agent design, MCP development, skill architecture, and rapid prototyping. Activate on 'create agent', 'new skill', 'MCP server', 'custom tool', 'agent design'. NOT for using existing agents (invoke them directly), general coding (use language-specific skills), or infrastructure setup (use deployment-engineer).
日本語の概要は準備中です。原文の説明を表示しています。
Ultra-fast proof-of-concept and MVP specialist. Use this agent when you need to validate an idea quickly working prototype before the meeting's over. Pragmatic, speed-focused, validation-oriented. Ships in days, not weeks.
日本語の概要は準備中です。原文の説明を表示しています。
EXPERIMENT MODE: Timeboxed, throwaway code for rapid validation. Bypasses TDD requirements. Code must be quarantined and cannot be merged to main.
日本語の概要は準備中です。原文の説明を表示しています。
Monitors dark web forums, marketplaces, paste sites, and ransomware leak sites for mentions of organizational assets, leaked credentials, threatened attacks, and threat actor communications to provide early warning intelligence. Use when establishing dark web monitoring coverage, investigating specific data breach claims, or enriching incident investigations with dark web context. Activates for requests involving dark web OSINT, leak site monitoring, credential exposure, Recorded Future dark web, or Tor hidden service intelligence.
日本語の概要は準備中です。原文の説明を表示しています。
houtu-dependencies enterprise-grade Spring Cloud microservice foundational framework complete usage guide. GroupId is io.github.lujiafa, covering unified response, exception handling, parameter parsing, session authentication, permission control, signature verification, anti-replay, distributed lock, rate limiting, database field encryption, config decryption, access logging, canary routing, weighted load balancing, Feign enhancement, Sentinel circuit breaking, service discovery, Swagger documentation, crypto utilities, HTTP client, monitoring metrics, and other enterprise-grade capabilities. When the project build file (pom.xml or build.gradle/build.gradle.kts) contains io.github.lujiafa or houtu-related dependencies, or when the user mentions houtu or houtu-dependencies, this Skill must be read and code must be generated strictly following framework conventions. Even if the user is simply doing regular Spring Boot development (e.g., writing Controller, Service, Feign), as long as the project includes houtu, the houtu approach must be used instead of native Spring. When the user explicitly wants to use the houtu framework and the project has not yet included it, proactively add the BOM and required Starters; when the project already includes it, proactively identify and import required module dependencies based on business scenarios during coding, naturally integrating framework capabilities to enhance business services based on business semantics, rather than waiting for the user to specify each one.
日本語の概要は準備中です。原文の説明を表示しています。
"Apply the Dynamic Capabilities framework (Teece et al., 1997) — sensing, seizing, and transforming — to analyze how firms adapt, integrate, and reconfigure competences in rapidly changing environments. Use this skill when the user needs to explain why some firms sustain advantage while others decline, evaluate organizational agility, distinguish operational from strategic capabilities, or when they ask 'how do we stay competitive as the market shifts', 'why did this firm fail to adapt', or 'what capabilities do we need to build'.".
日本語の概要は準備中です。原文の説明を表示しています。
"Apply the Born Global framework to analyze firms that internationalize rapidly from inception under resource constraints. Use this skill when the user needs to evaluate whether a startup or SME can pursue early internationalization, identify the capabilities enabling born globals, or design a resource-constrained international market entry strategy.".
日本語の概要は準備中です。原文の説明を表示しています。
Generate contextual briefings for legal work — daily summary, topic research, or incident response. Use when starting your day and need a scan of legal-relevant items across email, calendar, and contracts, when researching a specific legal question across internal sources, or when a developing situation (data breach, litigation threat, regulatory inquiry) needs rapid context.
日本語の概要は準備中です。原文の説明を表示しています。
"Model viral spread dynamics using SIR/SIS/SEIR compartmental models. Use this skill when the user needs to predict content spread patterns, estimate viral thresholds, or model information cascades in social networks — even if they say 'will this go viral', 'epidemic model for content', or 'spread prediction'.".
日本語の概要は準備中です。原文の説明を表示しています。
"Implement a web crawler pipeline covering URL discovery, fetching, parsing, and storage. Use this skill when the user needs to build a site crawler, audit website structure, or collect web data systematically — even if they say 'scrape a website', 'crawl all pages', or 'site audit spider'.".
日本語の概要は準備中です。原文の説明を表示しています。
Rapidly map a new codebase, identify the runtime model, risk zones, and first high-value next steps.
日本語の概要は準備中です。原文の説明を表示しています。
Draft crisis communication packages including holding statements, stakeholder updates, Q&A documents, and internal briefs. Follows ICS (Incident Command System) communication principles. Use during PR crises, data breaches, product recalls, or any event requiring rapid coordinated messaging.
日本語の概要は準備中です。原文の説明を表示しています。
SQL discipline for querying Pulp Perfetto traces (.pftrace) with trace_processor — idempotent CREATE OR REPLACE PERFETTO views, GLOB not LIKE, dur = -1 incomplete-slice handling, EXTRACT_ARG for span args, joining on stable utid/upid, SPAN_JOIN PARTITIONED, and the draft→validate→execute loop. Ships Pulp's CPU/UI trace stdlib plus closed GPU startup, health, and probe views. TRIGGER when writing or debugging SQL over a .pftrace, when `pulp trace query` returns wrong/empty rows, or when the trace-analysis skill needs a query primitive.
日本語の概要は準備中です。原文の説明を表示しています。
Rapid prototyping workflow. Skips normal standards to quickly validate a game concept or mechanic. Produces throwaway code and a structured prototype report.
日本語の概要は準備中です。原文の説明を表示しています。
Public relations, corporate communications, and analyst relations for B2B SaaS. Use this skill for earned media and press strategy, announcements and press releases, executive and crisis communications, media relationships and briefings, and the Gartner/Forrester/IDC analyst program including Magic Quadrant and Wave evaluation submissions. Also triggers on: PR, public relations, press release, earned media, media relations, journalist, embargo, announcement, crisis comms, corporate communications, analyst relations, AR, Gartner, Forrester, IDC, Magic Quadrant, Forrester Wave, analyst briefing, inquiry, newsjacking, rapid response, should we comment on this news story, expert commentary, reactive comment, source request, Qwoted, is this newsworthy.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a cytotechnologist — screening a gynecologic (Pap test) slide and applying Bethesda System criteria, assessing non-gynecologic specimen adequacy (FNA rapid on-site evaluation, body fluid, brushing) against the relevant reporting system, deciding whether a finding can be signed out independently or must be referred to a pathologist, or auditing screening quality metrics (ASC:SIL ratio, rescreen concordance, workload compliance). A reasoning aid, not a substitute for a certified cytotechnologist or pathologist signing out an actual case.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Control and Valve Installer/Repairer — sizing a control valve's Cv against actual process flow, diagnosing a limit-cycling control loop as valve stiction versus a bad PID tune, running an FCI 70-2 seat-leakage or API 598 pressure test, calibrating a positioner/actuator after a rebuild, or scheduling PHMSA-mandated regulator/relief-valve testing on a gas distribution system.
日本語の概要は準備中です。原文の説明を表示しています。
Inspect the effective Spec Kit artifact inventory and composition stacks via `specify artifact`. USE FOR: listing commands/templates/scripts/hooks, explaining which preset or extension layer supplies an artifact, inspecting resolution precedence and hidden layers, checking hook registration, or resolving a stack lookupId to its validated contribution. DO NOT USE FOR: installing or changing presets/extensions (use speckit-preset or speckit-extension), resolving only a preset-managed filename (use speckit-preset), or running an artifact.
日本語の概要は準備中です。原文の説明を表示しています。