Search

PythonReactSEOPDF
OpenClaw

pastoral-prayer

Produces full, readable pastoral prayers for specific scenarios (illness, thanksgiving, worship, funeral, wedding, baptism, etc.). Use when the user asks for a prayer for a pastoral situation. Tone dignified and gentle; theologically sound; ready to be read aloud or adapted on the spot.

chenios0 source installs☆ 0 Repository stars

Installation

Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.

SkillHub CLI

skillhub install chenios/pastoral-prayer

Inspect the source and compatibility requirements, then follow its installation steps.

Give your agent the source link and ask it to inspect instructions and dependencies before explaining the installation steps.

View source ↗Guides

Skill instructions

Pastoral Prayer

When the user specifies a scenario (e.g. illness, thanksgiving, worship, funeral, wedding, baptism), produce one complete prayer. Output in English only. Default output is plain text; use Markdown or DOCX only if the user requests it.

Defaults and overrides

  • Tradition: Evangelical unless the user specifies Reformed, Charismatic, Baptist, Non-denominational, or other. Avoid sect-specific jargon unless the user has specified a tradition.
  • Output format: Plain text by default; offer or use Markdown/DOCX only when the user asks.

Shared guidelines

  • Tone: dignified, gentle, reverent; clear and restrained; no mystical or esoteric language.
  • Where phrasing goes beyond clear biblical language, label it Reference application / not direct scripture (e.g. in a short note after the prayer or in brackets only if necessary for transparency).
  • Doctrine: avoid occult, extreme declarations, unorthodox terminology.

Output

  • One complete prayer text: address to God, thanksgiving or context, petitions, and closing (e.g. in Jesus’ name, Amen).
  • Length: suitable to be read aloud in 1–2 minutes unless the user asks for shorter or longer.
  • Use “you”/“your” for God; avoid overly informal or theatrical language.

Rules

  • Prayers must be theologically sound and consistent with orthodox Christian belief.
  • Do not assume denominational specifics (e.g. baptism mode, Lord’s Supper theology) unless the user specifies a tradition.
  • The prayer should be usable as-is or with minimal editing in the stated scenario (hospital, worship service, funeral, wedding, etc.).
  • If a phrase is inferred from general biblical themes rather than a direct quote, avoid overclaiming; optional note: (Reference application) for transparency.

Before use (funeral, wedding, and other personal occasions)

For funeral, wedding, baptism, or other highly personal settings, the pastor should tailor the wording before use: insert the correct names and relationships,...

Source information

Source
github
Repository
openclaw/skills
Path
skills/chenios/pastoral-prayer
Version
—
Commit
a0bf1bdda3eae53d9bc4d66d52f1b1ed3aed5acc
Classification source
rules
Status
active
Visibility
public

These signals come from indexed source analysis and may lag behind changes. Check the current source files.

Extracted content

SKILL.md
# Pastoral Prayer

When the user specifies a scenario (e.g. illness, thanksgiving, worship, funeral, wedding, baptism), produce one complete prayer. Output in English only. Default output is plain text; use Markdown or DOCX only if the user requests it.

## Defaults and overrides

- **Tradition:** Evangelical unless the user specifies Reformed, Charismatic, Baptist, Non-denominational, or other. Avoid sect-specific jargon unless the user has specified a tradition.
- **Output format:** Plain text by default; offer or use Markdown/DOCX only when the user asks.

## Shared guidelines

- Tone: dignified, gentle, reverent; clear and restrained; no mystical or esoteric language.
- Where phrasing goes beyond clear biblical language, label it **Reference application / not direct scripture** (e.g. in a short note after the prayer or in brackets only if necessary for transparency).
- Doctrine: avoid occult, extreme declarations, unorthodox terminology.

## Output

- One complete prayer text: address to God, thanksgiving or context, petitions, and closing (e.g. in Jesus’ name, Amen).
- Length: suitable to be read aloud in 1–2 minutes unless the user asks for shorter or longer.
- Use “you”/“your” for God; avoid overly informal or theatrical language.

## Rules

- Prayers must be theologically sound and consistent with orthodox Christian belief.
- Do not assume denominational specifics (e.g. baptism mode, Lord’s Supper theology) unless the user specifies a tradition.
- The prayer should be usable as-is or with minimal editing in the stated scenario (hospital, worship service, funeral, wedding, etc.).
- If a phrase is inferred from general biblical themes rather than a direct quote, avoid overclaiming; optional note: *(Reference application)* for transparency.

## Before use (funeral, wedding, and other personal occasions)

For funeral, wedding, baptism, or other highly personal settings, the pastor should tailor the wording before use: insert the correct names and relationships,...

Related skills

OpenClaw

x402hub

capncoconut

Register, communicate, and earn on the x402hub AI agent marketplace. Use when an agent needs to register on x402hub, browse or claim bounties, submit deliverables, send messages to other agents via x402 Relay,...

OpenClaw

claw

capevace

Real-time event bus for AI agents. Publish, subscribe, and share live signals across a network of agents with Unix-style simplicity.

OpenClaw

captchas-openclaw

captchasco

OpenClaw integration guidance for CAPTCHAS Agent API, including OpenResponses tool schemas and plugin tool registration.