بنقرة واحدة
fact-check
Fact-check content by verifying every claim against trusted sources.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Fact-check content by verifying every claim against trusted sources.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Create content of any configured type from a topic or from the content backlog. Orchestrates research, writing, style review, glossary creation, linking, and reindexing as focused sub-agents. Hooks handle tracker updates and build verification automatically.
content-seo setup wizard. Run /init to see status, or /init [round] to run a setup step. Rounds: project, credentials, strategy.
Site-level SEO intelligence. Routes to one of five workflows — status (site-wide GSC performance), opportunities (pages ranking 4–20), diagnose (deep-dive a page with GSC data + fixes), brief (keyword research before writing), or coverage (audit GSC indexing errors from a CSV export).
content-ops setup wizard. Run /init to see status, or /init [round] to run a setup step. Rounds: project, content-types, style, strategy, infra, images, link-building.
Identify content gaps and add suggestions to the backlog. Accepts an optional freeform payload to narrow scope. Without a payload, surveys the full corpus against pillars. Powered by the backlog-suggester agent.
Loads and applies the project's configured style guide. Hard stops if config or any required piece is missing. All style rules come from the guidelines file set during /init style.
| name | fact-check |
| description | Fact-check content by verifying every claim against trusted sources. |
| argument-hint | <file-path> |
| user-invocable | true |
| allowed-tools | Read, Glob, Grep, Bash, WebSearch, WebFetch, Edit, Task, TodoWrite |
Fact-check content by verifying claims against trusted sources.
File: $ARGUMENTS
Pass the path to an article or glossary file (e.g., src/content/articles/en/my-article.md).
Read the target file. Extract every factual claim:
List each claim clearly.
Delegate verification to the content-researcher agent. The agent uses a research cache (MCP) to avoid re-verifying known facts — it checks cached findings before doing web searches.
Use the content-researcher agent to verify these claims from the article "[title]":
1. [claim 1]
2. [claim 2]
...
For each claim: confirm, flag as unconfirmed, or mark incorrect with the correct information and source URL.
Check the research cache first; only search the web for uncached or stale topics.
Present the agent's findings in this format:
## Fact-Check Report: <article title>
### Summary
- Total claims checked: N
- Confirmed: N
- Unconfirmed: N
- Incorrect: N
### Details
| Claim | Status | Source | Notes |
|-------|--------|--------|-------|
| "X was created in 2009" | Confirmed | source-url/... | — |
| "reward is Y per cycle" | Incorrect | source-url/... | Corrected: Z per cycle |
After presenting the report, ask the user if they want you to fix incorrect claims directly. If yes:
content: fact-check corrections in "<title>"