ls-github-release-publishing SKILL.md skillA
ls-github-release-publishing from cruxexperts/localsetup is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add cruxexperts/localsetup/ls-github-release-publishing@v1.2Pins v1.2 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- cruxexperts/localsetup
- Path
ls/skills/ls-github-release-publishing/SKILL.md- Versions recorded
- 1
- Latest version
- v1.2, committed Oct 21, 2026
- Size
- 16,689 bytes
- Repository stars
- 6
- License
- a license file GitHub does not identify
Use when publishing to GitHub, preparing a public release, or reviewing repo readiness. Covers public-doc structure, licensing, PII/secrets/path scrub, version checks, and repository settings.
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
# GitHub publishing workflow (framework baseline) **Purpose:** Follow a consistent, research-backed workflow to get a repo ready for public GitHub publication: documentation layout, licensing, scrub for sensitive or context-specific content, and a repeatable checklist. ## Documentation and structure (best practice) - **README:** Clear value proposition near the top; install instructions; layout of deployed content; optional contents table or TOC for navigation. Section headings that work as anchors. Consider light visual cues (e.g. section icons) for scanability; keep one H1 per doc. - **SECURITY.md:** How to report vulnerabilities (private advisory or contact). Link from repo Security tab. State scope (this repo only; third-party tools out of scope). - **CONTRIBUTING.md:** How to open Issues, Discussions, and PRs; repo layout; that contributions are licensed under the project license. Point to LICENSE. - **LICENSE:** Chosen license (e.g. MIT) with correct copyright holder. Single source for "can use, modify, distribute" terms. …
Read the whole file at its exact version.
How to install
mdr add cruxexperts/localsetup/ls-github-release-publishing@sha256:81db639756887af4The line at the top of this page pins the label v1.2, 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_blwgcvtwo5illkge)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 21, 2026.
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 (16689 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
cruxexperts/localsetup · 6 stars · license a license file GitHub does not identify · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_blwgcvtwo5illkge GET https://markdownregistry.com/api/v1/resolve?ref=cruxexperts/localsetup/ls-github-release-publishing GET https://markdownregistry.com/api/v1/blob/81db639756887af4c6a91fa0f20972c7c99c6a7e7dcc9133afa6ca3db260d034
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.