「evaluate」の検索結果

Scaffold, run, inspect, and evaluate model-agnostic agents that connect to MCP servers, skills, shell tools, and workflow packs.

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

Rates any SKILL.md on a 0-100 scale across 10 dimensions with a SHIP / REWORK / SCRAP verdict. Evaluates trigger precision, instruction clarity, output predictability, edge case coverage, anti-hallucination guardrails, developer experience, composability, open-source readiness, wow factor, and real-world utility. No flattery — calibrated against Anthropic's own skill-creator rubric. Use this skill whenever someone says "score this skill", "rate my skill", "is this skill good", "skill review", "skill audit", "roast my SKILL.md", "grade this", "will this skill work", "evaluate my skill", "how good is this", or pastes a SKILL.md and asks for feedback. Also trigger when comparing two skills, benchmarking a skill collection, or asking "what's wrong with this skill" — even without the word "score".

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

Evaluate tabulated subcontractor bids against specs and drawings — scope gap analysis, exclusion risk scoring, award recommendation. Triggers: 'evaluate bids', 'bid evaluation', 'lowest responsible bidder'.

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

Evaluate design from a UX perspective with Nielsen's heuristics scoring, anti-pattern detection, persona-based testing, and actionable feedback. Report-only. Triggers on critique, UX review, design feedback, how does this look, evaluate the design, component review.

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

Evaluates and scores Claude prompts and system prompts using a six-dimension Scorecard with anchored 1-5 rubrics. Trigger on: "review my prompt," "score this prompt," "rate my prompt," "evaluate this prompt," "improve my prompt," "what's wrong with my prompt." Also trigger on: "why isn't my prompt working," "my prompt produces bad output," "help me fix this prompt," "is this prompt any good." Scorecard covers Objective Clarity, Context Specificity, Reasoning Fit, Output Precision, Behavioral Calibration, and Architectural Efficiency, plus a five-question Output Evaluation Rubric for assessing actual output. Also use when the user pastes a system prompt and asks for feedback. Activate whenever structured quality assessment of a single prompt is the primary need. Do NOT use for project-level audits involving Custom Instructions architecture, knowledge file organization, or multi-file Project structure (use rootnode-project-audit if available).

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

Selects the active profile from triggering context. Evaluates a rule set against inputs (current time, calendar state, geofence, manual command, custom signals) and returns the profile name that consuming Skills (handoff-trigger-check, critic-gate, future Skills) should apply. Configuration-driven; rule set lives in a router config file conforming to the included schema. Deterministic precedence — manual override beats calendar beats time-window beats default. Required default profile guarantees a routing decision always exists. Use when an orchestrator needs to pick a profile automatically rather than having the caller specify one, when wiring calendar/time/Telegram triggers to gate behavior, or when a Skill's behavior should change with availability mode. Trigger on: "what profile should I use," "route to a profile," "which mode am I in," "auto-select profile," "active mode," "current profile." Do NOT use to evaluate work readiness or review proposed changes. Always returns a profile name.

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

Assess an open-source agent framework for investment readiness by evaluating community health, supersession risk, architecture alignment, and governance sustainability. Produces a four-tier classification (INVEST / EVALUATE-FURTHER / CONTRIBUTE-CAUTIOUSLY / AVOID) to guide resource allocation decisions before committing engineering effort.

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

Evaluate and simplify Boolean expressions using truth tables, algebraic laws (De Morgan, distributive, absorption, idempotent, consensus), and Karnaugh maps for up to six variables. Use when you need to reduce a Boolean expression to its minimal sum-of-products or product-of-sums form, verify logical equivalence between two expressions, or prepare a minimized function for gate-level implementation.

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

Evaluate and compare levitation mechanisms for a given application through a structured trade study. Covers magnetic (passive diamagnetic, active feedback, superconducting), acoustic (standing wave, phased array), aerodynamic (hovercraft, air bearings, Coanda effect), and electrostatic (Coulomb suspension, ion traps) mechanisms. Use when selecting the most appropriate levitation approach for transport, sample handling, display, bearings, or precision measurement applications.

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

执行模型测评（统一入口）。LLM/VLM 走主流程 scripts/run_evaluation.py + Evaluation YAML；model_family=dit 走 DiT 扩展节（references/dit/evaluate_workflow.md，vbench.py 批量推理产出视频）。

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

Assesses a research paper outline (.qmd file) against structured criteria from Kosuke Imai's empirical research guide. Evaluates the abstract and section outline for: research question clarity, stated contributions, hypotheses and testable implications, data description, planned results and inferential approach, and robustness checks. Detects causal papers from the abstract and conditionally assesses identification strategy only when causal framing is present. Produces a structured markdown report with PASS/PARTIAL/FAIL assessments and actionable suggestions. Use when asked to assess, evaluate, review, or check a paper outline, abstract-and-outline, or research plan in a .qmd file.

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

