「diagnose」の検索結果

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.

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

When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," or "indexing issues." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema. For AI search optimization, see ai-seo.

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

Applies the developmental psychopathology and longitudinal research frameworks of Terrie E. Moffitt (psychologist, Duke University). Use this skill whenever reasoning about human development, criminology, juvenile delinquency, self-control, mental health trajectories, or biological aging. Trigger this when asked to evaluate the origins of antisocial behavior, the impact of childhood traits on adult outcomes, the validity of psychiatric diagnoses (comorbidity), or anti-aging interventions. Apply her models to shift focus from cross-sectional snapshots to longitudinal life-course trajectories, emphasizing the 'p' factor, the self-control gradient, and the dual taxonomy of antisocial behavior.

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

Diagnose a concrete rendered hitch or stutter.

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

Diagnose measured runtime and Core Web Vitals.

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

Diagnose GSAP and ScrollTrigger performance.

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

Fix bugs and broken behavior when there is enough evidence to act on a repair path. Use for errors, crashes, incorrect results, API failures (500, 404, 403), CORS problems, database exceptions, broken rendering, duplicated or wrong data, off-by-one mistakes, timezone/date bugs, broken forms, config-caused runtime failures, and regressions. Trigger when the user wants the bug repaired and the conversation already contains a clear failing area, a reproducible failing test, a concrete error path, or a prior diagnosis to implement. Do NOT use for new features, pure explanation, architecture discussion, broad research, or bug reports where the main need is figuring out why the behavior happens — use diagnose for that.

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

The single config quality skill. Two modes: (1) Default — review/wire pending self-improvement proposals. (2) Audit — analyzes skills, rules, CLAUDE.md, project refs, hooks, and agents against the actual codebase to find inaccuracies, trigger overlaps, stale references, and weak rules, then fixes them. Trigger on 'self-evolve', 'evolve', 'config health check', 'audit config', 'check claude setup', 'apply this rule', 'reorganize rules', 'ok' (when proposals are pending). NOT for improving individual skills (use skill-creator), diagnosing code bugs (use diagnose), or fixing broken code (use fix).

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

Investigate unexpected behavior and mysterious bugs. Use when the cause of a problem is unknown and the user needs to understand WHY something is happening — symptoms like: sudden unexplained changes in metrics or behavior, works locally but not in staging/production, inconsistent or intermittent failures, correct code producing wrong results, operations succeeding but having no effect, environment-specific failures, duplicate executions, stale data, or any "why did this change?" or "why is this happening?" situation. Covers infrastructure anomalies (cache hit rates dropping, latency spikes, queue behavior shifts) as well as code bugs. The key signal is confusion about root cause, not a request to implement a known fix. Do NOT use for feature requests, known fixes, planning, or documentation tasks.

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

Use when the user wants to know if something works — the answer requires running code, not analyzing it. Output is a verdict backed by evidence: passed, failed, or broken. Primary triggers: 'run the tests', 'does X still work after my change?', 'did the merge break anything?', 'verify the fix worked', 'check if the endpoint returns X', 'confirm nothing regressed', 'run tests/unit/test_foo.py', 'let me know the results', 'make sure my changes didn't break anything'. Hard stops — do NOT use for: reviewing test code for quality/coverage gaps, debugging why test infrastructure/databases/seed scripts are misbehaving, writing or fixing tests, diagnosing root causes of unexpected behavior. The deciding question: is the user asking for the result of executing something, or asking for help understanding/analyzing/improving something? If it's the latter, use diagnose or review-code instead.

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

Diagnoses and fixes slow Neo4j Cypher queries by reading execution plans, identifying bad operators (AllNodesScan, CartesianProduct, Eager, NodeByLabelScan), and prescribing fixes (indexes, hints, query rewrites, runtime selection). Use when a query is slow, when EXPLAIN or PROFILE output needs interpretation, when dbHits or pageCacheHitRatio are poor, when cardinality estimation diverges from actuals, or when deciding between slotted/pipelined/parallel runtimes. Covers USING INDEX / USING SCAN / USING JOIN hints, db.stats.retrieve, SHOW QUERIES, SHOW TRANSACTIONS, TERMINATE TRANSACTION. Does NOT write new Cypher from scratch — use neo4j-cypher-skill. Does NOT cover GDS algorithm tuning — use neo4j-gds-skill. Does NOT cover index/constraint creation syntax details — use neo4j-cypher-skill references/indexes.md.

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

