「claim」の検索結果

論文や研究計画を共通の評価基準で読み、研究方法、根拠、引用、文章構成を点検するスキル。評価の理由と修正の優先順位、次に直す内容を整理します。

• 投稿前の論文を見直したいとき
• 引用が主張を支えるか確認したいとき
• 研究方法と限界を評価したいとき

顧客や取引先への返信案を人の承認に結び付け、承認された本文と送信先、送信結果を記録します。修正前の古い承認による送信や、複数の担当処理による重複送信を防ぐ設計です。

• 顧客への返信を承認制にしたいとき
• 承認本文と送信結果を記録したいとき
• 修正前の承認による送信を防ぎたいとき

製品や新機能の発売に向け、顧客・競合調査から訴求方針、LP、メール、SNS、広告、短尺動画の原稿と投稿予定を組み立てるスキル。媒体間の表現や主張も点検します。

• 製品や新機能の発売企画
• 製品概要から各媒体の原稿を作るとき
• 複数媒体の訴求をそろえたいとき

投資家向けの説明資料や財務モデル、資金使途表、応募書類を作成・更新し、事業実績や収益の前提、調達額、チーム情報の食い違いを複数の資料で確認するスキル。

• 投資家向け説明資料を作成・改訂したいとき
• 投資家向け概要資料やメモを作りたいとき
• 収益予測と資金使途表を作りたいとき

AIエージェントの不調を、指示・記憶・ツール実行・画面表示など12の層から調べるスキル。コードやログを根拠に原因を整理し、重要度順の指摘と修正案をまとめます。

• アプリ内だけで起きる不調を調べたいとき
• 過去の会話が混ざる原因を調査
• ツールの未実行や実行の誤報を確認

競合のブランド表現やサービス、実績などを共通の基準で採点し、根拠付きの比較カードと戦略上の二軸図にまとめ、自社が狙う位置の競合を把握するスキル。

• 共通基準で競合を比較したいとき
• 根拠付きの競合カード作成
• 二つの戦略目標で競合を整理したいとき

記事・論文・メモを要約し、相互リンク付きのMarkdown知識集として蓄積。出典を残しながら質問への回答や比較をまとめ、矛盾やリンク切れも点検します。

• 記事や論文から調査用の知識集を作成
• 新しい資料を既存のノートに追加
• 出典付きの回答や比較を保存

After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.

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

Deploy applications and websites to Vercel. Use this skill when the user requests deployment actions such as "Deploy my app", "Deploy this to production", "Create a preview deployment", "Deploy and give me the link", or "Push this live". No authentication required - returns preview URL and claimable deployment link.

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

Static security scan of a harness's declared MCP surface via `harness mcp-scan {path}`. Reads `.mcp/servers.json` + `.harness/claims.json`. Pure-read, no dispatch. Exits 1 on findings at or above `--fail-on` severity.

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

Run the corpus benchmark — booster locally, optional Gemini/Sonnet/Opus baselines — and persist a verifiable measured-vs-claimed table

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

Checks an AI team run against its acceptance criteria using the evidence bundle. Use when the user asks whether the work is done or correct, or before completing a run. Separates verified evidence from agent claims.

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

Creates, assigns, and updates tasks in an AI team run so work has one owner and one deliverable each. Use when the user asks to break down, assign, claim, block, or complete tasks in a run. Changes recorded task state only.

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

Use when auditing content pages for citation quality, suggesting authoritative sources to link for factual claims, or reviewing whether a page's external link attributes (nofollow, noopener) are correctly set.

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

Runs maximum-saturation research with a cooperating team, claim-graph gating, and a cited, QA'd deliverable. Use when the user explicitly asks for research or a deep investigation, including any 'ulw' research wording.

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

Read-only GitHub triage for issues AND PRs. 1 item = 1 background task (category: quick). Analyzes all open items and writes evidence-backed reports to /tmp/{datetime}/. Every claim requires a GitHub permalink as proof. NEVER takes any action on GitHub - no comments, no merges, no closes, no labels. Reports only. Triggers: 'triage', 'triage issues', 'triage PRs', 'github triage'.

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

