What makes Ministry Weekly notable?

1.1K downloads. Trust evidence available

How should Ministry Weekly be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this agent.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

agentCLAWHUBUnverified

Ministry Weekly

Use this skill when a church staff user is actively producing weekly Sunday content. Specific triggers: 'generate this week's content package,' 'here's the b...

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

1.1k

Updated

Oct 11, 2026

Version

1.1.1

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 1.1K downloads reported by the source. Last updated 10/11/2026.

Avoid when

Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor: Clawhubvendor · observed Oct 11, 2026
Protocol compatibility: OpenClawcompatibility · observed Oct 11, 2026
Adoption signal: 1.1K downloadsadoption · observed Oct 11, 2026
Latest release: 1.1.1release · observed Jun 8, 2026
Handshake status: UNKNOWNsecurity

Install and run

Setup complexity: low.

clawhub skill install s17f63svb641q2stekk1cmcdn183k4rq:ministry-weekly

Install using `clawhub skill install s17f63svb641q2stekk1cmcdn183k4rq:ministry-weekly` in an isolated environment before connecting it to live workloads.
No published capability contract is available yet, so validate auth and request/response behavior manually.
Review the upstream CLAWHUB listing at https://clawhub.ai/chris/ministry-weekly before using production credentials.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-chris-ministry-weekly/snapshot"

Documentation

CLAWHUB

69,981 characters of source documentation, loaded on request.

Extracted files

5 files captured from the source.

SKILL.md

---
name: ministry-weekly
version: 1.1.1
description: "Use this skill when a church staff user is actively producing weekly Sunday content. Specific triggers: 'generate this week's content package,' 'here's the brief for Sunday,' 'sermon this week is [passage/title],' 'we're starting a new sermon series [title],' 'week [N] of the [series] series,' 'what have we covered in this series so far,' 'make me graphics for this week's sermon,' 'draft the weekly church email,' 'draft Sunday's bulletin,' 'social posts for this week's sermon,' 'update my church profile,' or 'send this package to the Telegram channel.' Do NOT trigger on casual mentions of church-related topics, personal religious questions, theology discussions, or general scripture lookups outside a weekly-content-production context. Covers: bulletin drafting, scripture context blocks with cross-references, platform-specific social posts (Facebook, Instagram, X, Threads, community group), the weekly church email, AI image generation prompts anchored to the series' graphics theme, sermon-series threading and recaps, and (optional) Telegram channel delivery of the assembled package. Persists church profile, sermon series history, and weekly briefs to a local JSON file."
metadata:
  openclaw:
    emoji: ✝️
---

# Ministry Weekly

You are a ministry communications assistant helping church staff eliminate the weekly content grind. Your job is to take a simple Sunday briefing and produce a complete, ready-to-use content package — no back-and-forth, no extra prompting needed.

The core promise: **one message in, full content package out.** Optional depth (scripture awareness, series threading, image prompts, Telegram delivery) layers on top without slowing the basic flow.

---

## Privacy and Data Handling

Be honest with the user about what this skill does. It directs the assistant to read and write a local file (`ministry-data.json`) for church profile, sermon series history, and weekly briefs. When the church profile lists Telegram as a delivery channel, it also directs the assistant to format and (after explicit user confirmation) post the assembled content package to that Telegram channel using whatever Telegram integration the user has configured in OpenClaw.

The skill itself ships no executable code, runs no background processes, makes no network calls of its own, and has no telemetry. The Telegram posting and any other external publishing happens through the user's own connected tools, under the user's credentials, with the user's explicit go-ahead per package.

**Data scope and consent rules**

- **Local storage by the skill**: `ministry-data.json` (church profile, sermon series, weekly briefs) is written to the user's working directory. Generated content packages are ephemeral unless the user says "save this brief" or "log this week."
- **Telegram delivery is opt-in and confirmation-gated**: even when Telegram is in `deliveryChannels`, the skill must format the package, present it, and a

README.md

# Ministry Weekly

An OpenClaw skill that turns a one-message Sunday briefing into a complete weekly content package for church staff. Bulletin, scripture context, platform-specific social posts, email, image prompts for graphics, and (when applicable) a sermon series recap. One shot, no back-and-forth.

**Current version: 1.1.1**

## What's new in 1.1.1

- Rewrote the **Privacy and Data Handling** section in SKILL.md to accurately describe Telegram delivery and external-channel scope (rather than understating it)
- Added a **Permissions and Privacy** section to this README so users see scope, the Telegram confirmation gate, and the no-congregant-PII rule before installing
- Narrowed the activation triggers in `description` to require an explicit weekly-content-production context, with a "do NOT trigger" guard against casual church-topic chat and general scripture lookups

## What's new in 1.1.0

- **Church Profile**: a one-time setup that captures church name, tradition, voice, audience, service times, and social channels — so the skill stops asking the same questions every week
- **Sermon Series Threading**: recognizes when a brief is part of an active series and carries context forward week to week (callbacks, current week, recap on demand)
- **Platform-Specific Social Posts**: distinct posts for Facebook, Instagram, X, Threads, and a members-only community group — each optimized for that platform, replacing the previous generic "Facebook or Instagram" output
- **Scripture Context Block**: a 4-6 sentence factual context block for the week's passage with cross-references and an optional discussion question
- **Image Generation Prompts**: ready-to-use prompts for AI image tools (Midjourney, DALL-E, Firefly) covering sermon slide, IG square, and vertical story formats, anchored to the series' graphics theme
- **Series Recap**: a built-in series-level view ("where we've been, where we are, where we're going") for catch-up emails and post-service posts
- **Liturgical sensitivity**: optional liturgy block in the bulletin for traditions that use one
- **Telegram delivery hook**: format and send the full package to a configured Telegram channel after generation
- **Data persistence**: `ministry-data.json` stores church profile, sermon series history, and weekly briefs across sessions

See [CHANGELOG.md](CHANGELOG.md) for the full release history.

## What It Does

Give it a sermon title, scripture, and any announcements. It returns a complete weekly content package:

1. **Bulletin Draft** — clean, formatted, optional liturgy block for liturgical traditions
2. **Scripture Context** — short factual context block with cross-references and a discussion question
3. **Platform-Specific Social Posts** — Facebook (3 posts: mid-week, day-of, post-service), Instagram (caption + story prompts), X (thread + quote tweet), Threads (mini-thread), community/members group (discussion-focused)
4. **Weekly Email** — 150-250 word email with subject line, optional segment

_meta.json

{
  "ownerId": "kn77r9qjvh6fy4aja2km8bzgvd83khv9",
  "slug": "ministry-weekly",
  "version": "1.1.1",
  "publishedAt": 1780960591164
}

CHANGELOG.md

# Changelog

All notable changes to this skill will be documented in this file.

The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and this skill adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## [1.1.1] — 2026-06-08

### Added
- **Privacy and Data Handling** section in SKILL.md describing assistant-mediated reads/writes against `ministry-data.json` and honest disclosure of the (opt-in, confirmation-gated) Telegram delivery instruction; adds an explicit no-congregant-PII rule (no named prayer requests, attendance, or giving records)
- **Permissions and Privacy** section in README.md so users see the scope (local file write, optional confirmation-gated Telegram delivery, social/email outputs as drafts only) and congregant privacy rules before installing

### Changed
- Narrowed the activation triggers in the `description` frontmatter to require an explicit weekly-content-production context (sermon brief, series management, specific output requests), with a "do NOT trigger" guardrail for casual church-related chat, theology discussions, and general scripture lookups
- Unquoted the `version` field in frontmatter (matches updated ClawHub CLI semver requirements)

## [1.1.0] — 2026-05-12

### Added
- **Church Profile** (one-time setup): captures church name, tradition, audience, voice preferences, service times, social handles, and delivery channels, then auto-applies to every weekly brief
- **Sermon Series Threading**: recognizes when a brief is part of an active series, carries context forward week to week with optional callbacks, and maintains a current-week pointer
- **Series Recap** generation on demand: produces "where we've been, where we are, where we're going" summaries for catch-up emails and mid-series posts
- **Scripture Context Block**: 4-6 sentence factual context with 1-2 cross-references and an optional discussion question; included in the weekly output and available standalone
- **Platform-Specific Social Posts**: separate, optimized posts for Facebook (3 posts), Instagram (caption + story prompts), X (thread + quote tweet), Threads (mini-thread), and a community/members group post; replaces the previous "three posts that work on Facebook or Instagram"
- **Image Generation Prompts**: ready-to-use prompts for AI image tools covering sermon slide, IG square, vertical story, and optional scripture quote graphic; anchored to the active series' `graphicsTheme` for visual consistency
- **Optional Liturgy Block** in the bulletin for traditions that use one (anglican, lutheran, mainline)
- **Telegram Delivery Hook**: format and send the full package to a configured Telegram channel after generation
- **Data Persistence**: `ministry-data.json` stores church profile, sermon series, and weekly brief history across sessions
- **Optional email segments**: youth/family note, volunteer prompt, prayer request invitation

### Changed
- Frontmatter `version` field now quoted as a string per ClawHub

skill-card.md

## Description:

Ministry Weekly helps church staff turn a Sunday briefing into a weekly content package with bulletin copy, scripture context, platform-specific social posts, email, image prompts, sermon-series recap, and optional confirmation-gated Telegram delivery.

This skill is ready for commercial/non-commercial use.

## Publisher:

[chris](https://clawhub.ai/user/chris)

### License/Terms of Use:

MIT-0

## Use Case:

External church staff and ministry communicators use this skill to produce weekly Sunday communications from a concise sermon brief. It supports bulletin drafts, social posts, email announcements, image-generation prompts, sermon-series continuity, and optional Telegram delivery after user confirmation.

### Deployment Geography for Use:

Global

## Known Risks and Mitigations:

Risk: The skill stores church profile, sermon series history, and weekly planning history in a local ministry-data.json file.

Mitigation: Use it only where local ministry planning data is acceptable, and keep congregant PII, giving records, attendance lists, and identifiable prayer requests out of the workflow.

Risk: Optional Telegram delivery can publish the assembled package through the user's configured Telegram integration.

Mitigation: Configure Telegram only when desired, review the package first, and require explicit confirmation before each post.

Risk: Generated ministry copy, scripture context, and image prompts may need pastoral, theological, or brand review before publication.

Mitigation: Review all drafts before use, keep scripture context factual and tradition-neutral, and publish social or email content manually unless the confirmed Telegram path is intentionally used.

## Reference(s):

- [ClawHub Skill Page](https://clawhub.ai/chris/skills/ministry-weekly)
- [Publisher Profile](https://clawhub.ai/user/chris)
- [README](artifact/README.md)
- [Changelog](artifact/CHANGELOG.md)

## Skill Output:

**Output Type(s):** [Text, Markdown, Configuration, Guidance]

**Output Format:** [Markdown-style structured content package with labeled sections and optional JSON-backed local state]

**Output Parameters:** [1D]

**Other Properties Related to Output:** [Produces drafts for user review; optional Telegram posting is confirmation-gated and uses the user's configured integration.]

## Skill Version(s):

1.1.1 (source: frontmatter, README, changelog, ClawHub release evidence)

## Ethical Considerations:

Users should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.

Github ReposUpdated 2d agoRank 70

AionUi

Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!

MCPOPENCLAW

Github ReposUpdated 6mo agoRank 70

activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

OPENCLAW

Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.