4,533 件 ・ 関連度順
概要と使いどころ
Implements standardized API error responses with proper status codes, logging, and user-friendly messages. Use when building production APIs, implementing error recovery patterns, or integrating error monitoring services.
日本語の概要は準備中です。原文の説明を表示しています。
HTTP API testing for TypeScript (Supertest) and Python (httpx, pytest). Test REST APIs, GraphQL, request/response validation, authentication, and error handling.
日本語の概要は準備中です。原文の説明を表示しています。
Use when operating, debugging, deploying, or monitoring a Telegram bot or Telegram-to-agent gateway. Triggers on "telegram bot down", "bot not responding", "debug bot", "check webhook", "polling vs webhook", "restart bot", "deploy bot", "bot logs", "agent gateway", "Telegram Bot API error", "send test message", "бот не отвечает", "проверь бота", "логи бота", "перезапусти бота". Covers health checks, logs, webhook/polling diagnostics, environment validation, safe restart/deploy checklists, Bot API smoke tests, forum topic delivery, privacy mode, gateway routing, and incident notes.
日本語の概要は準備中です。原文の説明を表示しています。
Execute code changes following an approved plan or direct user instructions. Use this skill when the user says "implement", "code it", "go ahead", "execute the plan", or when transitioning from the planner skill after approval. Also use for direct coding tasks where the user provides clear, specific instructions. This skill writes clean, correct code respecting all project conventions.
日本語の概要は準備中です。原文の説明を表示しています。
Refine a Stage 4 follow-up response using condensed prior discussion context, current follow-up question, and the user's draft.
日本語の概要は準備中です。原文の説明を表示しています。
Remove AI-generated writing patterns from rebuttal prose to make it sound natural, direct, and authentically human-authored. Use when a Stage 2 refined draft or Stage 4 follow-up response reads too formulaic, robotic, or "GPT-like". Supports academic English.
日本語の概要は準備中です。原文の説明を表示しています。
Verification guide for citations added during rebuttal writing. Use when Stage 2 responses introduce new references, when the Area Chair asks about a cited paper, or when any citation in the rebuttal might have been AI-generated. Prevents the serious credibility damage of fabricated references in reviewer-facing documents.
日本語の概要は準備中です。原文の説明を表示しています。
Base template for Stage1 reviewer-comment breakdown. Use when creating or extending conference-specific Stage1 skills (for example ICLR, ICML, NeurIPS, ACL) so shared extraction, splitting, and response-mapping logic stays consistent.
日本語の概要は準備中です。原文の説明を表示しています。
Condense rebuttal prose into fewer words without changing the original meaning. Use when a response block, paragraph, or selected passage is too long but all technical content, citations, and commitments must stay intact. Supports academic English.
日本語の概要は準備中です。原文の説明を表示しています。
Use when drafting or revising internal technical design docs, review notes, architecture writeups, or sharing posts in Chinese, especially when the tone should stay evidence-backed, calm, and suitable for peers or leaders rather than marketing or literary writing.
日本語の概要は準備中です。原文の説明を表示しています。
Create text-based wireframes at low, mid, and high fidelity with component inventories, interaction annotations, and responsive breakpoint specifications. Use when the user requests wireframing or provides relevant inputs for this workflow.
日本語の概要は準備中です。原文の説明を表示しています。
Build a preliminary, evidence-based EU AI Act readiness assessment across AI-system inventory, territorial scope, operator roles, prohibited-practice screening, risk classification, transparency, high-risk controls, general-purpose AI obligations, governance, and implementation milestones. Use when an organization needs to triage an AI use case, vendor, model, product, or portfolio for Regulation (EU) 2024/1689; prepare an AI inventory, gap register, implementation roadmap, or counsel briefing; assess provider, deployer, importer, distributor, product-manufacturer, authorised-representative, or GPAI-provider responsibilities; or re-check readiness after regulatory or product changes.
日本語の概要は準備中です。原文の説明を表示しています。
Design and build production-ready frontend interfaces with design systems, responsive layouts, accessible components, and dark mode support. Use when the user requests frontend design or provides relevant inputs for this workflow.
日本語の概要は準備中です。原文の説明を表示しています。
Create tailored sales proposals and RFP responses that address prospect needs, articulate solution value, and include pricing, timelines, and social proof. Use when the user requests proposal generation or provides relevant inputs for this workflow.
日本語の概要は準備中です。原文の説明を表示しています。
Classify, prioritize, and route incoming support tickets by extracting intent and entities, assigning severity, and generating initial responses. Use when the user requests ticket triage or provides relevant inputs for this workflow.
日本語の概要は準備中です。原文の説明を表示しています。
Draft a professional, audience-aware email or reply with calibrated tone and a clear call to action. Use when the user needs one message, response, follow-up, support note, or meeting request; use sales-email-sequences for a coordinated multi-touch outbound campaign.
日本語の概要は準備中です。原文の説明を表示しています。
Idiomatic Go - package and interface design, error wrapping, table-driven tests, generics, the modern standard library (slices/maps/cmp/errors.Join), current syntax, and logging discipline. Use when writing, reviewing, or refactoring any Go code, especially code drifting toward Java/Spring shapes (deep layer trees, generic repositories, heavy frameworks) - even if the user never says "idiomatic". Distilled from spf13/go-skills and adapted to this repo.
日本語の概要は準備中です。原文の説明を表示しています。
Standardize a 2D animation baseline image with `/img2mo-std xxx.png/pos`. Use when preparing a character, creature, prop, or weapon baseline before motion generation, especially if the source image is too large, tightly cropped, lacks transparent action margin, has a white background, or later walk/attack/idle frames show clipping, overlap, scale popping, or inconsistent character size.
日本語の概要は準備中です。原文の説明を表示しています。
Think and work like an expert Geomorphologist. Use when a task calls for Geomorphologist judgment. Reasons from coupled form, process, and time and from rates, thresholds, and lag times through field mapping, lidar/SfM DEM morphometry (chi profiles, Ksn in LSDTopoTools/Landlab), cosmogenic nuclide dating (CRONUS-Earth, OSL, U-Th), and landscape-evolution models, while treating equifinality, inheritance, DEM artifacts, and steady-state assumed over transient response as first-class failure modes.
日本語の概要は準備中です。原文の説明を表示しています。
Think and work like an expert Immunotherapy Scientist. Use when a task calls for Immunotherapy Scientist judgment. Reasons from antigen recognition and checkpoint circuits through CAR-T/bispecific design, ASTCT CRS/ICANS grading, flow cytometry release CQAs, iRECIST response assessment, COMPASS/TIDE biomarker modeling, and JACIE/FACT IEC accreditation while treating antigen escape, pseudoprogression, tonic signaling, and step-up CRS as first-class failure modes.
日本語の概要は準備中です。原文の説明を表示しています。
Think and work like an expert Embedded Systems Engineer. Use when a task calls for Embedded Systems Engineer judgment. Reasons from hardware timing, interrupt latency, memory maps, and deterministic WCET resource bounds through DWT CYCCNT and Saleae logic-analyzer timing proofs, SWD/JTAG (J-Link/OpenOCD) with CFSR/HFSR/BFAR fault decode, FreeRTOS/Zephyr respecting configMAX_SYSCALL_INTERRUPT_PRIORITY, MISRA C:2012 and ISO 26262 ASIL discipline, Nordic PPK2 power profiling, and MCUboot signed OTA while treating priority inversion, Cortex-M7 uncached-DMA D-cache incoherence, CAN bus-off, I2C NACK storms, and brownout-during-flash-write NVS corruption as first-class failure modes.
日本語の概要は準備中です。原文の説明を表示しています。
Think and work like an expert Comparative Physiologist. Use when a task calls for Comparative Physiologist judgment. Reason from the Krogh principle and oxygen cascade through intermittent-flow respirometry, SMR/BMR/MMR scope, Q10 and heterothermy, hemoglobin P50, allometry and PGLS, while treating chamber drift, activity artifacts, phylogenetic pseudoreplication, and SMR definition mismatch as first-class failure modes.
日本語の概要は準備中です。原文の説明を表示しています。
Think and work like an expert Crop Scientist. Use when a task calls for Crop Scientist judgment. Reasons from genotype-by-environment-by-management interaction, yield-component partitioning, and phenology-gated critical periods through MET stability analysis (AMMI, Finlay-Wilkinson, GGE biplots), mixed models (ASReml-R, lme4), N-response curves (quadratic-plateau, MRTN), and crop models (APSIM, DSSAT) while treating pseudo-replicated subsamples, single-site yield champions, uncorrected harvest moisture, and weather-during-anthesis confounding as first-class failure modes.
日本語の概要は準備中です。原文の説明を表示しています。
Think and work like an expert Clinical Pharmacologist. Use when a task calls for Clinical Pharmacologist judgment. Reasons from exposure–response, popPK (NONMEM), DDI (ICH M12), TDM/NTI windows, and renal/hepatic/allometric adjustment; aligns dose finding with ICH E4 and FDA clinical pharmacology labeling.
日本語の概要は準備中です。原文の説明を表示しています。