1443 个 · 按相关度排序
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.
中文简介正在准备中。当前显示原文说明。
Use when rating whether a project, repo, skill, workflow, plugin, agent product or post uses TypeSafe's Jev (System One) model well -- "is this a good use of Jev?", "rate this Jev integration", "jevaluate <url>", or a link to something named after Jev; also when checking whether something that calls itself Jev actually uses it.
中文简介正在准备中。当前显示原文说明。
Use when testing whether the jevaluate rubric and instructions lead graders to the right answers: after a rubric or instruction change, before freezing a rubric, before publishing ratings, or when a grader's calls look wrong.
中文简介正在准备中。当前显示原文说明。
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.
中文简介正在准备中。当前显示原文说明。
Improve AI application with evaluation-driven development. Define eval criteria, instrument the application, build golden datasets, observe and evaluate application runs, analyze results, and produce a concrete action plan for improvements. ALWAYS USE THIS SKILL when the user asks to set up QA, add tests, add evals, evaluate, benchmark, fix wrong behaviors, improve quality, or do quality assurance for any Python project that calls an LLM model.
中文简介正在准备中。当前显示原文说明。
Evaluate design from a UX perspective, assessing visual hierarchy, information architecture, emotional resonance, cognitive load, and overall quality with quantitative scoring, persona-based testing, and actionable feedback. Use when the user asks to review, critique, evaluate, or give feedback on a design or component.
中文简介正在准备中。当前显示原文说明。
Evaluate design from a UX perspective, assessing visual hierarchy, information architecture, emotional resonance, cognitive load, and overall quality with quantitative scoring, persona-based testing, and actionable feedback. Use when the user asks to review, critique, evaluate, or give feedback on a design or component.
中文简介正在准备中。当前显示原文说明。
Generate, evaluate, and improve Rosetta Stone attribute mappings for a Narrative dataset. Use when: "map this dataset to Rosetta Stone", "suggest normalized attributes for dataset N", "evaluate the mappings on dataset N", "why is this mapping low confidence", "fix this expression", "improve this NQL mapping expression". (narrative-common)
中文简介正在准备中。当前显示原文说明。
Improve AI application with evaluation-driven development. Define eval criteria, instrument the application, build golden datasets, observe and evaluate application runs, analyze results, and produce a concrete action plan for improvements. ALWAYS USE THIS SKILL when the user asks to set up QA, add tests, add evals, evaluate, benchmark, fix wrong behaviors, improve quality, or do quality assurance for any Python project that calls an LLM model.
中文简介正在准备中。当前显示原文说明。
Marp形式プレゼンテーションの専門レビュー・評価・改善スキル。 10軸スコアリング（100点満点）で品質を定量評価し、具体的な改善コード付きで提案する。 Use when the user asks to: - Review, evaluate, or critique a Marp presentation / プレゼンをレビュー / 評価 / 添削 - Improve, polish, or upgrade existing slides / スライドを改善 / ブラッシュアップ - Check slide quality, score slides, or audit a deck / スライドの品質チェック / 採点 - "このプレゼンどう？" "スライドを見てほしい" "プレゼン資料のフィードバック" Reads .md files with Marp frontmatter, scores across 10 dimensions, and outputs a detailed review report with concrete before/after code improvements. Works as a companion to the marp-slides skill (generation → review → improvement cycle).
中文简介正在准备中。当前显示原文说明。
Apply critical rationalist epistemology (Popper, Deutsch) to evaluate reasoning, identify errors, and refine understanding. Use when the user explicitly requests help with reasoning - phrases like "help me think this through", "does this make sense", "any flaws in this", "what am I missing", "critique this", "is this reasoning sound", "stress test this idea", "devil's advocate", or any request to evaluate arguments, identify logical problems, or improve thinking. Also use when errors in reasoning are significant enough to materially affect the user's goals, even if not explicitly requested.
中文简介正在准备中。当前显示原文说明。
Evaluate design from a UX perspective, assessing visual hierarchy, information architecture, emotional resonance, cognitive load, and overall quality with quantitative scoring, persona-based testing, and actionable feedback. Use when the user asks to review, critique, evaluate, or give feedback on a design or component.
中文简介正在准备中。当前显示原文说明。
Claude Code のセッション記録（~/.claude の履歴・セッションログ・memory）から、週ごとの問い（questions.json）に答える「ナレッジカード」を下書きし、本人が確認・修正したうえで機密スキャンを通し、Notion の「ナレッジカード」DB に提出する。引数なしなら先週（月曜〜日曜）の記録を集計し、確認のうえ Notion に提出する。「Claude Code の履歴をナレッジカードにまとめて」「先週のログからナレッジカードを作って」「ナレッジカードを提出したい」「今週のカードを出して」「週次の振り返りカードを作って」などの依頼で使う。週次のカード提出であり、個人の採点や評価ではない（セッション 1 本の採点は evaluate-session の領域）。
中文简介正在准备中。当前显示原文说明。
週ごとに Notion「ナレッジカード」DB に集まったカードを読み、問いをまたいで親和図にまとめ、正（worked）と反（failed）の対立から合（提案）を出し、次の問いを決めて、「合成テーマ」DB と週の行の配下の「まとめ」ページに書き込む。「今週のカードを合成して」「W43 のまとめを作って」「ナレッジカードの合成」などの依頼で使う。カードの提出は knowledge-cards、個人の採点は evaluate-session の領域。個人別の件数ランキングや「誰が何を失敗した」は出さない。
中文简介正在准备中。当前显示原文说明。
Evaluate design from a UX perspective, assessing visual hierarchy, information architecture, emotional resonance, cognitive load, and overall quality with quantitative scoring, persona-based testing, and actionable feedback. Use when the user asks to review, critique, evaluate, or give feedback on a design or component.
中文简介正在准备中。当前显示原文说明。
スキル使用後の observation（結果・問題・フィードバック）を記録する。 スキルの改善サイクル（Observe → Inspect → Amend → Evaluate）の起点。 使用後に `/skill-observe <スキル名> <結果> [問題/フィードバック]` で呼び出す。
中文简介正在准备中。当前显示原文说明。
蓄積された observations を分析し、SKILL.md への改善提案を生成する。 Observe → Inspect → Amend → Evaluate ループの Inspect/Amend フェーズ。 `--apply` フラグで承認後の適用も可能。
中文简介正在准备中。当前显示原文说明。
Claude Code の過去のセッション記録（~/.claude の履歴・セッションログ・memory）から、他のメンバーと共有できる運用 Tips を抽出し、公式ドキュメントや論文などの一次情報で裏付けを取って、Markdown・Artifact・Notion に公開する。「過去の会話から Tips をまとめて」「Claude Code の使い方をチームに共有したい」「今月の学びを Tips にして」などの依頼で使う。セッション 1 本の効率採点ではない（それは evaluate-session の領域）。週次のナレッジカード提出は knowledge-cards で行い、このスキルはカードや記録から Tips 文書を作る下流工程にあたる。
中文简介正在准备中。当前显示原文说明。
Validate process decomposition and architecture design quality before execution begins. Load when the setup-evaluator agent fires (automatic for agent-chain tasks), or when user says "evaluate this setup", "check the decomposition", "validate the architecture", "is this plan sound", "review the agent design". Catches structural errors, missing knowledge, unrealistic step ordering, and topology mismatches. Does NOT modify — only evaluates.
中文简介正在准备中。当前显示原文说明。
Evaluate design from a UX perspective, assessing visual hierarchy, information architecture, emotional resonance, cognitive load, and overall quality with quantitative scoring, persona-based testing, and actionable feedback. Use when the user asks to review, critique, evaluate, or give feedback on a design or component.
中文简介正在准备中。当前显示原文说明。
Systematically evaluate architecture decisions, document trade-offs, and select appropriate patterns. This skill should be used when the user asks about 'architecture decision', 'ADR', 'design pattern selection', 'technology choice', or needs to evaluate architectural trade-offs. Keywords: architecture, ADR, patterns, trade-offs, technical debt, quality attributes, decision record.
中文简介正在准备中。当前显示原文说明。
Decision tree analysis for complex decision-making across all domains. Use when user needs to evaluate multiple options with uncertain outcomes, assess risk/reward scenarios, or structure choices systematically. Applicable to business, investment, personal decisions, operations, career choices, product strategy, and any situation requiring structured evaluation. Triggers include decision tree, should I, what if, evaluate options, compare alternatives, risk analysis.
中文简介正在准备中。当前显示原文说明。
通过操作次数与实测数据排查OpenClaw启动、聊天和界面显示缓慢的原因，优先减少不必要的处理，并支持性能改进PR的编写与审查。