Split meta skill CLI and review gates

Merge the beta-ready Yao Meta Skill architecture, report, evidence gate, and release-boundary updates.\n\nRelease boundary: beta/public testing is allowed; formal world-class, fully reviewed, or superiority claims remain blocked until the pending evidence gates are accepted.

Author: yaojingang

.gitignore

@@ -3,6 +3,7 @@ dist/
 *.zip
 __pycache__/
 tests/tmp/
+tests/tmp_*/
 tests/tmp_snapshot/
 tests/tmp_cli/
 tests/tmp_skill_overview/
@@ -23,9 +24,12 @@ tests/tmp_baseline_compare.*
 reports/release_snapshots/
 reports/telemetry_events.jsonl
 .yao/
+evidence/world_class/submission-kit/
+evidence/world_class/submissions/
 
 # Local business-skill experiments belong outside this meta-skill repo unless promoted intentionally.
 geo-ranking-article-generator/
 
 # Private or one-off pattern analysis reports should not be committed as factory evidence.
 reports/*pattern-analysis*.md
+reports/*research-plan*.md

.previews/yao-meta-skill-v2-report-demo/geo-content-brief-skill/README.md

@@ -0,0 +1,72 @@
+# Geo Content Brief Skill
+
+## What It Does
+
+`geo-content-brief-skill` is a reusable skill package for this job:
+
+> 将 GEO 内容访谈、关键词笔记、竞品线索和渠道约束整理成可执行的中文内容简报。用于团队复用、选题规划、内容生产交接和质量评审；不用于直接代写完整长文或替代品牌策略判断。
+
+## 中文使用方式
+
+1. 输入访谈纪要、关键词、渠道限制、竞品摘要、品牌禁区或已有内容方向。
+2. 先判断请求是否属于“生成内容简报”，而不是完整长文、广告口号或品牌策略。
+3. 按 `references/brief-structure.md` 输出一页中文简报。
+4. 用 `references/review-checklist.md` 检查事实、结构、证据、风险和下一步动作。
+5. 用 `evals/trigger_cases.jsonl` 和 `evals/output_cases.jsonl` 做轻量回归。
+
+## How To Use
+
+1. Load the skill through `SKILL.md`.
+2. Start with `reports/intent-dialogue.md` to tighten the real job, outputs, exclusions, and the standards you care about.
+3. Open `reports/reference-scan.md` to capture external benchmarks and any user-supplied references worth learning from.
+4. Review `reports/intent-confidence.md` to see whether the real job, inputs, outputs, and exclusions are clear enough yet.
+5. Open `reports/reference-synthesis.md` to see the GitHub benchmarks plus curated official, research, and principle tracks in one place.
+6. Follow the workflow steps in `SKILL.md`.
+7. Check `reports/skill-overview.html` for the generated bilingual HTML skill audit report: overview, metrics, capability profile, principle, contract, quality, risk, assets, and iteration roadmap. It defaults to Simplified Chinese and includes an English switch in the top right.
+8. Open `reports/review-studio.html` for the one-page Review Studio 2.0 gate view.
+9. Record source-line reviewer comments in `reports/review_annotations.md` when review needs follow-up.
+10. Open `reports/review-viewer.html` for a compact visual review of the package.
+11. Check `reports/output-risk-profile.md` to see likely output mistakes and self-repair checks.
+12. Check `reports/artifact-design-profile.md` to see the intended artifact direction, layout patterns, visual quality gates, and anti-patterns.
+13. Check `reports/prompt-quality-profile.md` to see the need model, RTF-to-skill mapping, complexity, and prompt-facing quality matrix.
+14. Review `reports/skill-ir.json` for the platform-neutral Skill IR contract before platform-specific packaging.
+15. Review `reports/compiled_targets.md` to see how Skill IR compiles into OpenAI, Claude, generic, and Agent Skills compatible target contracts.
+16. Review `reports/iteration-directions.md` for the three most valuable next moves.
+17. Review `reports/system-model.md` to understand the boundary, feedback loops, drift watch, failure map, and highest-leverage next changes.
+18. Review `reports/adoption_drift_report.md` to see local-first metadata-only adoption and drift signals.
+19. Review `reports/review_waivers.md` to see human reviewer risk approvals and expiry dates.
+
+## Honest Boundaries
+
+- This package starts from the current intent frame and should not pretend to cover unclear adjacent jobs.
+- The first version should ask for clarification when the real input, output, or exclusion boundary is still fuzzy.
+- New structure should be added only when it earns its keep through evidence, validation, or reviewer need.
+- It should not fabricate search volume, competitor rankings, customer quotes, or third-party evidence.
+
+## Package Map
+
+- `SKILL.md`: trigger and workflow entrypoint
+- `agents/interface.yaml`: portable interface metadata
+- `manifest.json`: lifecycle and packaging metadata
+- `references/brief-structure.md`: 中文 GEO 内容简报结构、字段说明和质量标准
+- `references/review-checklist.md`: 交付前编辑复核清单
+- `evals/trigger_cases.jsonl`: 应触发和不应触发样例
+- `evals/output_cases.jsonl`: 输出结构验收样例
+- `reports/intent-dialogue.md`: front-loaded discovery questions for better boundary design and clearer human alignment
+- `reports/intent-confidence.md`: current clarity score, open gaps, and the next follow-up questions worth asking
+- `reports/github-benchmark-scan.md`: top public benchmark repositories, extracted patterns, and borrow or avoid notes
+- `reports/reference-scan.md`: benchmark notes from public references, user references, and local constraints
+- `reports/reference-synthesis.md`: a combined view of GitHub benchmarks plus curated world-class pattern tracks
+- `reports/output-risk-profile.md`: predicted output failure modes and self-repair constraints for this skill
+- `reports/artifact-design-profile.md`: artifact-specific design direction, layout patterns, visual quality gates, and anti-patterns
+- `reports/prompt-quality-profile.md`: prompt-facing need model, RTF mapping, complexity, and quality matrix
+- `reports/system-model.md`: systems-thinking model for boundary, feedback loops, drift, failure patterns, and leverage points
+- `reports/skill-ir.json`: platform-neutral 2.0 Skill IR contract for trigger, workflow, resources, evals, risk, and governance
+- `reports/compiled_targets.md`: target compiler report showing generated contracts, adapter modes, preserved semantics, warnings, and unsupported features
+- `reports/skill-overview.html`: white-background bilingual HTML skill audit report with sticky four-character Chinese navigation, a top-right language switch, metrics, SVG charts, contract boundary, quality review, risk governance, assets, and iteration roadmap
+- `reports/review-studio.html`: Review Studio 2.0 gate page for intent, trigger, output eval, context, runtime conformance, trust, atlas, and release readiness
+- `reports/review-viewer.html`: compact review page for architecture, usage, feedback, and next steps
+- `reports/iteration-directions.md`: the top three next iteration directions
+- `reports/adoption_drift_report.md`: local-first metadata-only telemetry summary for adoption, missed triggers, bad outputs, script errors, and review drift
+- `reports/review_waivers.md`: human reviewer risk approval ledger for warning acceptance and expiry
+- `reports/review_annotations.md`: source-line reviewer comments linked to Review Studio gates

.previews/yao-meta-skill-v2-report-demo/geo-content-brief-skill/SKILL.md

@@ -0,0 +1,57 @@
+---
+name: geo-content-brief-skill
+description: "将 GEO 内容访谈、关键词笔记、竞品线索和渠道约束整理成可执行的中文内容简报。用于团队复用、选题规划、内容生产交接和质量评审；不用于直接代写完整长文或替代品牌策略判断。"
+---
+
+# Geo Content Brief Skill
+
+## When To Use This Skill
+
+- 用户提供访谈纪要、关键词、竞品片段、产品卖点或渠道限制，希望沉淀为中文内容简报。
+- 团队需要把零散输入转换成可执行的 GEO 内容选题、角度、结构、证据和交付要求。
+- 需要先明确触发边界、输入缺口和输出验收标准，再进入内容生产。
+
+## Workflow
+
+1. 读取用户输入，识别目标受众、内容渠道、关键词、品牌边界、禁止表达和必须覆盖的信息。
+2. 对照 `references/brief-structure.md` 生成简报骨架：目标、洞察、角度、关键词、结构、证据、风险和验收标准。
+3. 如果缺少核心输入，先提出最多三个澄清问题，不用假设补全用户没有提供的事实。
+4. 用 `evals/trigger_cases.jsonl` 检查当前请求是否属于 GEO 内容简报场景。
+5. 用 `evals/output_cases.jsonl` 检查输出是否包含输入摘要、内容结构、证据要求、禁区和下一步动作。
+6. 交付前回看渠道限制和品牌禁区，删除空泛营销话术、无来源断言和不可执行建议。
+
+## Inputs
+
+- 访谈纪要、销售反馈、客户问题或专家观点。
+- 关键词、搜索意图、竞品页面摘要或排名线索。
+- 目标渠道、目标读者、品牌口径、禁用词和交付格式。
+
+## Outputs
+
+- 一页中文内容简报，包含目标、受众、核心洞察、推荐角度、文章结构、关键词布置、证据需求和风险提示。
+- 缺口清单，说明继续生产前必须补齐的信息。
+- 下一步动作，面向写作者、编辑或 SEO/GEO 负责人。
+
+## Output Quality Guardrails
+
+- Before final output, apply the likely failure modes in `reports/output-risk-profile.md` when that report is present.
+- Before rendering reports, tutorials, review pages, dashboards, or visual artifacts, apply the artifact direction and visual quality gates in `reports/artifact-design-profile.md` when that report is present.
+- When prompt behavior, role design, dialogue quality, or output contracts matter, apply `reports/prompt-quality-profile.md` when that report is present.
+- Before adding more structure, apply the boundary, feedback-loop, drift, and leverage-point checks in `reports/system-model.md` when that report is present.
+- Repair generic headings, cluttered notes, fragile visual assumptions, weak tables, and missing verification cues before handing work back.
+- Map role, task, and format into skill behavior rather than copying a large prompt template into `SKILL.md`.
+- Let the artifact's content choose the visual system; do not copy a fixed palette or report style from another skill without a clear reason.
+- If output-specific evidence is missing, state the gap instead of inventing screenshots, citations, data, or examples.
+
+## Honest Boundaries
+
+- 不直接代写完整长文，不替代品牌策略判断，不伪造竞品数据、搜索量、排名或引用来源。
+- 当用户只想要标题灵感、广告文案、舆情分析或完整文章撰写时，不应触发本 Skill。
+- 缺少目标读者、渠道或关键词时，先收紧输入，再输出简报。
+
+## Reference Map
+
+- `references/brief-structure.md`: 中文 GEO 内容简报结构、字段说明和质量标准。
+- `references/review-checklist.md`: 交付前的编辑复核清单。
+- `evals/trigger_cases.jsonl`: 应触发和不应触发样例。
+- `evals/output_cases.jsonl`: 输出结构验收样例。

.previews/yao-meta-skill-v2-report-demo/geo-content-brief-skill/agents/interface.yaml

@@ -0,0 +1,29 @@
+interface:
+  display_name: "Geo Content Brief Skill"
+  short_description: "将 GEO 内容访谈、关键词笔记、竞品线索和渠道约束整理成可执行的中文内容简报。"
+  default_prompt: "当你需要把访谈纪要、关键词、竞品线索和渠道限制整理成中文 GEO 内容简报时，使用 $geo-content-brief-skill。"
+compatibility:
+  canonical_format: "agent-skills"
+  adapter_targets:
+    - "openai"
+    - "claude"
+    - "generic"
+    - "vscode"
+  activation:
+    mode: "manual"
+    paths:
+      - "SKILL.md"
+      - "references/brief-structure.md"
+      - "evals/trigger_cases.jsonl"
+  execution:
+    context: "inline"
+    shell: "bash"
+  trust:
+    source_tier: "local"
+    remote_inline_execution: "forbid"
+    remote_metadata_policy: "allow-metadata-only"
+  degradation:
+    openai: "metadata-adapter"
+    claude: "neutral-source-plus-adapter"
+    generic: "neutral-source"
+    vscode: "agent-skills-source-with-vscode-notes"

.previews/yao-meta-skill-v2-report-demo/geo-content-brief-skill/evals/output_cases.jsonl

@@ -0,0 +1,2 @@
+{"id":"brief_minimum_contract","input":"访谈纪要、关键词、渠道、品牌禁区","must_include":["输入摘要","目标读者","搜索意图","内容角度","结构建议","证据需求","风险禁区","下一步动作"],"must_not_include":["虚构搜索量","无来源竞品排名","完整长文正文"]}
+{"id":"missing_evidence_behavior","input":"只有关键词，没有访谈、渠道和品牌限制","must_include":["缺口清单","最多三个澄清问题","待补充证据"],"must_not_include":["假设用户品牌口径","编造客户原话"]}

.previews/yao-meta-skill-v2-report-demo/geo-content-brief-skill/evals/trigger_cases.jsonl

@@ -0,0 +1,4 @@
+{"id":"should_geo_interview_notes","input":"这里有一段客户访谈和 8 个 GEO 关键词，帮我整理成一份中文内容简报，给写作者用。","expected":"trigger","reason":"用户明确要把访谈和关键词整理为内容简报。"}
+{"id":"should_competitor_brief","input":"把这些竞品页面摘要、品牌禁区和知乎渠道限制整理成一页选题简报。","expected":"trigger","reason":"输入包含竞品、品牌边界和渠道约束，输出是一页简报。"}
+{"id":"should_not_full_article","input":"根据这些关键词直接帮我写一篇 3000 字完整文章。","expected":"no_trigger","reason":"用户要完整长文写作，不是生成内容简报。"}
+{"id":"should_not_ad_copy","input":"给这个活动想 20 条广告口号，越短越好。","expected":"no_trigger","reason":"广告口号生成不属于 GEO 内容简报。"}

.previews/yao-meta-skill-v2-report-demo/geo-content-brief-skill/manifest.json

@@ -0,0 +1,24 @@
+{
+  "name": "geo-content-brief-skill",
+  "version": "0.1.0",
+  "owner": "Yao Team",
+  "updated_at": "2026-06-15",
+  "status": "active",
+  "maturity_tier": "production",
+  "lifecycle_stage": "production-preview",
+  "context_budget_tier": "production",
+  "review_cadence": "per-release",
+  "skill_archetype": "production",
+  "target_platforms": [
+    "openai",
+    "claude",
+    "generic",
+    "agent-skills-compatible",
+    "vscode"
+  ],
+  "factory_components": [
+    "references",
+    "scripts",
+    "reports"
+  ]
+}

.previews/yao-meta-skill-v2-report-demo/geo-content-brief-skill/references/brief-structure.md

@@ -0,0 +1,23 @@
+# GEO 内容简报结构
+
+## 目标
+
+把零散材料整理成写作者可以直接执行的一页内容简报。简报应帮助团队快速判断：写给谁、解决什么问题、采用什么角度、需要哪些证据、哪些话不能说。
+
+## 推荐字段
+
+- 项目背景：产品、业务目标、目标渠道和期望交付物。
+- 目标读者：读者身份、已知问题、决策阶段和内容理解门槛。
+- 搜索意图：核心关键词、近义词、长尾问题和需要避开的无关意图。
+- 内容角度：建议主张、差异化角度、可引用观点和与竞品的区分点。
+- 结构建议：标题方向、章节顺序、每节回答的问题和必要证据。
+- 证据需求：内部数据、案例、截图、第三方来源、专家观点或客户原话。
+- 风险禁区：禁止承诺、敏感表述、未证实数据、品牌不采用的语气。
+- 验收标准：完成后需要检查的结构、事实、语气、关键词和行动建议。
+
+## 质量标准
+
+- 每个推荐角度都应能追溯到输入材料或明确标记为待验证假设。
+- 缺少事实证据时写“待补充证据”，不要编造来源。
+- 输出要服务内容生产交接，避免泛泛的市场建议。
+- 中文表达要具体、可执行、便于编辑继续拆稿。

.previews/yao-meta-skill-v2-report-demo/geo-content-brief-skill/references/review-checklist.md

@@ -0,0 +1,11 @@
+# 内容简报复核清单
+
+交付前按以下顺序检查：
+
+1. 输入摘要是否覆盖访谈、关键词、渠道限制和品牌禁区。
+2. 目标读者是否具体到角色、问题和决策阶段。
+3. 推荐角度是否能从输入材料中找到依据。
+4. 文章结构是否能直接分配给写作者执行。
+5. 证据需求是否列出已拥有证据和待补证据。
+6. 风险提示是否包含禁用表达、未证实数据和不应承诺的结果。
+7. 下一步动作是否明确谁继续补材料、谁写稿、谁审核。

.previews/yao-meta-skill-v2-report-demo/geo-content-brief-skill/reports/adoption_drift_report.json

@@ -0,0 +1,62 @@
+{
+  "ok": true,
+  "schema_version": "2.0",
+  "generated_at": "2026-06-15T09:03:27Z",
+  "skill_dir": ".previews/yao-meta-skill-v2-report-demo/geo-content-brief-skill",
+  "privacy_contract": {
+    "storage": "local-first",
+    "event_scope": "metadata-only",
+    "raw_content_allowed": false,
+    "raw_event_log_packaged": false,
+    "blocked_fields": [
+      "content",
+      "input",
+      "inputs",
+      "message",
+      "messages",
+      "note",
+      "output",
+      "outputs",
+      "prompt",
+      "raw",
+      "text",
+      "transcript"
+    ]
+  },
+  "summary": {
+    "event_count": 0,
+    "adoption_sample_count": 0,
+    "activation_count": 0,
+    "accepted_count": 0,
+    "edited_count": 0,
+    "rejected_count": 0,
+    "missed_count": 0,
+    "failed_count": 0,
+    "adoption_rate": 0,
+    "missed_trigger_count": 0,
+    "wrong_trigger_count": 0,
+    "bad_output_count": 0,
+    "script_error_count": 0,
+    "missing_resource_count": 0,
+    "review_overdue_count": 0,
+    "risk_band": "no-data",
+    "event_types": {},
+    "failure_types": {},
+    "source_types": {},
+    "command_counts": {}
+  },
+  "adoption_by_skill": [],
+  "next_iteration_candidates": [
+    {
+      "signal": "no telemetry",
+      "recommendation": "Start with a small metadata-only sample before using telemetry for release decisions."
+    }
+  ],
+  "recent_events": [],
+  "failures": [],
+  "artifacts": {
+    "events_jsonl": ".previews/yao-meta-skill-v2-report-demo/geo-content-brief-skill/reports/telemetry_events.jsonl",
+    "json": ".previews/yao-meta-skill-v2-report-demo/geo-content-brief-skill/reports/adoption_drift_report.json",
+    "markdown": ".previews/yao-meta-skill-v2-report-demo/geo-content-brief-skill/reports/adoption_drift_report.md"
+  }
+}