fact checker

Other Community

Skill notes

When to use

Trigger when users request: "Fact-check this document" "Verify these AI model specifications" "Check if this information is still accurate" "Update outdated data in this file"

Workflow

Copy this checklist to track progress:

Step 1: Identify factual claims

Scan the document for verifiable statements: Target claim types: Technical specifications (context windows, pricing, features) Version numbers and release dates Statistical data and metrics

Step 2: Search authoritative sources

For each claim, search official sources: AI models: Official announcement pages (anthropic.com/news, openai.com/index, blog.google) API documentation (platform.claude.com/docs, platform.openai.com/docs) Developer guides and release notes

Step 3: Compare claims against sources

Create a comparison table: Claim in Document · Source Information · Status · Authoritative Source Claude 3.5 Sonnet: 200K tokens · Claude Sonnet 4.5: 200K tokens · ❌ Outdated model name · platform.claude.com/docs GPT-4o: 128K tokens · GPT-5.2: 400K tokens · ❌ Incorrect version & spec · openai.com/index/gpt-5-2 Status codes:

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Other
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@daymade · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Windows
Runtime requirements
Python
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1: Identify factual claims

Scan the document for verifiable statements: Target claim types: Technical specifications (context windows, pricing, features) Version numbers and release dates Statistical data and metrics

02
Step 2: Search authoritative sources

For each claim, search official sources: AI models: Official announcement pages (anthropic.com/news, openai.com/index, blog.google) API documentation (platform.claude.com/docs, platform.openai.com/docs) Developer guides and release notes

03
Step 3: Compare claims against sources

Create a comparison table: Claim in Document · Source Information · Status · Authoritative Source Claude 3.5 Sonnet: 200K tokens · Claude Sonnet 4.5: 200K tokens · ❌ Outdated model name · platform.claude.com/docs GPT-4o: 128K tokens · GPT-5.2: 400K tokens · ❌ Incorrect version & spec · openai.com/index/gpt-5-2 Status codes:

04
Step 4: Generate correction report

Present findings in structured format:

05
Step 5: Apply corrections with user approval

Before making changes: Show the correction report to the user Wait for explicit approval: "Should I apply these corrections?" Only proceed after confirmation When applying corrections:

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.