okhp3-tradition-reference

Provide structured metadata for Abrahamic traditions, including canon scope and API providers.

2|1|Updated Jun 12, 2026
One-click install
npx skills add https://github.com/OKHP3/skillz --skill okhp3-tradition-reference
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: okhp3-tradition-reference
Source: https://github.com/OKHP3/skillz/tree/main/abrahamic/okhp3-tradition-reference
Command: npx skills add https://github.com/OKHP3/skillz --skill okhp3-tradition-reference

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill provides quick access to authoritative metadata for Abrahamic traditions, including Judaism, Christianity, and Islam, enabling accurate and informed content generation, API calls, and scope determination.

Core Features & Use Cases

  • Structured Reference: Offers comprehensive, structured information on Abrahamic traditions, including canon scope, key texts, population share, translations, and API providers.
  • Scope Determination: Helps determine if a tradition is in scope based on Abrahamic lineage and US population threshold.
  • Use Case: When an agent needs to know the canon of a denomination, available translations, or the correct API endpoint for a tradition, this Skill provides the necessary information.

Quick Start

Use the okhp3-tradition-reference skill to get information about the Christian canon.

Frequently Asked Questions about okhp3-tradition-reference

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What structured metadata is available for Abrahamic traditions like Judaism, Christianity, and Islam?

Structured metadata for Abrahamic traditions includes canon scope, key texts, US population share, available translations, and API providers, providing authoritative reference data to determine tradition scope and canonical information for accurate content generation.

How do I determine if a religious tradition is in scope based on Abrahamic lineage and US population thresholds?

You can determine tradition scope by checking the structured reference data for Abrahamic lineage and verifying if the tradition meets the designated US population threshold, with the metadata specifying which traditions qualify as in-scope within the ecosystem.

How do I find the correct API endpoint and available translations for a specific Christian denomination?

To find the correct API endpoint and translations for a Christian denomination, you query the tradition reference metadata, which maps denominations to their respective API providers and lists available translations for key texts within the ARE ecosystem.

What sections are explicitly out of scope when retrieving canonical information for Abrahamic traditions?

The metadata explicitly defines out-of-scope sections alongside canon scope and key texts, ensuring you do not attempt to retrieve unsupported canonical information or make invalid API calls for a tradition.

Does the interfaith reference metadata cover non-Christian Abrahamic texts and their API availability?

Yes, the interfaith reference metadata covers Judaism and Islam in addition to Christianity, providing canon scope, key texts, and API availability across all three Abrahamic traditions to support interfaith content generation and API calls.