「analyze」の検索結果

Expert in 2000s-era music visualization (Milkdrop, AVS, Geiss) and modern WebGL implementations. Specializes in Butterchurn integration, Web Audio API AnalyserNode FFT data, GLSL shaders for audio-reactive visuals, and psychedelic generative art. Activate on "Milkdrop", "music visualization", "WebGL visualizer", "Butterchurn", "audio reactive", "FFT visualization", "spectrum analyzer". NOT for simple bar charts/waveforms (use basic canvas), video editing, or non-audio visuals.

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

Analyzes ticket complexity and dependencies against the codebase before sprint planning. NOT for writing plans (mk:plan-creator); NOT for scope review (mk:plan-ceo-review).

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

Process images/video/audio/PDFs via Gemini API; generate images/video/speech/music; convert docs to Markdown. Multi-provider fallback. Use for analyze/transcribe/generate/convert on media files.

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

Read-first Figma gateway via Figma MCP: analyze designs, implement 1-3 screens, extract tokens, produce Evidence Packet. Advanced ops gated on explicit intent. Use for 'figma', 'design tokens'.

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

Ticket/PRD intake: product-area classification, completeness scoring, RCA, technical assessment. Works with Jira, Linear, GitHub, or manual paste. Use to analyze or triage a ticket.

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

Weekly-cadence engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware: breaks down per-person contributions with praise and growth areas. Use when asked to "weekly retro", "what did we ship", or "engineering retrospective". Proactively suggest at the end of a work week or sprint. NOT for per-session or per-task reflection (see mk:memory / Phase 6 Reflect).

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

Evaluate Jira ticket complexity + inconsistencies via the jira-evaluator agent. Read-only. Triggers: 'evaluate KEY', 'analyze ticket complexity for KEY', 'check ticket quality for KEY'. NOT for estimation (mk:jira-estimator); NOT for full RCA (mk:jira-analyst).

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

Process images, video, audio, PDFs with Gemini API. Generate images (Nano Banana 2), videos (Veo 3), speech (MiniMax TTS), music (MiniMax). Convert documents to Markdown. Multi-provider fallback (Gemini → MiniMax → OpenRouter). Activate when task references media files, asks to analyze/describe/transcribe/extract/generate/convert, or involves non-text binary files.

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

Analyzes ticket complexity and maps dependencies against an existing codebase before sprint planning. Triggers on 'how complex is this ticket', 'what should we work on first', 'can we fit this in the sprint', 'tech review before planning', 'plan the sprint'. NOT for writing implementation plans (see mk:plan-creator); NOT for scope/ambition review (see mk:plan-ceo-review).

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

Use when refining a draft user prompt before sending it to a coding agent. Decomposes goal/context/constraints/acceptance/output-format, detects ambiguity and model-coupled framing, then emits a model-agnostic rewrite. Supports --analyze, --score, and --deep. NOT for prompts from scratch (mk:brainstorming), plans/reviews (mk:elicit), implementation plans (mk:plan-creator), or general codebase scouting (mk:scout).

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

Full Jira ticket context analysis via the jira-analyst agent — including media (attached images / PDFs / screenshots) and linked issues. Produces structured findings suitable for posting back as a Jira comment. Read-only. Triggers: 'analyze KEY', 'rca for KEY', 'describe KEY with media'. NOT for complexity scoring (mk:jira-evaluator); NOT for story-point estimation (mk:jira-estimator).

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

Read-first Figma gateway via Figma MCP: analyze designs, implement Figma-to-code for 1–3 screens, extract design tokens, produce a Figma Evidence Packet for planning handoff, screenshot fallback. Advanced operations (Code Connect, canvas writes, design-system/library patterns) are gated references loaded only on explicit intent. Triggers: 'figma', 'design link', 'implement this design', 'design tokens', 'produce a Figma Evidence Packet'.

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

Ticket/PRD intake: product area classification, completeness scoring, RCA, technical assessment. Works with Jira (via mk:jira-issue / jira-as), Linear (via MCP), GitHub (via gh CLI), or manual paste. Triggers: 'analyze ticket', 'intake PRD', 'triage issue', 'classify ticket', 'check ticket'.

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

Deep spec analysis on a Confluence page. Reads page (+ children) via the confluence-as wrapper, produces a structured Spec Research Report with requirements, acceptance criteria, gaps, ambiguities, and suggested user stories for human review. Read-only — does NOT create Jira tickets. Triggers: 'analyze spec for PAGE-ID', 'extract requirements from confluence page', 'spec research on URL'. NOT for raw page CRUD (mk:confluence-page); NOT for ticket complexity scoring (mk:planning-engine).

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

Manage Model Context Protocol (MCP) servers - discover, analyze, and execute tools/prompts/resources from configured MCP servers. Use when working with MCP integrations, need to discover available MCP capabilities, filter MCP tools for specific tasks, execute MCP tools programmatically, access MCP prompts/resources, or implement MCP client functionality. Supports intelligent tool selection, multi-server management, and context-efficient capability discovery.

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

Analyze task trajectories to propose reusable SKILL.md candidates from successful patterns

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

Analyze external URL to evaluate fit with oh-my-customcode project and auto-create GitHub issue with verdict

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

Analyze GitHub issues against current codebase and perform automated triage with priority assessment

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

Analyze release workflow findings and recommend follow-up actions — execute immediately or register as issues

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

Analyze project and auto-configure agents, skills, rules, and guides

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

Analyze a natural language idea against the project codebase and return structured issue specs

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

On explicit /homework invocation, analyze the current and linked previous sessions, extract mistakes (찐빠), and report them via omcustom-feedback with a confirmation gate. Auto-activation on session cleanup/session-end signals is OPT-IN (default OFF) — requires an explicit project/user directive. Use when explicitly auditing recent work for harness gaps.

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

Reddit automation skill collection. Supports authentication, content publishing, search & discovery, social interactions, and compound operations. Triggered when a user asks to operate Reddit (post, search, comment, login, analyze, upvote, save).

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

Analyzes time-series and longitudinal RNA-seq for differential expression and trajectory structure. Covers DESeq2 LRT with reduced models, time as factor vs continuous vs natural splines, maSigPro (Nueda 2014 for RNA-seq), ImpulseDE2 with explicit impulse-model failure modes, DREAM for repeated measures via linear mixed models, pseudoreplication avoidance, conditional vs marginal modeling, and trajectory clustering with DPGP, Mfuzz (with Schwämmle 2010 fuzzifier estimation), and splines+k-means. Use when modeling time-course or longitudinal expression, choosing factor vs spline, handling repeated measures from the same subject, avoiding pseudoreplication, clustering temporal trajectories, or selecting between dedicated time-course tools and pairwise+LRT.

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