Write, run, and analyze structured test suites for Agentforce agents — functional AND security. TRIGGER when: user writes or modifies test spec YAML (AiEvaluationDefinition); runs sf agent test create, run, run-eval, or results commands; asks about test coverage strategy, metric selection, or custom evaluations; interprets test results or diagnoses test failures; asks about batch testing, regression suites, or CI/CD test integration; requests security testing, OWASP LLM Top 10, red-teaming, penetration testing, prompt-injection tests, a security grade, or a vulnerability assessment of an agent. DO NOT TRIGGER when: user creates, modifies, previews, or debugs .agent files (use agentforce-generate); deploys or publishes agents; writes Agent Script code; uses sf agent preview for development iteration; analyzes production session traces (use agentforce-observe); performs a static safety review of .agent file content (use agentforce-generate Section 15).

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

Evaluate any agent skill against a merged framework — Anthropic's Claude Code best practices plus Matt Pocock's writing-great-skills methodology — across 4 axes (Trigger, Structure, Steering, Pruning). Produces an evidence-cited scorecard (0–100), a weighted overall score, and diagnosed failure modes with prioritized fixes. Use when the user asks to evaluate, rate, or audit a skill ("evaluate this skill", "skill scorecard", "review SKILL.md"), or to compare two skills.

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

Inspect and diagnose minimal-zine posters, photo restyles, editorial images, and social-card series for subject preservation, factual and text integrity, composition, paper realism, print-process coherence, color signal, anti-AI craft, platform fit, and series continuity. Use when the user asks whether an image has高级感, feels AI-generated, matches Paper Signal or gc-minimal-zine quality, needs improvement, or should be regenerated. Returns evidence-based findings and a targeted correction prompt; regenerates only when the user also asks for a fix.

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

Diagnoses and improves measured latency, throughput, memory, CPU, bundle, rendering, query, or resource performance by defining a target, profiling a representative workload, locating the bottleneck, making one change at a time, and comparing before/after evidence. Use for performance work or regressions. Not for guessing optimizations without a reproducible workload or for generic refactoring.

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

Diagnoses slow services and regressions via profiling and tail-latency math. Use when diagnosing slow services, profiling hot paths, or judging whether an optimization is real.

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

Diagnoses stalled teams or agent hierarchies with Beer's VSM and Ashby's Law. Use when orchestrators overload, escalations pile up, or team boundaries need redesign.

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

Formulates LP, MILP, CP-SAT models; diagnoses infeasibility and gaps. Use when a MILP is infeasible, shifts need scheduling under capacity, or choosing a solver.

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

Diagnoses and tunes SQL for OLTP workloads on PostgreSQL, MySQL, and SQL Server. Use when tuning queries, reading plans, indexing, or fixing lock contention.

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

Claude adapter for diagnosing PlainTab bugs, broken flows, startup issues, storage or wallpaper regressions, and performance regressions.

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

Use when diagnosing PlainTab bugs, broken UI behavior, failing extension/web-mode flows, storage or wallpaper regressions, startup issues, or performance regressions.

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

Diagnose HitKeep traffic drops, spikes, source shifts, and suspicious changes. Use when traffic, sessions, visitors, pageviews, events, or conversions changed; when a deploy may have affected measurement or behavior; or when search, referral, direct, campaign, and bot explanations need to be separated.

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

Reinforces an AI agent by turning Monte Carlo's reinforcement loop diagnosis into code fixes. Reads the daily reinforcement loop report for an agent's workflows, ranks the diagnosed issues, proposes what to fix, and — with the user's approval at each step — opens a pull request. Activates on "fix my agent", "improve my agent's health", "reinforce my agent", "what should I fix in my agent". Not for investigating a specific agent alert or trace (monte-carlo-troubleshoot-agent-traces), creating agent monitors (monte-carlo-monitoring-advisor), or instrumenting a new agent (monte-carlo-instrument-agent).

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

Diagnoses pipeline performance issues -- slow jobs, expensive queries, latency trends -- using Monte Carlo's cross-platform observability. Uses a tiered investigation approach: discover problems, bridge to affected tables, then drill into root causes. Activates when a user asks about slow pipelines, expensive queries, or performance regressions.

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