'verified' 검색 결과

Check academic references for existence, accurate publication details, and support for cited claims. Provides a writing-time verification workflow using WebSearch and Google Scholar, including BibTeX retrieval and clear handling of references that cannot be verified.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking references suggested by AI
• Matching authors, titles, years, and publication venues
• Confirming that a paper supports a cited claim

Create a repository-specific verification skill and a comprehensive feature map for an app. It documents launch, UI, CLI, and API checks, then runs the instructions to capture evidence and distinguish verified features from untested or blocked ones.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Create verification instructions for agents new to a repository
• Map app features and their observable success conditions
• Prove a real user journey and preserve evidence

Read 小红书 / RedNote posts from shared links and summarize captions separately from information inside images. Check the post's identity and image order, then report sources, reading coverage, and claims that remain unverified.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Summarizing a post from a shared link
• Reading image notes in their original order
• Understanding tables and formulas inside images

Read WeChat Official Account articles through available web or browser tools. Summarize the content actually accessed, check article details and relevant images, and clearly report reading limits, verification barriers, and claims that remain unverified.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Summarize a WeChat article from its link
• Check the title, author, and publication date
• Inspect key images alongside the article

Manage a project's stored materials through inventory, migration, archiving, and ranking based on verified source reads. Changes follow owner approval, preserve material references, and include validation records and rollback procedures.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Inventory stored materials before migration
• Rank reading candidates using verified sources
• Archive materials while preserving references

Carry out technical plans in verified stages, with automated checks followed by human review. The skill defines task delegation, progress tracking, and persistent handoff records so work can resume with the context needed for the next task.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Implementing a technical plan in verified stages
• Assigning separate agents to sequential tasks
• Resuming work from saved handoff records

Contribute a verified bug fix for LazyCodex, lazycodex-ai, omo-codex, bundled Codex skills, or upstream Codex CLI bugs. Opens a fork PR only for upstream openai/codex; LazyCodex-owned defects become a verified-fix issue on code-yeongyu/lazycodex (never a PR — that repo is a generated distribution mirror). Use when the user asks to fix a bug, contribute a bug fix, contribute to fix bug, open a PR for a bug, or debug and PR a LazyCodex/Codex defect.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

[omh] Agent instruction file for a repo -- AGENTS.md, CLAUDE.md, a Cursor rule: write or update what an agent cannot derive from the code, inside a marked region, with every command verified or marked unverified and no counts that drift. Use when the user says: agent-instructions, agents.md, claude.md, gemini.md, copilot-instructions.md, .cursorrules, cursor rules, cursor rule.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Bring a project's formal verification back in line with the code after the code changes: find the commits that touched verified code, update the model, harness, or properties to describe the code as it is now, rerun, and say whether each failure is drift in the verification or a bug in the code. Use for /maintain-formal-verification-skill, "is the model still true to the code", or after merges and refactors that touched verified code without rechecking it.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Verify statistics and claims in blog posts by fetching cited source URLs and checking if the claimed data actually appears on the page. Extracts all load-bearing claims (statistics, product or policy claims, ranking and comparative claims, named sources), validates cited URLs before fetching, and scores match confidence (exact match 1.0, paraphrase 0.7-0.9, not found 0.0). Flags uncited claims as UNVERIFIED and marks a claim verified only when this run fetched the source and found the passage. Checks that a source says what the post says it says; it cannot prove the source is true or verify first-hand experience. Use when the user says "fact check", "verify statistics", "check sources", "factcheck". Report only; not for rewriting posts (blog-rewrite).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Bring a project's formal verification back in line with the code after the code changes: find the commits that touched verified code, update the model, harness, or properties to describe the code as it is now, rerun, and say whether each failure is drift in the verification or a bug in the code. Use for /maintain-formal-verification-skill, "is the model still true to the code", or after merges and refactors that touched verified code without rechecking it.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Adversarial verification of finished work. Treats any "done" as a set of claims, then re-runs the claimed verifications, diffs what actually changed, detects weakened tests and false completion claims, and delivers an evidence-based verdict (VERIFIED / VERIFIED WITH CAVEATS / REFUTED). Use after any agent or model claims work is complete - "/fable-judge", "judge this work", "verify what it did", "did that actually work?". Also runs the fable-method trap suite against a skill or model via "/fable-judge suite TARGET".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Matches a user’s biomedical research direction, disease problem, study aim, data modality, and resource constraints to the most relevant recent algorithms and method papers. Always search real recent algorithm literature first, prioritize the last 12 months, expand to 1–3 years only when needed, and add canonical baselines only when necessary. Every formal algorithm recommendation must include the verified primary method paper, plus published downstream papers that actually cite/use the algorithm when such papers are found, with DOI when available. Never fabricate papers, algorithm names, authors, journals, years, DOI, PMID, links, or benchmark claims. If no directly verified algorithm paper is found, say so explicitly.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generates audit-grade, hallucination-free documentation from codebase features with full traceability. Use when documenting features, creating technical specs, or generating verified documentation with code references.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Azure Verified Modules (AVM) requirements and best practices for developing certified Azure Terraform modules. Use when creating or reviewing Azure modules that need AVM certification.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Decides which named technologies a company actually runs on its website, verified against the live site. Triggers on "find companies using Shopify", "they're on HubSpot", "tech stack targeting", "technographics", "who uses Klaviyo", "companies running WordPress". Outputs a per-domain verdict (tech_confirmed plus the verified stack and its evidence); the copy-ready clause is OFF by default and runs only when the operator asks for one.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Verify a claim with fresh local evidence: restate it falsifiably, capture baseline and treatment, compare artifacts, and return VERIFIED, NOT VERIFIED, or INCONCLUSIVE.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

