ScepticAgent Prompts Reference

VerifiedSafe

Complete reference of prompts used by ScepticAgent to analyze web pages, verify sources, and detect bias and misinformation.

Sby Skills Guide Bot
Data & AIIntermediate
7/23/2026
Claude Code
#scepticagent#ai-prompts#misinformation-analysis#bias-detection#content-verification

Recommended for

Automated summary

Reference for ScepticAgent AI prompts, enabling customization of web page analysis to detect misinformation, bias, and emotional language.

Strengths

  • Structured misinformation detection with categories and scoring
  • Leverages web search to verify claims in real-time
  • JSON output easily parseable for highlights and analysis
  • Fine-grained control over analysis categories and behavior

Limitations

  • Limited to 10,000 characters of page content
  • Relies on web search function (may fail if unavailable)
  • Highlights must be verbatim from the page, which can be restrictive
When to use it

When you need to instruct the AI to objectively analyze a web page with source verification and bias highlighting.

When not to use it

For creative or subjective analyses where factual verification is not relevant.

Security analysis

Safe
Quality score90/100

This skill is a static reference document describing AI prompt locations, formats, and constraints for a browser extension. It contains no executable instructions, no tool declarations, and no dangerous operations. It poses no execution risk.

No concerns found

How this analysis is made

Examples

Change analysis categories
Modify the buildAnalysisSystem prompt to include a new category 'Logical Fallacies' with its own output section.
Adjust highlight format
Update the highlights prompt to increase the maximum number of highlights from 25 to 40.
Tune scoring behavior
Add a numerical score (0-10) for each highlight category in the JSON output of the highlights prompt.

name: scepticagent-prompts description: ScepticAgent AI prompt reference. Use whenever the user asks about the prompts, wants to change analysis behaviour, modify what the AI looks for, adjust highlight categories or scoring, understand what instructions are sent to the AI, or tune the output format of analysis or highlights.

Prompt locations — all in background.js

buildAnalysisSystem(url, title, content) — lines 658–705

Full page analysis system prompt. Instructs Claude to use web_search to verify claims, check source credibility, find supporting/opposing evidence, identify bias and emotional language. Page content truncated to 10000 chars.

Required output sections (renderer depends on these exact headings):

## Key Claims
## References & Sources
## Supporting Evidence
## Opposing Perspectives
## Bias & Framing
## Emotional Language
## Misinformation Risks
## Overall Assessment

Sources must be cited as inline markdown links e.g. [Reuters](https://reuters.com/...).


buildChatSystem(url, title, content) — lines 707–720

Chat follow-up system prompt. Instructs the agent to answer questions about the page using web search and cite sources as inline markdown links. Page content truncated to 10000 chars.


buildHighlightsPrompt(withSearch) — lines 108–140

Extracts verbatim phrases from the page. Two modes:

  • withSearch: true — includes STEP 1 (web_search for real URLs) / STEP 2 (output JSON). Used in manual "Highlight Page" after analysis is complete.
  • withSearch: false — JSON output only, source_url left empty. Used in the auto fast scan on page open.

Output JSON schema:

{
  "summary": "two sentences — what the article is about, then how emotional/factual/biased it is",
  "category_summaries": {
    "misinformation": "one sentence",
    "emotional": "one sentence",
    "bias": "one sentence",
    "supported": "one sentence",
    "logical": "one sentence"
  },
  "highlights": [
    {
      "phrase": "verbatim text from page (8–180 chars, no quote characters)",
      "category": "misinformation|emotional|bias|supported|logical",
      "note": "max 90 chars explanation",
      "source": "publication name or empty string",
      "source_url": "full URL or empty string"
    }
  ]
}

Constraints: max 25 highlights, phrases must appear verbatim on the page, no markdown code fences in output, no typographic quote characters in phrases.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/scepticagent-prompts-reference-mrwakg0a/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/scepticagent-prompts-reference-mrwakg0a' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/scepticagent-prompts-reference-mrwakg0a/download' --output '.skill-downloads/scepticagent-prompts-reference-mrwakg0a/SKILL.md.part' && mv '.skill-downloads/scepticagent-prompts-reference-mrwakg0a/SKILL.md.part' '.skill-downloads/scepticagent-prompts-reference-mrwakg0a/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/scepticagent-prompts-reference-mrwakg0a/SKILL.md' && test -s '.skill-downloads/scepticagent-prompts-reference-mrwakg0a/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/scepticagent-prompts' && cp -R '.skill-downloads/scepticagent-prompts-reference-mrwakg0a' '.claude/skills/scepticagent-prompts'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/scepticagent-prompts-reference-mrwakg0a'

openskills read 'scepticagent-prompts-reference-mrwakg0a'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/scepticagent-prompts-reference-mrwakg0a/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills