opencode-skills-collection 4.0.68 → 4.0.70

package/bundled-skills/expo-animation/SKILL.md

@@ -0,0 +1,295 @@
+---
+description: Curated upstream guidance for Expo Animation; use when the workflow matches the user goal.
+name: expo-animation
+version: 1.0.0
+license: MIT
+source_repo: expo/skills
+source_type: official
+source: expo
+date_added: '2026-09-21'
+risk: unknown
+---
+## When to Use
+- Use when this upstream workflow matches the user's stated goal.
+- Use when the task requires the procedures documented in this skill.
+
+# Building Animations in Expo
+
+This skill was created in collaboration with [Emil Kowalski](https://github.com/emilkowalski) and can also be found in the [emilkowalski/skills](https://github.com/emilkowalski/skills) repository, along with other useful animation skills.
+
+A construction skill for React Native. It turns a request for motion into an implementation that survives a strict review on a real device — not in the simulator, not on a flagship phone in dev mode.
+
+Mobile changes three things about animation, and everything in this skill follows from them:
+
+1. **There is no hover.** Every affordance the web puts in hover has to live in press, position, or nothing.
+2. **There are two runtimes.** Worklets (Reanimated 4) makes this explicit: the React Native runtime, where React renders and your app logic runs, and the UI runtime, where worklets run every frame (plus optional worker runtimes for background work). An animation that touches the RN runtime stutters the moment the app does anything else. The whole craft is keeping motion on the UI runtime.
+3. **The user's finger is on the element.** Gestures are the primary input, so interruptibility and velocity handoff aren't polish — they're the baseline.
+
+## Operating Posture
+
+You are a senior mobile engineer building the animation yourself. Make the call, state the reasoning in one line, write the code. Never present motion options as a menu.
+
+Two failure modes, and the first is worse:
+
+1. **Animating something that shouldn't animate.** The gate below exists to produce zero lines of code sometimes.
+2. **Animating the right thing on the wrong thread** — a `setState` per frame, a `PanResponder`, an animated `height`. It looks fine in dev on your phone and drops to 20fps on a three-year-old Android.
+
+## Hard Rules
+
+1. **Run the sequence in order.** Steps 1 and 2 gate everything.
+2. **Reanimated, not core `Animated`.** Core `Animated` can't be driven by a gesture without crossing the bridge, and `useNativeDriver` refuses anything but transform and opacity anyway. Reanimated worklets run on the UI thread and keep running while JS is busy.
+3. **No approximated values.** Curves and spring configs come from the tables below.
+4. **Reduced motion ships with the animation**, not as a follow-up.
+5. **Feel is judged on a release build on the slowest device you support.** Nothing else counts as verified.
+
+## The Build Sequence
+
+### 1. Should this animate at all?
+
+| Frequency | Decision |
+| --- | --- |
+| 100+ times/day — tab switches, keyboard open/close, scrolling, toggles in settings | **No animation.** Platform default or nothing. Stop here. |
+| Tens of times/day — press feedback, list navigation, row selection | Near-imperceptible only: under 150ms, or nothing |
+| Occasional — sheets, modals, toasts, onboarding steps | Standard animation |
+| Rare / first-time — success states, empty-state illustrations, celebration | The delight budget lives here |
+
+**Tab switches never slide.** Tabs are peers, not a hierarchy — sliding implies depth that isn't there, and the user pays for it dozens of times a session. `animation: 'none'`.
+
+If the request fails this gate, say so and don't write it.
+
+### 2. What is the purpose?
+
+Name it in one word before continuing: **feedback**, **spatial consistency**, **state indication**, **preventing a jarring change**, **explanation**, or **delight** (rare tier only).
+
+Can't name it? Don't build it.
+
+### 3. Pick the tool — cheapest that works
+
+Walk down; stop at the first that fits.
+
+| Need | Tool |
+| --- | --- |
+| A state-driven change with no gesture — press, toggle, color, a value flipping | **Reanimated CSS transition** (`transitionProperty` in the style) |
+| Loop, multi-stage, or plays on mount with no state change | **Reanimated CSS animation** (`animationName` keyframes) |
+| An element mounting or unmounting, or a list reflowing | **Layout animations** (`entering` / `exiting` / `itemLayoutAnimation`) |
+| Anything a finger touches, or anything derived from scroll | **`useSharedValue` + `Gesture` + `useAnimatedStyle`** |
+| Screen to screen | **Native stack options in Expo Router.** Never hand-roll this |
+| A bottom sheet that is its own screen | **`presentation: 'formSheet'`** — it's a real UISheetPresentationController, free and correct |
+| Tab bar | **`NativeTabs`** (from `expo-router/unstable-native-tabs`) — the platform's real tab bar, its behaviors and transitions included |
+| Context menu, press-and-hold preview | **`Link.Menu` / `Link.Preview`** (Expo Router, iOS-only) — native menus and peek, never rebuilt in JS |
+| Header that collapses into a large title | **`headerLargeTitleEnabled`** on the native stack (iOS-only; `headerLargeTitle` is deprecated) — not a scroll worklet |
+| Pull to refresh | **`RefreshControl`** — hand-roll only when it's a signature interaction (see the threshold recipe) |
+| UI that tracks the keyboard | **`react-native-keyboard-controller`** — the keyboard's real position, frame by frame, on the UI thread |
+| Vector illustration, celebration, empty state | **Lottie** — for illustration only, never for UI state |
+| A huge animated scene, freeform drawing | **`@shopify/react-native-skia`** — a canvas, for when the view hierarchy itself is the bottleneck |
+
+Reach for a shared value only when the value is continuous or interruptible. A press scale is a CSS transition; a drag is a shared value. Using a worklet for a two-state toggle is the mobile equivalent of installing a motion library for a fade.
+
+**Dependencies.** Install with `npx expo install <package>` — it resolves the version that matches the project's SDK, which plain `npm install` won't:
+
+| Need | Package |
+| --- | --- |
+| Animation | `react-native-reanimated` + `react-native-worklets` |
+| Gestures | `react-native-gesture-handler` |
+| Navigation, sheets, native tabs, menus | `expo-router` |
+| Haptics | `expo-haptics` |
+| Keyboard-following UI | `react-native-keyboard-controller` (needs `KeyboardProvider` at the root — see the keyboard recipe) |
+| Illustration, celebration | `lottie-react-native` |
+| Very large animated scenes, custom drawing | `@shopify/react-native-skia` |
+
+### 4. Pick the properties
+
+- **`transform` and `opacity` are free.** Everything else is a layout pass. `width`, `height`, `margin`, `padding`, `flex`, `top`, `left`, `gap` re-run Yoga on every frame for that node *and its siblings*.
+- **The one exception: an absolutely positioned element with no children** — a tab pill, a progress bar fill. It's out of flow, so nothing else re-lays-out, and animating `width` keeps the corner radius that `scaleX` would smear.
+- **Never `scale(0)`.** Start from `scale(0.9–0.97)` + `opacity: 0`. Nothing in the real world appears from nothing.
+- **`transform` is an array and order matters** — `[{ translateY }, { scale }]` scales after moving; reversed, the translate gets scaled too. Keep translate first unless you want the multiplication.
+- **Android shadows are `elevation`, and animating elevation re-renders the shadow every frame.** Animate opacity of a pre-shadowed layer instead.
+- **Never animate `BlurView` intensity.** On Android it re-renders the blur each frame. Crossfade the opacity of a static `BlurView` instead.
+- **Percentages work in `translate`** and are relative to the element's own size — `translateY('100%')` moves a sheet by its own height whatever its content.
+
+### 5. Timing or spring
+
+**If a finger was involved, use a spring.** Springs carry velocity through an interruption; timing curves restart. Everything else uses timing.
+
+Reanimated's spring takes Apple's two designer parameters directly — use this form, not mass/stiffness/damping:
+
+| Interaction | Config |
+| --- | --- |
+| Default settle, no overshoot | `{ duration: 400, dampingRatio: 1 }` |
+| Reposition / snap back after a drag | `{ duration: 400, dampingRatio: 0.8, velocity }` |
+| Sheet, drawer | `{ duration: 300, dampingRatio: 0.8, velocity }` |
+| Must not pass a hard edge | add `overshootClamping: true` |
+
+**Bounce only when the gesture carried momentum.** Overshoot on a menu that faded in feels wrong; overshoot on a card you flicked feels right.
+
+**Easing**, for everything without a finger on it:
+
+| Situation | Easing |
+| --- | --- |
+| Entering or exiting | `ease-out` |
+| Moving / morphing on screen | `ease-in-out` |
+| Constant motion (progress, marquee) | `linear` |
+| Default | `ease-out` |
+
+**Never `ease-in` on UI.** It starts slow, delaying the exact moment the user is watching. Reanimated's built-ins are as weak as CSS's — use these:
+
+```js
+import { cubicBezier, Easing } from 'react-native-reanimated';
+
+// transitionTimingFunction / animationTimingFunction
+const CSS_EASE_OUT = cubicBezier(0.23, 1, 0.32, 1);
+
+// withTiming / .easing(...)
+const EASE_OUT = Easing.bezier(0.23, 1, 0.32, 1);      // strong ease-out for UI
+const EASE_IN_OUT = Easing.bezier(0.77, 0, 0.175, 1);  // on-screen movement
+const EASE_SHEET = Easing.bezier(0.32, 0.72, 0, 1);    // iOS sheet curve
+```
+
+Reanimated 4.1.1 and 4.5.1 reject raw `'cubic-bezier(...)'` strings. CSS transitions and animations use `cubicBezier(...)`; `withTiming` and `.easing(...)` use `Easing.bezier(...)`.
+
+**Duration:**
+
+| Element | Duration |
+| --- | --- |
+| Press feedback | 100–150ms |
+| Toggle, chip, small state change | 150–200ms |
+| Sheet, modal, drawer | spring, ~300ms perceived |
+| Screen transition | the platform default — don't override it |
+
+Mobile UI animations stay under 300ms, same as web. The platform's own transitions are longer (iOS push is 350ms); match the platform for navigation, beat it everywhere else.
+
+### 6. Keep it off the JS thread
+
+This is the mobile-specific craft, and it's where most React Native motion dies.
+
+- **Never `setState` from a gesture or scroll handler.** One React render per frame is the single biggest cause of jank in RN apps. Shared value → `useAnimatedStyle`, and React never re-renders at all.
+- **Never schedule back to the RN runtime inside `onUpdate` or a scroll handler.** `scheduleOnRN(fn, ...args)` from `react-native-worklets` — the Reanimated 4 replacement for the deprecated `runOnJS(fn)(...args)` — queues an RN-runtime call, and in `onUpdate` that's 60–120× per second. It belongs in `onEnd`, or in a `useAnimatedReaction` that fires when a value crosses a threshold.
+- **Never read a shared value during render** (`translateY.get()` in JSX). It's a snapshot that never updates and it silently desyncs. **Never write one during render either** — it fires mid-reconciliation, and a re-render you didn't cause replays the write. Touch shared values only in worklets, handlers, and effects.
+- **Use `.get()` / `.set()`, not `.value`.** Same API, but direct `.value` access is the form the React Compiler can't see through — the Reanimated docs call `get`/`set` the compiler-safe way. `set` also takes a functional update: `sv.set((v) => v + 1)`.
+- **Functions called from a worklet need `'worklet'`** as their first line, or they throw at runtime on device while working fine in the debugger.
+
+### 7. Press, not hover
+
+Every hover affordance from the web has to be redesigned, not ported.
+
+- **Feedback on press-in, commit on press-out.** Waiting for the tap to complete before showing anything feels dead — this is the latency the user actually perceives.
+- **`scale: 0.97` in 100–150ms** on any button-like pressable, `Pressable` + a CSS transition. `scale` takes the label and icons with it, which is what makes it read as physical. Full-width list rows are the exception: they highlight their background instead — a scaling row reads as the whole screen squishing.
+- **44×44pt minimum touch target** (48dp Android). If the visual is smaller, add `hitSlop` — don't grow the visual.
+- **`pressRetentionOffset`** so a finger drifting a few pixels doesn't cancel a press the user meant.
+- **Android ripple only in a Material-styled app.** In a custom-designed app, the same scale on both platforms is more coherent than a ripple on one.
+
+### 8. Haptics
+
+Mobile has a sense the web doesn't. Use it sparingly and it becomes the thing that makes the app feel expensive; use it everywhere and users turn it off.
+
+| Moment | Call |
+| --- | --- |
+| A value ticks past a step — picker, slider detent, segmented control | `Haptics.selectionAsync()` |
+| Something snaps home, a sheet detent catches, a drag commits | `Haptics.impactAsync(ImpactFeedbackStyle.Light)` |
+| A heavy object lands, a destructive action fires | `Haptics.impactAsync(ImpactFeedbackStyle.Medium)` |
+| Operation succeeded or failed | `Haptics.notificationAsync(NotificationFeedbackType.Success / Error)` |
+
+Three rules, and they're absolute:
+
+- **Same frame as the visual.** A haptic that lags its animation reads as a glitch, not as feedback. Fire it at the causal moment — the detent catching — not when the animation finishes.
+- **One per user action.** Never on scroll, never per frame, never on an entrance animation the user didn't cause.
+- **Never the only feedback.** Haptics are off system-wide for many users, and silent on most Android hardware. The visual has to stand alone.
+
+From a worklet, haptics must be scheduled back to the RN runtime: `scheduleOnRN(Haptics.selectionAsync)`.
+
+### 9. Reduced motion and accessibility
+
+```jsx
+import { useReducedMotion, ReduceMotion, withSpring } from 'react-native-reanimated';
+
+const reduced = useReducedMotion();
+const y = useSharedValue(reduced ? 0 : SHEET_HEIGHT);
+
+// or let each animation decide
+withSpring(0, { duration: 300, dampingRatio: 0.8, reduceMotion: ReduceMotion.System });
+```
+
+Reduced motion means **fewer and gentler**, not zero: keep opacity and color changes that explain a state change, drop translation, scale, parallax and overshoot. Screen transitions become `animation: 'fade'`.
+
+**Text scales.** `allowFontScaling` is on by default, so any height you measured at default type size is wrong at 200%. Never animate to a hardcoded height — measure with `onLayout`, or animate a transform instead.
+
+## Setup that silently breaks motion
+
+Check these first when "the animation just doesn't run":
+
+- Install through Expo so versions match the SDK: `npx expo install react-native-reanimated react-native-worklets`. In an Expo project, `babel-preset-expo` configures the worklets Babel plugin automatically — no `babel.config.js` step. Only a bare RN project without that preset adds the plugin manually, and there it must be last in the list. A missing or misplaced plugin doesn't silently fall back anymore — it throws `Failed to create a worklet` at runtime.
+- `GestureHandlerRootView` must wrap the app, or gestures do nothing with no error.
+- Reanimated 4 requires the New Architecture.
+- **Expo Go is not a performance environment.** Judge feel in a release build; a dev build's JS thread is slow enough to hide exactly the problems you're looking for.
+
+## 120fps
+
+On ProMotion iPhones, third-party animations are capped at 60fps unless `CADisableMinimumFrameDurationOnPhone` is set. Recent Expo SDKs set it by default — confirm it's there, and add it if not:
+
+```json
+{ "expo": { "ios": { "infoPlist": { "CADisableMinimumFrameDurationOnPhone": true } } } }
+```
+
+Then the frame budget is 8ms, not 16. This is also why a UI-thread animation matters more on mobile than it does on web.
+
+## Recipes
+
+For ready-to-build implementations — press feedback, drag-to-dismiss sheet, swipe-to-delete, collapsing header, list entrances, keyboard-synced UI, tab indicator, screen transitions — see [RECIPES.md. Load it whenever the request matches one; start from the recipe rather than from a blank file.
+
+## Never Ship
+
+| Never | Instead |
+| --- | --- |
+| `PanResponder` | `Gesture.Pan()` from gesture-handler |
+| `setState` in a gesture or scroll handler | shared value + `useAnimatedStyle` |
+| `runOnJS` (deprecated in Reanimated 4) | `scheduleOnRN` from `react-native-worklets` |
+| `scheduleOnRN` per frame | `onEnd`, or `useAnimatedReaction` at a threshold |
+| Reading or writing a shared value during render | `.get()` / `.set()` in worklets, handlers, effects |
+| Core `Animated` for anything a finger touches | Reanimated |
+| Animating `height` / `width` / `margin` / `flex` / `top` | `transform` + `opacity` (absolute, childless elements exempt) |
+| Animating `BlurView` intensity or Android `elevation` | crossfade a static layer |
+| `entering` on a virtualized list row | animate the container, or `itemLayoutAnimation` |
+| A screen transition rebuilt in JS | native stack `animation` |
+| Sliding between tabs | `animation: 'none'` |
+| `Easing.in(...)` on a UI element | `Easing.bezier(0.23, 1, 0.32, 1)` |
+| `'cubic-bezier(...)'` in a Reanimated CSS style | `cubicBezier(...)` from `react-native-reanimated` |
+| `scale(0)` entrance | `scale(0.95)` + `opacity: 0` |
+| Distance-only dismissal threshold | velocity **or** distance — a flick is enough |
+| Hard stop at a boundary | rubber-band resistance |
+| A haptic per frame, or as the only feedback | one per commit, always paired with a visual |
+| Judging feel in Expo Go or the simulator | release build, slowest supported device |
+
+## Output
+
+Write the code. Then, in at most a few lines:
+
+- **The gate result** — frequency tier and named purpose. Say what you rejected and why.
+- **The ingredients** — tool, properties, spring or curve + duration, thread.
+- **What to feel-check on device** — gestures, velocity handoff and haptic timing cannot be judged from code. Name what to try: flick it, interrupt it mid-flight, reverse it, run it on the slowest Android you have.
+
+The code is the deliverable. Don't pad it into a report.
+
+## Tone
+
+Opinionated and brief. When the honest answer is "this shouldn't animate," or "this needs a real device before I can tell you if it's right," give it.
+
+## Submitting Feedback
+If you encounter errors, misleading or outdated information in this skill, report it so Expo can improve:
+```bash
+npx --yes submit-expo-feedback@latest --category skills --subject "expo-animation" "<actionable feedback>"
+```
+Only submit when you have something specific and actionable to report. Include as much relevant context as possible.
+If an AI agent repeatedly failed or the user had to take over an Expo task, load the expo-skill-feedback skill and follow its eval-candidate flow instead of reusing the command above.
+
+
+## Examples
+
+```text
+User: Apply this skill to my current task.
+Assistant: Follow the workflow in this skill, cite limitations, and ask before risky steps.
+```
+
+## Limitations
+
+- Imported upstream skill; verify credentials, permissions, and safety boundaries before execution.
+- Does not replace environment-specific validation, testing, or maintainer review.

package/bundled-skills/expo-animation/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Expo Animation"
+  short_description: "Build polished Expo and React Native animations"
+  default_prompt: "Use $expo-animation to build a polished, accessible animation for this Expo app."

package/bundled-skills/fact-check-x-unified/SKILL.md

@@ -0,0 +1,178 @@
+---
+name: fact-check-x-unified
+description: Fact-Check-X 流程编排能力，依次组织各方答案汇总、各方答案聚合（未核验）、权威核验后的最终答案和各方答案测评，生成可打开、可审计、可迁移的阶段产物与完整报告包。
+license: Apache-2.0
+source_repo: asi2030/fact-check-x
+source_type: official
+source: asi2030
+date_added: '2026-09-21'
+risk: unknown
+---
+## When to Use
+- Use when this upstream workflow matches the user's stated goal.
+- Use when the task requires the procedures documented in this skill.
+
+# Fact-Check-X 统一入口
+
+本技能只做编排，不内嵌三个业务层。它按以下顺序调用兄弟技能：
+
+1. `llm-answer-reference-compare`：多平台回答、引用与现场存证采集。
+2. `fact-check-x-knowledge-compare`：本地知识点结构化对比，可选。
+3. `fact-check-x-authoritative-verify`：逐知识点并发权威核验与平台表现报告。
+
+所有语义拆解和证据裁决由当前承载技能的智能体完成。脚本不调用任何模型 API。
+
+## 依赖定位
+
+四个技能放在同一目录时可直接运行。也可设置：
+
+```bash
+export FACTCHECK_SKILLS_DIR="<四个技能的父目录>"
+```
+
+检查依赖：
+
+```bash
+python3 scripts/fact_check_x.py locate
+```
+
+## 完整流程
+
+先采集 `results.json`，然后准备知识点对比：
+
+```bash
+python3 scripts/fact_check_x.py prepare-comparison \
+  --results <results.json> \
+  --run-dir <run>
+```
+
+命令会同步生成“各方答案汇总”，在运行目录顶层生成 `01-capture-report.html`。每个 `deliverables` 条目同时返回已验证存在的本机 `path`、标准 `fileUri` 和可直接展示的 `markdownLink`。调用方必须原样展示 `markdownLink`，不得自行拼接 Windows 路径或把 `path` 直接塞进 Markdown；产物不存在时命令会在当前阶段失败。
+
+默认交互模式下，程序会把阶段状态写入 `stage-checkpoints.json`。调用方发送本阶段产物并收到用户“继续下一步”后，必须使用 `checkpoint.acknowledgement.token` 执行：
+
+```bash
+python3 scripts/fact_check_x.py acknowledge-stage \
+  --run-dir <run> --stage <checkpoint.stage> \
+  --token <checkpoint.acknowledgement.token> --decision continue
+```
+
+未确认时，下一阶段命令会直接失败。即使用户最初要求完整连续执行，也必须依次展示每个阶段产物并取得确认；不存在可绕过确认的自动推进模式。
+
+当前智能体读取 `<run>/comparison-task.json`，写入 `<run>/comparison-analysis.json`，再执行：
+
+`comparison-task.json` 是自包含的紧凑工作集。阶段确认后只允许“读取任务包一次、写入分析一次、执行验收一次”，最多三次工具调用；不得读取技能源码、契约或完整 `results.json` 探路，不得打印或转储完整任务包。`capturedText` 只是有界原文预览，完整正文由程序在验收时从 `results.json` 校验和重建。
+
+拆解时，原子性同时约束知识点和各平台 `claim`。一个原句包含多个独立义务、条件、对象、数值或后果时必须拆点，每个 `claim` 只保留当前事实；平台独有的实质新增事实也要另起无锚点知识点，不能并入宽泛知识点后复用深知晓锚点免查。每个知识点同时标明 `claimType=fact|recommendation`：纯操作建议可标为 `recommendation`，不因缺少逐句脚标而判引用不忠实；建议中包含的制度事实、条件、数字或时效必须拆成独立 `fact`。
+
+```bash
+python3 scripts/fact_check_x.py complete-comparison \
+  --results <results.json> \
+  --run-dir <run>
+```
+
+命令会在运行目录顶层生成 `02-comparison-report.html`，并通过 `deliverables[].markdownLink` 返回可点击链接；调用方必须原样展示。报告必须包含明确标为“未核验”的综合草案。默认交互模式下，用户确认继续后才能进入权威核验。
+
+生成每个知识点的独立云端请求并并发取证：
+
+```bash
+python3 scripts/fact_check_x.py prepare-authority --run-dir <run>
+python3 scripts/fact_check_x.py search-authority --run-dir <run> --max-workers 12
+```
+
+深知晓采集同时保留回答内逐句脚标和“知识专库”中的回答级来源；相同 URL 合并为 `inline_and_global`。回答级来源只有经当前知识点逐条语义匹配且原文可定位时才可支持该事实，不得整库继承。知识点已有深知晓/深知晓（深度溯源）本次回答所附的官方材料，或其他平台本次回答所附的 `gov.cn` 材料，且原文确实支持当前事实主张时，直接复用为官方证据，不调用可信搜索。纯操作建议同样不调用可信搜索；除此之外，已有材料不足以裁决的事实知识点才是非免查知识点。
+
+若存在非免查知识点但本机尚无可信搜索配置，`prepare-authority` 和 `search-authority` 会返回 `status=configuration_required`、`userPrompt` 与 `configuration.command` 并以非零状态退出。调用方先展示登录提示，再前台执行该命令。用户只需在自动打开的深知 MaaS 页面完成登录；组件会自动复用已有完整 Key，没有时创建 `Fact-Check-X` 专用 Key，验证后保存到 `~/.fact-check-x/credentials/trusted-search-key`。Codex、Claude Code、WorkBuddy 等载体共享该配置，检测到已有 Key 时直接跳过登录。配置成功后调用方自动重跑 `prepare-authority`，不得要求用户复制 Key、编辑 shell 配置、回复“已配置”，也不得改用深知晓来源或普通搜索绕过。
+
+只有可信搜索返回 401/403 时才把现有 Key 视为失效并进入自动配置。超时、断网或服务异常保留现有配置并自动重试；重试后仍失败则停留在搜索阶段返回技术错误，不要求用户重新登录，也不转成人工事实复核。
+
+`prepare-authority` 会写入 `authority-gate.json`。只有可信搜索批次正常完成、门禁状态变为 `searched` 后，`finalize-authority` 才允许运行；手工写 evidence 或 result 不能绕过。
+
+当前智能体逐个读取 `authority/requests` 与 `authority/evidence`，把裁决写入 `authority/assessments/<知识点ID>.json`，然后：
+
+免查模式下，`trustedAnchor.officialAnswer` 是当前事实知识点的权威结论；锚点证据列表用于来源追溯。无论来自深知晓还是 `gov.cn`，都必须确认已捕获正文实际支持该结论，不得仅凭官方属性自动判定。`trustedAnchor.claimEvidenceMap` 记录各平台已经逐主张绑定的官方原文；命中该映射的平台直接复用本次回答自带证据，不得因另一轮可信搜索未召回同一材料而降为证据不足。其他平台主张与 `officialAnswer` 语义一致或可由其直接推出时，裁决为 `supported` 并引用有效锚点证据 ID。仅当平台主张增加了权威结论不能支持的实质事实，或确实无法判定时，才使用 `insufficient`。知识点对比阶段的引用忠实性与本阶段的事实正确性分别保留，不能因平台自身引用不足而拒绝判断已经被权威结论证实的主张。`recommendation` 作为“操作建议”单独展示，不进入事实准确率或幻觉率；若权威证据证明建议会误导，仍可判为 `contradicted`。
+
+```json
+{
+  "authoritativeFinding": "由权威证据支持的知识点结论",
+  "verdicts": {
+    "<平台ID>": {
+      "verdict": "supported",
+      "reason": "主张与 E1 一致",
+      "evidenceIds": ["E1"]
+    }
+  }
+}
+```
+
+`verdict` 只能使用 `supported`、`contradicted` 或 `insufficient`，证据 ID 必须存在于当前 evidence 文件中。旧式顶层 `verdict`、`officialAnswer`、`platformAssessment` 会被拒绝。
+
+```bash
+python3 scripts/fact_check_x.py finalize-authority --run-dir <run>
+```
+
+第三步完成后如需修正 assessment，禁止手工清空结果或修改 gate。先执行 `python3 scripts/fact_check_x.py reopen-authority --run-dir <run> --reason "<原因>"`；程序校验锁定摘要并归档旧裁决后回退到 `searched`，再修改 assessment、重新 `finalize-authority` 并重新确认第三步产物。
+
+`finalize-authority` 生成“权威核验后的最终答案”，只将证据充分的直接知识点纳入 `finalAnswer`，将补充参考单独写入 `supplementalFindings`，将证据不足项写入 `evidenceGaps`。第三步只展示直接答案、证据边界和简洁来源索引；逐知识点裁决与评分只在第四步展示。
+
+`finalize-authority` 完成裁决后会独立生成 `03-authority-report.html`，并通过
+`deliverables` 返回已验证的路径、文件 URI 和 `markdownLink`。调用方必须原样展示 `markdownLink`；默认交互模式下，
+只有状态为 `completed` 且用户确认继续后才执行：
+
+```bash
+python3 scripts/fact_check_x.py deliver --results <results.json> --run-dir <run>
+```
+
+可信搜索返回 `no_evidence` 时记录为 `insufficient_evidence`：空结果只表示本次没有取得可裁决材料，不能直接判成“编造”；证据边界记录完成后继续生成后续报告。
+
+`deliver` 必须在运行目录顶层生成并返回四份独立可读报告：
+
+- `01-capture-report.html`：各方答案汇总；
+- `02-comparison-report.html`：各方答案聚合（未核验）；
+- `03-authority-report.html`：权威核验后的最终答案、权威证据和证据边界；
+- `04-final-report.html`：各方答案测评报告。
+
+`deliver` 只能读取第三步已锁定的 `verification.json` 和 `03-authority-report.html`；任一文件摘要变化都必须拒绝，不得重算或重写第三步。
+
+缺少任一报告都不得生成或交付 `05-complete-report-package.zip`。
+
+最终保留：
+
+- `capture/results.json`、`capture/report.html`、`capture/report.md`；
+- `comparison-task.json`、`comparison-analysis.json`、`comparison.json`、`comparison.html`；
+- 每个知识点独立的 request、evidence、assessment、result；
+- `authority/batch.json`、`verification.json`、`report.html`、`pipeline.json`；
+- 四份阶段报告和 `05-complete-report-package.zip`。
+
+## 跳过知识点对比
+
+知识点对比是可选能力。已有结构化知识点时，可按权威证据核验模块的数据契约直接建立单知识点请求，独立调用 `fact-check-x-authoritative-verify`。统一入口不会强迫用户先采集多个 AI 回答。
+
+## 执行边界
+
+- 原始答案阶段只采集，不核验；可用可信搜索全文参数补全平台已给出的同一来源正文，但不得新增或替换引用。
+- 知识点对比只比较原答案与所附来源，不联网找真相。
+- 云端层只接收当前知识点；各家主张相同则不上传主张，不同才上传差异。
+- 深知晓已有合格官方锚点时不重复搜索。
+- 最终报告必须使用权威证据核验模块内的稳定报告渲染器。
+
+## 交付门禁
+
+```bash
+python3 tests/smoke_test.py
+python3 "${CODEX_HOME:-$HOME/.codex}/skills/.system/skill-creator/scripts/quick_validate.py" .
+```
+
+完整标准见 [验收标准]。
+
+
+## Examples
+
+```text
+User: Apply this skill to my current task.
+Assistant: Follow the workflow in this skill, cite limitations, and ask before risky steps.
+```
+
+## Limitations
+
+- Imported upstream skill; verify credentials, permissions, and safety boundaries before execution.
+- Does not replace environment-specific validation, testing, or maintainer review.

package/bundled-skills/fact-check-x-unified/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Fact-Check-X 流程编排"
+  short_description: "编排原始答案采集、知识点对比、权威核验和完整交付"
+  default_prompt: "使用 $fact-check-x-unified 编排完整事实核验链路；语义工作由当前智能体完成，不调用外部模型接口。"

package/bundled-skills/fact-check-x-unified/references/acceptance-criteria.md

@@ -0,0 +1,44 @@
+# 验收标准
+
+## 架构
+
+- 对外入口是轻量编排 Skill，不复制 1.0、1.1、可信搜索或报告实现。
+- 原始答案采集、知识点对比、权威证据核验均可独立安装和独立调用。
+- 四个 Skill 全部使用中文说明和中文交互提示。
+- 语义分析使用当前承载技能的智能体，代码中没有模型 API 客户端、模型名称、模型密钥或模型路由。
+
+## 1.0
+
+- 完整回答、原始引用列表、引用标记、原始 URL 和现场存证无损保留。
+- 原 URL 不被标题搜索或其他 URL 替换。
+- 失败状态显式保留。
+- 回答停止生成前不得落盘；自动重采仍失败时输出 Computer Use 恢复请求。
+- 任一平台失败、回答为空、内容仍是登录/地区提示或恢复状态为 `required` 时，`capture-gate.json` 必须阻止所有下游步骤。
+
+## 1.1
+
+- 形成所有平台知识点并集，区分直接答案与补充参考。
+- 精确呈现相同、不同、各自主张、所附依据与来源忠实性。
+- 有显式标记只用标记来源；无标记才检查该平台全部原始来源。
+- 不调用可信搜索或网络搜索。
+- 中间报告按实际平台数动态展示全部原答案与知识点；默认 2 家，`N=1` 展示单平台结构化核验，`N≥2` 增加跨平台对比，不得截断第三家及后续平台。
+
+## 权威核验
+
+- 每个知识点形成一个独立请求，多个请求并发执行。
+- 云端用户内容只有总标题、当前知识点和必要的差异主张。
+- 主张相同不上传主张；不同才上传差异。
+- 深知晓已附官方材料，或其他平台已附 `gov.cn` 材料，且正文实际支持当前主张时免查，实际请求数为 0。
+- 非深知晓、非 `gov.cn` 或已有材料不足以裁决的知识点，每点只进行一次可信搜索，所有平台共用证据。
+- `dknowExemptCount`、`govExemptCount` 和 `officialExemptCount` 必须与比较结果一致。
+- 分类符合直接准确、间接准确、结果巧合、严重误导、凭空编造、证据不足、未覆盖的最终口径。
+- 官方前提的一步显然算术推导可判直接准确。
+
+## 最终交付
+
+- 独立交付原始答案、参考文献、引用标记、原始 URL 与现场存证报告，不依赖最终报告的折叠章节才能查看。
+- `pipeline.json` 明确登记 `capture/results.json`、`capture/report.html` 和 `capture/report.md`。
+- 最终报告使用统一渲染器，保留参考性、逐条判定、补充参考、关键发现、原始存证、指标口径和元信息章节。
+- 同一组 JSON 中间产物可离线重现相同类别、指标和报告结构。
+- 套件与四个独立 zip 可解压运行，不包含浏览器登录目录、历史运行数据或密钥。
+- 四个冒烟测试、技能结构校验、禁止模型 API 扫描和打包清单校验全部通过。

package/bundled-skills/fact-check-x-unified/references/contracts.md

@@ -0,0 +1,39 @@
+# 编排契约
+
+统一入口不发明新的业务判断，只连接三个稳定契约：
+
+- 1.0：`schemaVersion=1` 的 `results.json`。
+- 1.1：`fact-check-x/comparison@1`。
+- 单点权威请求：`fact-check-x/authority-request@1`。
+- 单点权威结果：`fact-check-x/authority-result@1`。
+- 汇总：`fact-check-x/verification@2`。
+- 流水线：`fact-check-x/pipeline@2`。
+
+`comparison-gate.json` 锁定 1.0 结果、智能体分析和归一化 comparison 的 SHA-256。`authority-gate.json` 锁定 request、evidence、assessment、result 的精确 ID 集合与 SHA-256；任何缺失、额外、陈旧或后改文件都必须阻断后续步骤。
+
+`verification.json`：
+
+```json
+{
+  "schemaVersion": "fact-check-x/verification@2",
+  "question": "用户问题",
+  "finalAnswer": {
+    "status": "verified",
+    "answer": "按知识点顺序合并的权威核验答案",
+    "knowledgePointIds": ["K1"]
+  },
+  "platforms": [{"platform": "dknowc-chat", "label": "深知晓"}],
+  "knowledgePoints": [
+    {
+      "id": "K1",
+      "description": "原子事实",
+      "claims": {},
+      "authority": {"schemaVersion": "fact-check-x/authority-result@1"}
+    }
+  ],
+  "trustedSearchRequestCount": 0,
+  "status": "completed"
+}
+```
+
+`pipeline.json` 记录每层技能名称、产物绝对路径、知识点数、实际可信搜索请求数、深知晓官方材料免查数、`gov.cn` 材料免查数、官方材料免查总数和最终状态。

package/bundled-skills/fact-check-x-unified/scripts/common.py

@@ -0,0 +1,31 @@
+#!/usr/bin/env python3
+from __future__ import annotations
+
+import json
+import os
+import tempfile
+from datetime import datetime, timezone
+from pathlib import Path
+from typing import Any
+
+
+class PipelineError(RuntimeError):
+    pass
+
+
+def load_json(path: str | Path) -> Any:
+    return json.loads(Path(path).read_text(encoding="utf-8"))
+
+
+def dump_json(path: str | Path, value: Any) -> None:
+    target = Path(path)
+    target.parent.mkdir(parents=True, exist_ok=True)
+    with tempfile.NamedTemporaryFile("w", encoding="utf-8", dir=target.parent, delete=False) as handle:
+        json.dump(value, handle, ensure_ascii=False, indent=2)
+        handle.write("\n")
+        temporary = handle.name
+    os.replace(temporary, target)
+
+
+def now_iso() -> str:
+    return datetime.now(timezone.utc).astimezone().isoformat(timespec="seconds")