🇺🇸 Hardware + SaaS GTM Playbook — End-to-end go-to-market for consumer hardware products with software subscription models. Covers crowdfunding engineering (Kickstarter/Indiegogo/Makuake), KOL matrix for physical products, hardware PMF validation metrics, device-as-funnel subscription design, localization entry timing, and community flywheel mechanics. Built from verified Plaud, Insta360, and DJI case data. 🇨🇳 硬件+软件订阅 GTM 实操手册 — 面向消费硬件产品的完整出海及增长打法。覆盖众筹超额工程（KS/IGG/Makuake）、硬件 KOL 矩阵策略、硬件 PMF 验证、设备即漏斗订阅设计、本地化进入时机判断、社区飞轮构建。基于 Plaud/Insta360/大疆真实案例数据撰写。 🇯🇵 ハードウェア＋SaaS GTMプレイブック — クラウドファンディング（Kickstarter/IGG/Makuake）を起点とした消費者向けハードウェア製品のGTM戦略。KOLマトリクス、PMF検証、デバイスをファネルとするサブスクリプション設計、ローカライゼーション進入タイミング、コミュニティフライホイールまで網羅。Plaud・Insta360・DJIの実例データに基づく。 🇰🇷 하드웨어+SaaS GTM 플레이북 — 크라우드펀딩(Kickstarter/IGG/Makuake) 기반 소비자 하드웨어 제품의 엔드투엔드 GTM 전략. KOL 매트릭스, PMF 검증, 디바이스-as-퍼널 구독 설계, 현지화 진입 타이밍, 커뮤니티 플라이휠 포함. Plaud·Insta360·DJI 실제 사례 데이터 기반. Triggers: "hardware GTM" | "crowdfunding strategy" | "hardware+SaaS" | "Kickstarter launch" | "hardware KOL" | "hardware PMF" | "device subscription" | "hardware product launch" | "consumer hardware growth" | "Makuake" | "众筹策略" | "硬件出海" | "硬件+订阅" | "硬件GTM" | "KS众筹" | "硬件PMF" | "设备订阅" | "硬件冷启动" | "ハードウェアGTM" | "クラファン" | "하드웨어 GTM" | "크라우드펀딩"

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

カスタムクレーム（Custom Claims）機能の開発・修正を行う際に使用。claims: scopeマッピング、verified_claims: マッピング実装時に役立つ。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Research a specific technology, library, system, protocol, or tool to answer a concrete technical question with source-traceable evidence. Use when current implementation details, version behavior, configuration, compatibility, or authoritative technical facts must be verified rather than recalled. Also use when explicitly asked to incorporate verified findings into an existing skill.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Verify multiple factual claims in backlog items, skill documentation, or plugin content. Extracts discrete claims, delegates each to the canonical factual-verification process, and aggregates VERIFIED/REFUTED/INCONCLUSIVE results. Use for "fact check", "verify claims", or a set of unverified factual assertions.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Verifies claims in backlog items, skill documentation, or plugin content against primary sources using web lookups. Spawns parallel verification agents that must use WebFetch/WebSearch/gh — training data recall is explicitly rejected as evidence. Produces VERIFIED/REFUTED/INCONCLUSIVE verdicts with citations. Use when items are marked UNVERIFIED or when verifying tool API claims, CLI flags, or documented software behavior.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when a verified non-trivial fix lands or existing solution docs need refresh. Not for unverified fixes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Close out a review/meta branch that lands an evidence-ingest / curation batch: create the named nodes, ingest verified evidence, appraise Trust Magnitude, calibrate stars, wire suites, correct upstream naming, stage ONLY the intended artifacts (dropping CRLF churn and blocking leaks), validate, and open the PR. Use when a curation/ingest batch is verified and ready to land, or when the user says "close the review/meta branch", "land the ingest batch", "wrap up the intake PR", "/gaia-review-meta-close". Wraps the deterministic hygiene in scripts/review_meta_close.py and gates the judgment calls (calibration, Origin, suite promotion, naming, merge) behind explicit human checkpoints.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.