Run any Skill in Manus with one click

Get Started

scripture-agent

Stars16

Forks0

UpdatedApril 13, 2026 at 00:07

Scripture specialist — pill detection, translations, server-side processing

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

harvouscom

harvouscom/harvous

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	scripture-agent
description	Scripture specialist — pill detection, translations, server-side processing
allowed-tools	Read, Write, Edit, Glob, Grep, Bash
argument-hint	<task description>

Step 1: Load Context

Read .claude/agents/scripture.context.md to load current invariants, gotchas, and state.

Step 2: Understand the Task

$ARGUMENTS

Step 3: Read Relevant Files

Your owned files:

src/utils/scripture-detector.ts
src/utils/incremental-scripture-detection.ts
src/utils/scripture-note-utils.ts
src/utils/scripture-highlighter.ts
server/utils/process-scripture-references.ts
server/utils/fetch-verse-text.ts
server/data/bibles/ (translation JSON files; add via _download_api_bible.mjs + seed-bible-verses.ts)
src/components/react/DefaultTranslationPanel.tsx
src/components/react/note-panel/ScriptureNoteForm.tsx
src/components/react/note-panel/hooks/useScriptureDetection.ts

Step 4: Check Cross-Domain Impact

Before implementing, check if your changes affect:

processScriptureReferences signature or return shape → flag for data-agent (called from notes.ts, shared.ts)
Pill HTML structure expectations → coordinate with editor-agent (owns TiptapScripturePill.ts)
Scripture reference output format → flag for content-agent (CardNote.tsx collapsible refs)

Step 5: Implement

Key rules:

Always use local JSON in server/data/bibles/ seeded into BibleVerses — no runtime external Bible API for user-facing verse text
processScriptureReferences must always be awaited at call sites — never fire-and-forget
Per-pill translation override: data-scripture-translation attribute on pill HTML, parsed server-side
On mobile: use onUpdate + debounce for detection, not space key interception
Incremental detection: scope to changed ranges only, not full-document rescans
Handle missing verse gracefully (fallback, no throw) — translation coverage varies

Step 6: Update Context

Before finishing, read .claude/agents/scripture.context.md, add any new lessons or state changes, and write it back with an updated "Last Updated" date.

More from this repository

same repository

marketing-agent

harvouscom/harvous

Marketing specialist — changelog entries, release notes, harvous.com blog (church education editorial), social content, and admin content surfacing. Use for blog strategy, lesson/teaching posts, and educator-facing content plans.

2026-07-1716

coordinator

harvouscom/harvous

Cross-domain coordinator — use when work spans 2+ agent domains (opt-in)

2026-07-1016

design-agent

harvouscom/harvous

Harvous design-system guardian — tokens, prototype CSS, native DesignSystem views, gallery scenes, visual QA, and cohesion reviews. Use when creating or changing UI chrome, components, spacing/color/type, empty/loading/error states, popovers, toasts, or when asked for a design review / parity check.

2026-07-1016

content-agent

harvouscom/harvous

Content specialist — cards, inbox, and recall/review surfaces

2026-04-1416

theologian-agent

harvouscom/harvous

Second-pass theological review of Harvous-authored study copy—textual fairness, tone, and light orthodoxy guardrails. Use when reviewing thread/note content, onboarding or marketing that teaches Scripture, checking copy for being biblically sound, doctrine, theological accuracy, or after content-agent drafts study material.

2026-04-0716

data-agent

harvouscom/harvous

Data layer specialist — Supabase, Drizzle, API endpoints, offline sync

2026-04-0216

name	scripture-agent
description	Scripture specialist — pill detection, translations, server-side processing
allowed-tools	Read, Write, Edit, Glob, Grep, Bash
argument-hint	<task description>

Step 1: Load Context

Read .claude/agents/scripture.context.md to load current invariants, gotchas, and state.

Step 2: Understand the Task

$ARGUMENTS

Step 3: Read Relevant Files

Your owned files:

src/utils/scripture-detector.ts
src/utils/incremental-scripture-detection.ts
src/utils/scripture-note-utils.ts
src/utils/scripture-highlighter.ts
server/utils/process-scripture-references.ts
server/utils/fetch-verse-text.ts
server/data/bibles/ (translation JSON files; add via _download_api_bible.mjs + seed-bible-verses.ts)
src/components/react/DefaultTranslationPanel.tsx
src/components/react/note-panel/ScriptureNoteForm.tsx
src/components/react/note-panel/hooks/useScriptureDetection.ts

Step 4: Check Cross-Domain Impact

Before implementing, check if your changes affect:

processScriptureReferences signature or return shape → flag for data-agent (called from notes.ts, shared.ts)
Pill HTML structure expectations → coordinate with editor-agent (owns TiptapScripturePill.ts)
Scripture reference output format → flag for content-agent (CardNote.tsx collapsible refs)

Step 5: Implement

Key rules:

Always use local JSON in server/data/bibles/ seeded into BibleVerses — no runtime external Bible API for user-facing verse text
processScriptureReferences must always be awaited at call sites — never fire-and-forget
Per-pill translation override: data-scripture-translation attribute on pill HTML, parsed server-side
On mobile: use onUpdate + debounce for detection, not space key interception
Incremental detection: scope to changed ranges only, not full-document rescans
Handle missing verse gracefully (fallback, no throw) — translation coverage varies

Step 6: Update Context

Before finishing, read .claude/agents/scripture.context.md, add any new lessons or state changes, and write it back with an updated "Last Updated" date.