Results for “analyze”

Use when you need to analyze Java profiling data collected during the detection phase — including interpreting flamegraphs, memory allocation patterns, CPU hotspots, threading issues, systematic problem categorization, evidence documentation with profiling-problem-analysis and profiling-solutions markdown files, or prioritizing fixes using Impact/Effort scoring. This should trigger for requests such as Analyze JFR profile; Analyze the profile; Analyze the performance; Analyze the memory; Analyze the threading; Analyze GC logs from profiling; Prioritize Java profiling bottlenecks by impact. Part of Plinth Toolkit

The English summary is being prepared. Showing the original description.

Extract YouTube transcripts and analyze messaging, structure, intended viewers, emotional appeal, credibility, and calls to action—requests for viewers to act. Analyze one video or compare several keyword-selected videos to identify recurring strategies and content gaps.

• Compare competitors' video content strategies
• Research intended viewers and their problems
• Identify topics competitors have not covered

Fix stale Haskell analyzer binaries silently being used by the orchestrator even after a successful rebuild. Use when: (1) modified `packages/js-analyzer/` or other Haskell analyzer source, ran `scripts/build-native.sh ... cabal install`, but a subsequent `grafema analyze` shows old behavior (missing new edges, no new node types, etc.), (2) `~/.cabal/bin/grafema-analyzer` has fresh timestamp but `grafema analyze` produces output as if the change didn't happen, (3) a test verifying new analyzer output passes locally in unit tests but fails in end-to-end runs that go through the orchestrator. Root cause: the Rust orchestrator's `resolve_binary` checks `~/.grafema/bin/<name>` BEFORE `~/.cabal/bin/<name>`, so any stale copy that was once installed there (possibly months ago) shadows the fresh `cabal install` output.

The English summary is being prepared. Showing the original description.

Assess code change risk, locate complex areas, and inspect file statistics with ruflo analysis commands. The skill also guides running and extending ruflo’s regression guards, automated checks that help catch previously fixed problems.

• Assessing risk before reviewing a code change
• Finding complex code that needs attention
• Running ruflo regression guards locally

Evaluate 3D point clouds and movement trajectories against reference data with CloudAnalyzer. Prepare inputs, measure differences, apply quality thresholds, inspect results visually, and track baseline history for mapping, localization, and perception workflows.

• Compare a generated point cloud with reference data
• Measure errors in estimated movement trajectories
• Check ground segmentation against quality thresholds

Use the open-source free `Meziantou.Analyzer` package for design, usage, security, performance, and style rules in .NET. Use when a repo wants broader analyzer coverage with a single NuGet package. USE FOR: the repo uses or wants Meziantou.Analyzer; the team wants one analyzer pack that covers design, usage, security, performance, and style. DO NOT USE FOR: repos that already enforce an overlapping analyzer baseline and do not want extra diagnostics; formatting-only work. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.

The English summary is being prepared. Showing the original description.

Audit Google Cloud access permissions to find overly broad roles, unnecessary service account keys, public access, and impersonation risks. Use gcloud CLI, Policy Analyzer, and IAM Recommender to document findings and plan more limited permissions.

• Reviewing access permissions across a GCP organization
• Replacing broad Owner and Editor roles with narrower roles
• Auditing unused service accounts and user-managed keys

Use the open-source free `StyleCop.Analyzers` package for naming, layout, documentation, and style rules in .NET projects. Use when a repo wants stricter style conventions than the SDK analyzers alone provide. USE FOR: the repo wants StyleCop.Analyzers; naming, layout, or documentation style needs stronger enforcement; the team needs stylecop.json guidance. DO NOT USE FOR: repos that intentionally rely only on SDK analyzers; repos where StyleCop overlaps too heavily with an existing style package and no. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.

The English summary is being prepared. Showing the original description.

Use a repo-root `.editorconfig` to configure free .NET analyzer and style rules. Use when a .NET repo needs rule severity, code-style options, section layout, or analyzer ownership made explicit. USE FOR: the repo needs a root .editorconfig; analyzer severity and style ownership are unclear; the team wants one source of truth for rule configuration. DO NOT USE FOR: choosing analyzers with no config change; formatting-only execution with no config ownership question. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.

The English summary is being prepared. Showing the original description.

Analyze slow development workflows and agent coordination using execution times, resource use, dependencies, and communication patterns. Identify bottlenecks, prioritize causes, and build an improvement plan covering parallel work, caching, or resource allocation.

• Investigate slow test execution
• Find unnecessary waits in task sequences
• Reduce communication delays between agents

Review a codebase for readability, performance, security, and architectural issues. The skill organizes findings into actionable recommendations, helping teams identify refactoring work, dependency risks, and areas that need better tests.

