maintain-splash-pages SKILL.md skillA
maintain-splash-pages from lossless-group/lossless-agent-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add lossless-group/lossless-agent-skills/maintain-splash-pages@git:20261102.148ae12Pins git:20261102.148ae12 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- lossless-group/lossless-agent-skills
- Path
maintain-splash-pages/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261102.148ae12, committed Nov 2, 2026
- First version recorded
- May 8, 2026
- Size
- 36,087 bytes
- Repository stars
- 4
- License
- MIT
The Lossless Group's pattern for repo-level splash pages — small Astro sites at <repo>/splash/ that ship to GitHub Pages on push to main, render the repo's changelog/ + context-v/ alongside curated marketing copy, and stay isolated from any package the repo also publishes. Use proactively whenever scaffolding a noteworthy new repo (every "important" repo wants one), when shipping a coherent chunk of work that an external reader would land on, when adding a feature…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Maintain Splash Pages > A splash is the source repo's own GitHub Pages presence — distinct from any future custom-domain marketing site. The directory is named `splash/` precisely to keep that linguistic space open. **Status: Draft.** This skill codifies the pattern after three confirmed instances. It pairs with a sibling **habit** titled *"Maintain a Github Splash Page for each Repo"* that explains the *why*; this skill is canonical for the *how*. The habit currently lives under `lossless-monorepo/context-v/habits/` but may move — search for it by title before assuming a path. Always cross-reference the most recent reference implementation (currently `lfm/splash/`) before scaffolding fresh. ## Reasoning step before implementation: does this repo deserve a splash? The convention is "every important repo." That word is doing work — not every repo earns one. Use this rough cut: **Yes, scaffold a splash:** - The repo will be shared with people outside the team (clients, collaborators, hiring loops, conference talks) - The repo has — or will have — a non-trivial `changelog/` worth surfacing …
Read the whole file at its exact version.
How to install
mdr add lossless-group/lossless-agent-skills/maintain-splash-pages@sha256:27589b55e05a224dThe line at the top of this page pins the label git:20261102.148ae12, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_e7r2rarzau6flbaj)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between May 8, 2026 and Nov 2, 2026, about one every 178 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261102.148ae12 latest | 2026-11-02 | 148ae12 | 36,087 B | A | view · diff |
| git:20260508.6839057 | 2026-05-08 | 6839057 | 35,468 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (36087 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
lossless-group/lossless-agent-skills · 4 stars · license MIT · pushed 2026-11-02 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_e7r2rarzau6flbaj GET https://markdownregistry.com/api/v1/resolve?ref=lossless-group/lossless-agent-skills/maintain-splash-pages GET https://markdownregistry.com/api/v1/blob/27589b55e05a224d53183cf31856e25f198ef2db680dd26c7a3163121514e924
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.