「evaluate」の検索結果

Brainstorms and debates approaches, then drives toward an actionable decision. Use whenever someone needs a thinking partner for a decision they're facing: 'discuss', 'debate', 'brainstorm', 'weigh options', 'tradeoffs', 'should I do X or Y', 'help me decide', 'I'm torn between', 'sanity check my thinking', or 'what do you think about'. The user must be asking for help reasoning through a choice — not asking to build, fix, evaluate, plan, or modify something (even if the topic involves this skill itself). Picks the right decision lens, surfaces tradeoffs and blind spots, pushes back when reasoning is genuinely weak, and never implements.

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

Review test quality using best practices validation. Use when user says "lets review tests" or "I want to evaluate test quality"

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

Audit NFR evidence for performance, security, reliability, and maintainability. Use when implementation evidence exists and the user says "audit NFR evidence", "audit NFRs", or "evaluate non-functional requirements"

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

Evaluate proposed repository harness changes with pinned Darwin tools and explicit evidence limits.

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

Evaluates neuromarketing studies and neural-data law. Use when judging EEG, fMRI, eye-tracking, or GSR ad study or vendor, or if signals are regulated neural data.

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

Update Claude Code (the CC CLI / "clog code") to a new version, or bump the pinned CC version. Use when the user asks to update Claude Code, bump the CC pin, evaluate a new CC release, or says "clog code update". Routes to the canonical, standardized process in docs/reference/cc-compatibility.md — do NOT re-derive the update mechanism by grepping every time. Do NOT use for general "what changed in CC" trivia with no intent to update.

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

Quality review of test files and manual evidence documents. Goes beyond existence checks — evaluates assertion coverage, edge case handling, naming conventions, and evidence completeness. Produces ADEQUATE/INCOMPLETE/MISSING verdict per story. Run before QA sign-off or on demand.

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

Read all open bugs in production/qa/bugs/, re-evaluate priority vs. severity, assign to sprints, surface systemic trends, and produce a triage report. Run at sprint start or when the bug count grows enough to need re-prioritization.

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

Brainstorming interactively to deepen ideas via four modes (Expand/Propose/Evaluate/Subtract). Does not write code. Not for decisions (Magi), feature specs (Spark), or one-shot reframing (Flux).

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

Simulating users to evaluate existing flows and generate synthetic demand: cognitive walkthroughs, feature requests, unmet needs, JTBD, and opportunity trees. Not real-user research.

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

Product AI Visibility & Ranking — evaluate how AI search engines (ChatGPT, Claude, Gemini, DeepSeek) recommend your product when shoppers ask buying questions. Triggers: AI visibility, product AI ranking, AI recommend, AI search, does AI mention my product.

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

Use Nexscope market list capability to filter Amazon niche markets by category dimensions, supporting market size, competition, top concentration, seller structure, new product share, price/rating/margin ranges, and many other criteria for discovering viable markets and evaluating product selection directions. Trigger when the user mentions Amazon market research, niche category research, market opportunity screening, market concentration analysis, new product opportunities, market selection, Nexscope market research, category market research. Even if the user does not explicitly mention "Nexscope", if the need is to screen and evaluate Amazon markets by category dimensions, this skill should also be triggered.

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

Design a source evaluation protocol using lateral reading and credibility checks for digital information. Use when students need to evaluate websites, online sources, or social media claims.

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

Require the learner to explain a concept in their own words before the AI evaluates or extends it. Ensures the AI works from the learner's understanding rather than providing an explanation from scratch.

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

Design a Funhouse Mirror activity where students use their own domain expertise to detect AI distortions, omissions, and overconfidence. Use when students know a subject well enough to evaluate AI claims about it.

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

Find, evaluate and install a ForgeCat profile. Use when the user wants to browse the registry, compare profiles, install one into a project or a home-target agent, or when an install is refused.

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

Evaluate a teacher-drafted central historical question for its capacity to drive genuine historical inquiry. Use when assessing whether a question will generate real evidence-weighing or produce shallow responses.

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

Design a structured protocol for auditing AI-generated text against Ennis's six CT standards. Use when students need to critically evaluate AI output in any subject.

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

After any AI-generated explanation, require the learner to identify one place it could be wrong, one thing to check, and one source to consult. Builds epistemic vigilance — treats AI output as a claim to evaluate, not truth to absorb.

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

Generate and evaluate grounded ideas. Use when the user asks for ideas, improvements, surprising options, or AI-generated directions before choosing one to develop; use ce-brainstorm to refine the user's own idea.

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

When the user wants to plan, evaluate, or build a free tool for marketing purposes — lead generation, SEO value, or brand awareness. Also use when the user mentions "engineering as marketing," "free tool," "marketing tool," "calculator," "generator," "interactive tool," "lead gen tool," "build a tool for leads," "free resource," "ROI calculator," "grader tool," "audit tool," "should I build a free tool," or "tools for lead gen." Use this whenever someone wants to build something useful and give it away to attract leads or earn links. For downloadable content lead magnets (ebooks, checklists, templates), see lead-magnets.

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

Runs the evals of a BMad skill through the agent harness the user works in and reports what they show: baseline against the bare model, variant against a stripped or prior version, quality against a rubric, and trigger accuracy of the description with an optional optimization loop. Use when the user asks to evaluate, benchmark, test the triggers of, grade, or compare versions of a skill, or when the bmad-toolsmith skill asks for an eval of a skill it built.

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

Evaluates ambient context artifacts (CLAUDE.md, memory, local skills, settings hooks) for compatibility with swarm governance. Returns a classified report so users can address interference before launching a team.

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

Evaluate proposed repository harness changes with pinned Darwin tools and explicit evidence limits.

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