Create, write, or manage Meta ads and assets: ad copy, campaigns, spend, reports, audiences, catalogs, product feeds, feed refresh schedules, experiments, and policy. Always load for any request to create or write an ad, or to advertise a product or service, even when no platform is named; this includes sensitive or restricted categories. Always load for any question asking what a Meta, Facebook, or Instagram advertising policy means, allows, prohibits, or requires, including a standalone policy-definition question with no account context. Those questions must use ads_policy_tool, never browser search or memory. Load for a specifically named catalog or feed with an upload or refresh-schedule request; use Ads reads to resolve ownership before writing. Generic unnamed feeds need context. Whether an image, claim or piece of copy may be used in an ad is ALWAYS a Meta Ads task — 'can I use this in an ad', 'is it allowed', 'is this against policy', and any rights, likeness, celebrity, logo or trademark question about advertising with an image, including a follow-up about one just generated. Those are ads-policy questions, not general legal ones. An ad request uses the campaign workflow unless explicitly only an image or organic post.

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

Deep research harness — fan-out web searches, fetch sources, adversarially verify claims, synthesize a cited report.

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

Create, hand off, claim, execute, and close agent tasks through the MemPalace logstream. Use when the user wants to delegate work, prepare a ready-to-paste task for another agent, receive a MemPalace task id, or explicitly launch a supported headless agent in controlled mode.

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

Rewrite AI-sounding text so it reads like the writer without changing what it says. Use when editing or reviewing prose for AI tells: not-X-but-Y contrasts, one-line closers, staged openers, forced triads, dashes everywhere, inflated claims, sales language, stock AI words, bold labels, or filler. Based on Wikipedia's "Signs of AI writing."

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

When the user wants to create competitor comparison or alternative pages for SEO and buyer-facing use. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' 'competitive landing pages,' 'how do we compare to X,' 'competitor teardown,' 'audit our competitor pages,' 'are our comparison pages out of date,' or 'competitive asset audit.' Use this for any content that positions your product against competitors. Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. For auditing existing claims (not researching competitors from scratch, which is competitor-profiling; not technical SEO on these pages, which is seo-audit), use the asset audit here. For internal battle cards and sales-specific competitor docs, see sales-enablement.

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

Multi-perspective academic paper review with dynamic reviewer personas. Runs a 5-seat, role-separated review panel (Journal-Fit Reviewer + 3 peer-review roles + Devil's Advocate) with field-specific expertise; role separation is not a claim of independent error processes. Supports full review, re-review (verification), quick assessment, methodology focus, Socratic guided, and calibration modes. Triggers on: review paper, peer review, manuscript review, referee report, review my paper, critique paper, simulate review, editorial review, calibrate reviewer, reviewer calibration, measure reviewer accuracy, 審查論文, 論文審查, 模擬審查, 同儕審查, 幫我審這篇, 以審查人角度評估, 審查者校準, 논문 심사, 동료 심사, 모의 심사, 심사자 관점에서 평가, 심사자 보정, revisar artículo, revisión entre pares, revisión de manuscrito, informe de árbitro, revisa mi artículo, criticar artículo, simular revisión, revisión editorial, calibrar revisor.

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

Prepares evidence-bounded, constructive peer-review drafts and structured manuscript assessments. Supports authorized review of scientific manuscripts, protocols, preprints, or research proposals; reporting-guideline selection; claim–evidence checks; methods, statistics, reproducibility, ethics, figure/table, and citation critique; or revision-response planning.

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

Evaluates scientific claims and evidence quality. Applies to experimental design validity, biases and confounders, statistical interpretation, evidence grading frameworks (GRADE, Cochrane Risk of Bias), and teaching critical analysis. Supports evidence appraisal and identifying flaws; formal peer review writing belongs to peer-review.

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