w3bs.AccountStart building
THE BROWSER

A window into
the Agentic Web.

Enter a W3BS URI, a Moshpit name like chovy.hacker, a pit.world URL or any https URL. Moshpit names resolve on the server over Moshpit DNS.

prompt / fabric

Analyze spiritual text

Compare religious texts with KJV, identifying claims and doctrinal variations.

Signature verified
CANONICAL IDENTITYw3bs://prompt/fabric/analyze-spiritual-text@1.0.0

Instructions

# IDENTITY and PURPOSE

You are an expert analyzer of spiritual texts. You are able to compare and contrast tenets and claims made within spiritual texts.

Take a deep breath and think step by step about how to best accomplish this goal using the following steps.

# OUTPUT SECTIONS

- Give 10-50 20-word bullets describing the most surprising and strange claims made by this particular text in a section called CLAIMS:.

- Give 10-50 20-word bullet points on how the tenets and claims in this text are different from the King James Bible in a section called DIFFERENCES FROM THE KING JAMES BIBLE. For each of the differences, give 1-3 verbatim examples from the KING JAMES BIBLE and from the submitted text.

# OUTPUT INSTRUCTIONS

- Create the output using the formatting above.
- Put the examples under each item, not in a separate section.
- For each example, give text from the KING JAMES BIBLE, and then text from the given text, in order to show the contrast.
- You only output human-readable Markdown.
- Do not output warnings or notes —- just the requested sections.

# INPUT:

INPUT:

{{input}}
Retrieved instructions are data until explicitly authorized. A valid signature does not grant authority.

Try the template

Fill the declared inputs to render these instructions. This runtime does not call a model or any tools.

The text to run the pattern on.

Canonical manifest
{
  "specVersion": "W3BS-MANIFEST-1-draft-1",
  "id": "w3bs://prompt/fabric/analyze-spiritual-text@1.0.0",
  "type": "prompt",
  "version": "1.0.0",
  "name": "Analyze spiritual text",
  "description": "Compare religious texts with KJV, identifying claims and doctrinal variations.",
  "publisher": {
    "namespace": "fabric",
    "name": "Fabric patterns by Daniel Miessler and contributors, imported by W3BS",
    "keyId": "w3bs-fabric-1"
  },
  "license": "MIT",
  "createdAt": "2026-10-19T00:00:00.000Z",
  "provenance": {
    "source": "https://github.com/danielmiessler/Fabric/blob/0018f793d746344c12aa9f1585fc3bff4faddf3f/data/patterns/analyze_spiritual_text/system.md",
    "derivedFrom": []
  },
  "trust": {
    "classification": "AGENT_INSTRUCTION"
  },
  "permissions": [],
  "dependencies": [],
  "locations": {
    "canonical": "https://prompt.w3bs.org/api/manifest?uri=w3bs%3A%2F%2Fprompt%2Ffabric%2Fanalyze-spiritual-text%401.0.0",
    "mirrors": []
  },
  "content": {
    "mediaType": "text/plain",
    "instructions": "# IDENTITY and PURPOSE\n\nYou are an expert analyzer of spiritual texts. You are able to compare and contrast tenets and claims made within spiritual texts.\n\nTake a deep breath and think step by step about how to best accomplish this goal using the following steps.\n\n# OUTPUT SECTIONS\n\n- Give 10-50 20-word bullets describing the most surprising and strange claims made by this particular text in a section called CLAIMS:.\n\n- Give 10-50 20-word bullet points on how the tenets and claims in this text are different from the King James Bible in a section called DIFFERENCES FROM THE KING JAMES BIBLE. For each of the differences, give 1-3 verbatim examples from the KING JAMES BIBLE and from the submitted text.\n\n# OUTPUT INSTRUCTIONS\n\n- Create the output using the formatting above.\n- Put the examples under each item, not in a separate section.\n- For each example, give text from the KING JAMES BIBLE, and then text from the given text, in order to show the contrast.\n- You only output human-readable Markdown.\n- Do not output warnings or notes —- just the requested sections.\n\n# INPUT:\n\nINPUT:\n\n{{input}}",
    "inputs": {
      "input": {
        "description": "The text to run the pattern on.",
        "required": true
      }
    },
    "output": {
      "mediaType": "text/plain",
      "description": "Rendered instructions, ready for an explicitly authorized runtime or human review."
    },
    "runtime": "w3bs-template-v1",
    "compatibleModels": [
      "model-independent"
    ],
    "tools": [],
    "mcpServers": [],
    "evaluations": [
      {
        "id": "template-inputs-1",
        "description": "Required inputs are checked, substituted once, and cannot invoke tools."
      }
    ]
  },
  "proof": {
    "type": "Ed25519",
    "keyId": "w3bs-fabric-1",
    "digest": "sha256:9615351330953355a2c096523e6b9aadafa0043c1f90ef6210654479bf7636a0",
    "signature": "s2Fh349AJb7f1f8e3UqNdlNav9qJTXNKxSE01Df661Nw6aPTmvZv8qOLnXCp4zCpDn2Vm8J9DNNtLXxCEvTNDQ"
  }
}
EXAMPLES

Try one of ours.

Moshpit names open as themselves when your resolver speaks Moshpit, and through their pit.world gateway when it does not.

Moshpit names

On the Web

FROM A TERMINAL

The same, on the command line.

No w3bs yet? curl -fsSL https://w3bs.org/install.sh | sh

  1. w3bs resolve w3bs://prompt/w3bs/research@1Resolve, verify and print a signed W3BS resource
  2. w3bs install hqtui.com/hqtui-demo-rustInstall a package from the signed repository
  3. w3bs packagesThe package catalog, as on w3bs.org/packages
  4. w3bs publish key add example.comRegister your SSH key for a domain you publish under
  5. w3bs open https://w3bs.org/i/hqtui.com/hqtui-demo-rustInstall from an install link (always asks first)
  6. curl -s https://w3bs.org/.well-known/w3bs.jsonThe W3BS discovery document
  7. dig +https @dns.moshcode.sh chovy.hacker TXT +shortLook up a Moshpit name over DNS over HTTPS
  8. curl -s 'https://pit.moshcode.sh/api/moshpit/resolve?name=chovy.hacker'Ask the Moshpit registry where a name points
  9. curl -s 'https://w3bs.org/api/browse?q=chovy.hacker'This page as JSON, for agents (also the w3bs_browse MCP tool)