「claim」の検索結果

List OKX Agentic Wallet exclusive trading competitions, register users for contests, track participation and leaderboard rankings, and claim won rewards. Use when users want to list available trading competitions or trading cups, view competition rules / prize pool / total prizes, register or sign up or enroll or join a contest, check the leaderboard (who is winning) or their own rank (am I in the prize zone, what is my place), ask did I win or query participation / claim status, claim won rewards or prizes from completed competitions, see which wallet account they registered with, or submit Telegram / WeChat / Email / Twitter contact for prize delivery to top-tier winners.

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

This skill should be used when the user asks to "review paper quality", "check paper completeness", "validate paper structure", "self-review before submission", "audit claims", "check overclaiming", "verify whether results support claims", or mentions systematic paper quality checking. Provides comprehensive quality assurance checklist for academic papers.

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

Examine what a file claims about itself and what it actually contains — powered by Apache Tika. True content-based type detection (extensions lie), provenance claims (authors, dates, creating application), revision and tamper signals (PDF incremental updates, tracked changes, hidden slides, zip integrity), hidden and embedded content (attachments, macros), risk indicators (PDF JavaScript actions, encryption), and content digests. Evidence gathering, not verdicts: Tika reports what the file asserts and what parsing observed; it does not attribute authorship or validate signatures. Use for triaging suspicious files, provenance questions, e-discovery-style review, or "is this file what it claims to be."

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

Use when the user asks to "map the category narrative", "tear down how competitors tell their story", or "find the language conventions in our market"; produces a category narrative map — the dominant stories and points of view in the category, its language conventions and framing clichés, and a per-competitor narrative teardown (arc, claimed onlyness, proof pattern) plus how each rival's messaging has shifted over time (scraped copy vs archived copy). Not for the positioning canvas itself — use positioning-mapper; not for the beachhead's beliefs and objections — use audience-belief-mapper; not for SERP keyword targeting — use keyword-research; not for claim adjudication — use offer-claims-registry. 品类叙事/竞争叙事拆解/语言惯例/叙事演变

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

Use when the user asks to "design our change narrative", "build the old-world-to-new-game story arc", or "frame the shift our category is undergoing"; produces a Raskin-style strategic narrative arc — old world → the undeniable shift → winners vs losers under the new rules → the promised land → proof the promised land is real — derived from the positioning truth set and the belief/objection map, feeding the TALE Architecture arc sub-item. Every proof beat is labeled Measured / User-provided / [needs source] and this skill never adjudicates a claim. Not for the message house hierarchy — use message-system-architect; not for the pitch deck narrative — use pitch-narrative-builder; not for claim substantiation — use offer-claims-registry. 变革叙事弧/旧世界/应许之地/战略叙事结构

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

Use when the user asks to "plan how our narrative lands on every surface", "write per-surface message-match specs", or "brief each creative builder from the canon"; maps the narrative-registry canon onto every flagship surface (homepage, pricing, store listing, sales deck, social bio, docs, email) as a per-surface message-match spec — what claim, pillar, proof, and objection reframe each surface must carry — and cuts a handoff brief to each discipline's creative builder (content-writer, ad-creative-builder, email-creative-builder, social-creative-builder, message-house-builder), so the same story lands consistently everywhere. Not for writing the finished surface copy — use each discipline creative builder; not for the tier-scoped launch asset manifest — use launch-asset-packager; not for scoring cross-surface consistency — use narrative-quality-auditor; not for claim adjudication — use offer-claims-registry. 叙事落地/逐面消息一致/创意交接简报/画布传导

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

Use when receiving code review feedback (especially if unclear or technically questionable), when completing tasks or major features requiring review before proceeding, or before making any completion/success claims. Covers three practices - receiving feedback with technical rigor over performative agreement, requesting reviews via code-reviewer subagent, and verification gates requiring evidence before any status claims. Essential for subagent-driven development, pull requests, and preventing false completion claims.

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

Assesses whether study results are trustworthy by auditing design integrity, sample structure, statistical handling, bias control, validation chain, and claim discipline. It identifies where results are robust, fragile, overfit, under-validated, or overclaimed. Always separate reported findings from reliability judgment. Never fabricate references, PMIDs, DOIs, trial identifiers, study features, or validation claims.

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

Extract factual claims from PR copy, verify each claim independently, attach concrete citations, and warn when certainty is low. Runs each claim through proven newsroom verification methods (lateral reading, source-tier climbing, provenance pillars, triangulation, calibrated rating) and puts the burden of proof on the speaker. Use before a pitch, press release, reactive comment, DM, or other journalist-facing draft is trusted or sent.

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

Decode an insurance claim denial letter — what the cited reason actually means, whether it's commonly overturnable, and the appeal letter that answers it point by point. Use when someone asks 'my insurance claim was denied what do I do', 'decode this denial letter', 'can I appeal this denial', or 'write my insurance appeal'. Produces the denial decode with overturn-likelihood framing, the evidence checklist, the point-by-point appeal letter, and the escalation ladder past the insurer.

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

Work out whether you're eligible for a class-action settlement or refund program — and actually file the claim before the deadline. Use when asked am I owed money from a settlement, is there a class action for [product/company], how do I claim a settlement, or did I qualify for that refund. Produces a way to check for relevant settlements, an eligibility read against the class definition, the proof you need and how to file, deadline tracking, and honest expectations on payout size — plus how to avoid fake-settlement scams. Not legal advice.

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

Render a designed 'value prop' video from a config — 3-5 noun-phrase benefit claims (<=4 words each) revealed sequentially over per-SKU product visuals, one crisp editorial frame per claim (hook sticker -> N claim beats -> brand end card). Deterministic PIL/HTML beat renderer frame-stepped via Playwright and encoded with FFmpeg, sound-off legible, hard cuts, uniform pacing. FREE (no paid calls); music is added separately (create-music-elevenlabs). Use for the value-prop format.

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

Critically assess and improve a legal scholarly thesis, article idea, student note, seminar-paper claim, or research agenda using Eugene Volokh's novelty, nonobviousness, utility, and soundness framework, connector-aware research, claim-specific tests, and a sustainable adversarial pass. Produces a self-contained green-, yellow-, or red-light report. Use when a law professor or law student asks whether a claim is viable, novel, publishable, preempted, useful, worth pursuing, or better than competing topics; or wants a thesis stress-tested, narrowed, repaired, or compared. No connector is required: use connected legal and scholarly research when available, public sources otherwise, and disclose any no-research fallback.

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

Post-hoc verification and trust audit of AI-generated factual and interpretive claims. Classifies claims by type and salience, routes them to domain-appropriate sources, scores trustworthiness on a tiered scale with an Interpolated verdict for plausible-but-unsupported detail, and assesses rhetorical fairness on interpretive claims. Designed for clinical-negligence and healthcare-law practice in England and Wales, with general applicability beyond.

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

Writes the formal letter you send before suing someone in a civil case in England & Wales — the Letter Before Claim that starts the pre-action clock. The part it gets right is which pre-action protocol applies — debt, professional negligence, housing disrepair, personal injury, or the default Practice Direction on Pre-Action Conduct — each of which has its own rules a generic letter misses (the 30-day debt window, the professional-negligence preliminary-notice step). It also flags the limitation deadline for a solicitor to confirm rather than stating it as fact. Built for litigation juniors, in-house counsel, and small firms without a precedent to copy. Use when the user says 'draft an LBC', 'letter before claim', 'pre-action letter', 'pre-action protocol', or needs to start the pre-action clock before issuing a civil claim. Verify the current protocol before sending.

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

Rewrite `outline/claim_evidence_matrix.md` as a projection/index of evidence packs (NO PROSE), so claims/axes are driven by `outline/evidence_drafts.jsonl` rather than outline placeholders.

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

Use when `paper-review` needs a claim-by-claim evidence gap report grounded in an extracted claim ledger.

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

Seed `outline/claim_evidence_matrix.md` from outline+notes; claim-matrix-rewriter rewrites it later from evidence packs.

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

Screen a Medicare/Medicaid claims corpus for fraud, waste, and abuse and produce ranked, fully-cited investigation referrals for an SIU / program-integrity team. Use when asked to run a fraud sweep, screen claims for FWA, find billing anomalies, or generate investigation referrals over a claims dataset.

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

Use when about to claim a result, effect, significance, or that an analysis reproduces, before reporting or writing it up - requires running the analysis fresh and reading the actual output first; evidence before claims always

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

Document construction claims for disputes and recovery. Compile evidence, calculate damages, track notice requirements, and prepare claim packages.

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

Citation-integrity forensics: is every reference real, correctly attributed, and used in a context the cited work actually supports? Catches hallucinated references (no paper at the claimed arXiv id/DOI/venue, fabricated authors/year), metadata drift (wrong year/venue/version), and wrong-context citations (a real paper cited for a claim it never makes — or argues against). A hot zone for machine-generated papers. Decidable at L0 (text + canonical sources). Span-anchored to the evidence ledger (claims.json); the executor gathers canonical facts (DBLP / arXiv / DOI), then one FRESH cross-model thread per cited key proposes findings; reviewer != adjudicator. Emits citation-forensics.findings.json; NEVER computes the verdict. Triggers: "citation forensics", "check the references", "hallucinated citations", "wrong-context citation", "verify references", "引用核对".

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

Check that a document's claims about code are actually true by reading the prose, the code, and the tests and reporting (or fixing) where they disagree. Use whenever the user wants to verify a README, guide, spec, or docstring still matches the code; whenever they mention documentation drift, doc-code sync, "is this still accurate", stale docs, or keeping docs/tests/code consistent; before publishing or merging a docs change; or as a periodic doc-accuracy sweep. The agent reads the prose's meaning directly — there is no claim-comment DSL to maintain. Pairs with TDD — the test suite is the deterministic behavioral gate, this skill is the semantic prose-vs-reality review.

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

Use when receiving code review feedback (especially if unclear or technically questionable), when completing tasks or major features requiring review before proceeding, or before making any completion/success claims. Covers three practices - receiving feedback with technical rigor over performative agreement, requesting reviews via code-reviewer subagent, and verification gates requiring evidence before any status claims. Essential for subagent-driven development, pull requests, and preventing false completion claims.

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