"Apply the TPACK framework to evaluate and design technology-integrated instruction at the intersection of technological, pedagogical, and content knowledge. Use this skill when the user needs to assess teacher readiness for technology integration, design professional development for ed-tech, or evaluate whether technology use is pedagogically grounded — even if they say 'how to integrate technology in teaching', 'ed-tech evaluation', or 'teacher technology competency'.".

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

"Apply the Efficient Market Hypothesis (Fama, 1970) to evaluate information incorporation in asset prices across weak, semi-strong, and strong forms. Use this skill when the user needs to assess market efficiency, determine if a trading strategy can generate abnormal returns, evaluate event studies, or when they ask 'can technical analysis work', 'does the market already know this', or 'is this anomaly exploitable'.".

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

"Apply pragmatist philosophy (Peirce, James, Dewey) to frame knowledge as instrumental for action, evaluate ideas by their practical consequences, and conduct inquiry as problem-solving. Use this skill when the user needs to bridge theory and practice, evaluate competing theories by their usefulness, employ abductive reasoning to generate hypotheses, or when they ask 'which theory is more useful here', 'how do I move from abstract ideas to actionable knowledge', or 'what practical difference does this distinction make'.".

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

"Analyze unit economics to evaluate per-unit profitability and business model scalability. Use this skill when the user needs to assess whether each transaction, customer, or product unit is profitable, evaluate startup viability, or optimize contribution margins — even if they say 'does our business model work', 'what's our margin per order', or 'can we scale profitably'.".

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

"Calculate and analyze Customer Acquisition Cost (CAC) and Customer Lifetime Value (LTV) to evaluate unit economics and marketing efficiency. Use this skill when the user needs to assess whether their customer acquisition is profitable, optimize marketing spend allocation, or evaluate business model viability — even if they say 'are we spending too much on ads', 'what's each customer worth', or 'is our growth sustainable'.".

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

Build a weighted decision matrix to evaluate options. Use when the user says "decision matrix", "compare options", "weighted scoring", "which option should we choose", "evaluate alternatives", "Wiegers priority matrix", "force field analysis", "decision table", "trade-off analysis", "option comparison" - even if they don't explicitly say "decision matrix".

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

Analyze catastrophe modeling systems for natural disaster exposure, PML estimation, and reinsurance optimization. Use when: 'assess cat model', 'evaluate disaster exposure', 'review PML calculations', 'audit reinsurance program', 'check exposure data quality', 'analyze hurricane/earthquake risk models', 'evaluate Oasis or RMS setup'.

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

Analyze ad creatives (images and videos) extracted from competitor research. Use when given a directory of ad images, video files, or transcripts to evaluate ad quality, score visual and messaging effectiveness, assign a scale score for viral/engagement potential, and generate a cross-creative pattern summary. Triggered by requests like "analyze these ads", "score these creatives", "what hooks are competitors using", "evaluate the ad library", "give me a scale score", "analyze the ad folder", or "what's working in these ads".

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

Code auditor that grades software projects and the agents/developers who built them. Produces structured JSON + Markdown reports with a standardized rubric. Evaluates architecture, correctness, testing, authorship cohesiveness, ghost code, and more. Optionally ingests tmux session logs for process evidence and interrogates agents about specific problems found. Use when asked to "audit", "grade", "evaluate", "review code quality", "rate this project", "score the agents", or "assess the codebase". Especially useful after Marcus multi-agent experiments to grade agent output and track quality over time.

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

Deliberate system-improvement loop — audit your own Claude Code setup (rules / memory / skills / MCP / agents / registry), evaluate incoming tools via /vet, adopt the worthwhile ones with discipline (backup → verify), and record every decision. Use when bringing in a tool/idea/collection to improve the setup, or when doing a tooling-improvement pass. Triggers — "upgrade the workflow", "audit our setup", "let's improve the tooling", "evaluate this for us", when handed a post/repo/reel with a tool.

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

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).

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

Experimental behavioral evaluator. Drives a running artifact via browser/curl/CLI and records rubric evidence; the runner is not yet a fully implemented automated evaluation system.

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

Evaluate design from a UX perspective, assessing visual hierarchy, information architecture, emotional resonance, cognitive load, and overall quality with quantitative scoring, persona-based testing, automated anti-pattern detection, and actionable feedback. Use when the user asks to review, critique, evaluate, or give feedback on a design or component.

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