• Reviewing code quality before a pull request is merged
• Investigating performance and security issues
• Prioritizing refactoring and dependency updates

Analyze networks of people, web pages, or systems using PageRank, a method that scores importance from connections. Identify influential nodes and communities, generate personalized recommendations, and examine communication bottlenecks to guide network improvements.

• Finding influential users and communities on social networks
• Analyzing links and page importance on a website
• Generating recommendations based on user preferences

Analyze NTFS file records and change journals to investigate deleted files on Windows disks. Recover surviving metadata and content where possible, reconstruct file activity timelines, and compare timestamps for signs of deliberate manipulation.

• Recovering names and paths of deleted files
• Assessing whether deleted file content can be recovered
• Reconstructing file creation, modification, and deletion timelines

Run nf-core workflows on local sequencing files or public GEO/SRA datasets to analyze gene expression, genetic variants, or chromatin accessibility. The skill guides environment checks, sample table preparation, workflow configuration, execution, and output verification.

• Analyze gene expression from RNA-seq data
• Identify genetic variants in WGS/WES data
• Analyze chromatin accessibility from ATAC-seq data

Analyze saved NemoClaw CI timings to rank consistently slow command-line tests and compare base-image publication with reuse. Read-only analyzers report execution times, runner queues, and sample coverage as bounded JSON output.

• Finding consistently slow command-line tests
• Ranking test files by execution time
• Comparing base-image publication with reuse

Apply over 240 reusable prompt templates to summarize content, extract insights, improve writing, review code, or analyze security threats. It reads each template directly and returns results in the format defined for that task.

• Extract ideas and insights from an article
• Create a concise five-sentence summary
• Improve writing or review code with a selected template

Analyze short web fiction to understand its central premise, emotional progression, twists, characters, and writing techniques. Produce an evidence-based report and supporting files that can inform a new story without copying distinctive elements.

• Studying the structure of short web fiction
• Tracing emotional buildup and plot twists
• Examining character roles and opening or ending techniques

Analyze an Amazon competitor by ASIN, its product identifier, using listing text, keywords, images, and reviews. Identify competitor strengths and unmet buyer needs, then turn those findings into positioning and product opportunities for your brand.

• Analyze a competitor's titles and selling points
• Review keyword placement across a listing
• Find unmet buyer needs in reviews

Score one blog post (or a folder of posts) on a 5-category 100-point scale covering content quality, SEO, E-E-A-T, technical elements, and AI citation readiness. Runs the deterministic analyzer first, then adds judgment and prioritized Critical/High/Medium/Low fixes. Advisory style diagnostics never infer authorship or affect the score. Exports markdown, JSON or table; works with MDX, markdown, HTML or a URL. Use when the user asks to analyze, score, rate or check the quality of specific posts ("analyze blog", "blog score", "check blog quality", "rate this post"). For a site-wide health check (orphan pages, cannibalization, stale content, schema across all posts) use blog-audit instead.

The English summary is being prepared. Showing the original description.

Use the free built-in .NET SDK analyzers and analysis levels with gradual Roslyn warning promotion. USE FOR: the repo wants first-party .NET analyzers; CI should fail on analyzer warnings; the team needs AnalysisLevel or AnalysisMode guidance. DO NOT USE FOR: third-party analyzer selection by itself; formatting-only work. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.

The English summary is being prepared. Showing the original description.

Analyze an open-source project from What/Why perspective (not how-it's-implemented). Use when the user says "/analyze-oss", "분석해줘 이 오픈소스", "이 레포 뭐하는거야", "analyze this repo", "what does X do", "이거 왜 쓰는거야", "이 라이브러리 분석", provides a GitHub URL and wants understanding, or asks to deeply understand an OSS project's purpose, value, target users, and usage flow. Clones the repo to ~/opensource-analysis/<repo-name>/ (git pull if already exists), dispatches parallel subagents per analysis lens, then synthesizes a What/Why-focused report in chat. Supports optional user-specific follow-up questions.

The English summary is being prepared. Showing the original description.

Analyze LLM eval results — score breakdowns by category, regression detection vs baseline, failure clustering. Use when asked to "analyze our eval results", "did the model regress", or "cluster the eval failures".

The English summary is being prepared. Showing the original description.

Analyze A/B test results — statistical significance, practical significance, and segmentation. Use when asked to "analyze our A/B test", "is this result significant", or "read these experiment results".

The English summary is being prepared. Showing the original description.

Automates batch reverse engineering by generating Ghidra analyzeHeadless commands and post-analysis script skeletons to import, auto-analyze, and export results for many samples without the GUI. Activates for requests to script Ghidra headless analysis, batch-analyze samples with Ghidra, or generate an analyzeHeadless command and post-script.

The English summary is being prepared. Showing the original description.