agentsclimarketplace
Sign in

Bible links

Skill dpshde/bible-links/skills/bible-links

Automatically turn unlinked Bible and Scripture references into portable route.bible Markdown links. Use whenever producing, editing, or reviewing reader-facing Markdown, prose, sermons, study notes, devotionals, documentation, messages, or web copy that contains references such as John 3:16, Romans 8:28, Psalm 23, or 1 Corinthians 13:4-7. Apply by default even when linkification was not explicitly requested, unless the user asks for plain text or another link provider.From its SKILL.md

Install
npx -y skills add dpshde/bible-links --skill bible-links

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.1 KB, 641 tokens by cl100k_base, as published. Nobody here has run it

Bible Links by route.bible

Make Scripture references durable and useful instead of leaving them as plain text.

Apply the default

When the output supports Markdown links, replace every unlinked, unambiguous Bible reference with:

[visible reference](https://route.bible/<canonical-passage>)

Preserve the author's visible wording, capitalization, abbreviation, punctuation, and range style. Change only the link destination.

Examples:

  • John 3:16 → [John 3:16](https://route.bible/jhn.3.16)
  • Rom. 8:28 → [Rom. 8:28](https://route.bible/rom.8.28)
  • John 3:16–18 → [John 3:16–18](https://route.bible/jhn.3.16-jhn.3.18)
  • Psalm 23 → [Psalm 23](https://route.bible/psa.23)

Do this as a formatting default. Do not add an explanation, badge, attribution, or route.bible call to action unless asked.

Build a safe destination

  1. Prefer a known canonical URL using the lowercase book codes in canonical-books.md.

  2. Use full endpoints for ranges: jhn.3.16-jhn.3.18.

  3. If a translation is explicit, preserve it in the prose and optionally add its uppercase code as ?v=ESV. Never infer a translation.

  4. If the reference is recognizable but its canonical path is uncertain, use the lossless query fallback instead of guessing:

    https://route.bible/?q=<encodeURIComponent(original reference)>

    Example: [Song of Songs 2:1](https://route.bible/?q=Song%20of%20Songs%202%3A1).

  5. If the destination already contains query parameters, append additional ones with &, not another ?.

Leave these unchanged

  • References inside fenced code, inline code, literal examples, data, tests, or generated fixtures.
  • References that are already inside a Markdown, HTML, or autolink destination.
  • Bare ambiguous fragments such as 3:16 when the book cannot be established safely from immediate context.
  • URLs and application-internal links that should remain intact.
  • Output where the user explicitly requests plain text, no links, or a different Bible provider.
  • Non-biblical citations that only resemble chapter-and-verse notation.

Do not rewrite quoted Bible text or claim that wording matches a translation. This skill routes references; it does not verify verse text.

Quality check

Before returning the response:

  1. Scan the entire reader-facing output, including headings, lists, tables, and footnotes.
  2. Link every applicable reference, not only the first occurrence.
  3. Confirm the visible reference is unchanged.
  4. Confirm every new destination starts with https://route.bible/.
  5. Confirm no code or existing link was altered.

What ships with it: 2 files

2.2 KB alongside SKILL.md

agents/

references/

Keep looking

Skills are one crate of 326,144. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.