church-account_skill

This skill automates login and common tasks on churchofjesuschrist.org and LCR, streamlining session management and navigation.
  • Python

2.5k

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill church-account

  • _meta.json287 B
  • SKILL.md3.7 KB

Overview

This skill automates login and common tasks on churchofjesuschrist.org and LCR (Leader & Clerk Resources). It handles OAuth sign-in, session persistence, and navigation of key church services so scripts can read and update membership, callings, finance, and temple data. Built for headless browser automation, it focuses on reliable session reuse and access to core URLs.

How this skill works

The skill uses a Playwright-based OAuth flow targeting id.churchofjesuschrist.org to perform username and password entry, wait for redirects, and capture authenticated storage state. It applies stealth measures to reduce detection when running headless browsers. Once a storage state file is saved, the skill reuses that state to create new browser contexts without repeating credential entry. It also exposes the common service URLs and logical LCR sections for scripted navigation and actions.

When to use it

  • Automate logging into LCR or churchofjesuschrist.org programmatically
  • Fetch or sync ward and stake rosters and member directory data
  • Manage callings, view temple recommend status, or update ministering assignments
  • Automate finance-related tasks like tithing reports or donation lookups
  • Create scheduled jobs that require an authenticated church session

Best practices

  • Keep credentials in a secure vault or environment variables, never hard-code them
  • Save and protect storage_state files; they contain authentication tokens
  • Use Playwright with stealth settings to reduce bot detection when running headless
  • Respect privacy and church policies—only access data you are authorized to view
  • Add retry and timeout handling around navigation and waits to handle network delays

Example use cases

  • Headless job that logs in daily to export ward membership changes to a backup system
  • Scripted workflow to list and update current callings for clerks
  • Automated check of temple recommend status for active members in your unit
  • Periodic scrape of the member directory or calendar for integration with local tools
  • Finance report generator that logs in, downloads tithing settlement summaries, and archives them

FAQ

Typically the church OAuth flow does not require MFA or CAPTCHA for standard accounts; the skill does not implement MFA flows. If MFA is present, manual completion or additional automation is required.

How do I avoid re-authenticating on every run?

After a successful login, save the Playwright storage_state JSON. Reuse that file when creating a new browser context to skip the credential steps until the session expires.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational