technical-publishing skillA
technical-publishing is agent-read markdown (skill) from fmind/dot: Prepare and publish technical articles with verified content, canonical exports, and channel copy..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Publish Technical Articles Publish technical articles from package sources through review, canonical web publication, and channel copy. Third-party documentation sites and static websites use project-local documentation tooling, while software releases use [release](../git-delivery/references/release/GUIDE.md). Run the project-owned CLI from the publishing checkout: ```bash mise run pub -- init article <slug> # scaffold directories and draft mise run pub -- check <package> --publish-ready # offline readiness gate mise run pub -- publish <package> --site <site-directory> --dry-run # preview publication ``` ## Workflow 1. **Read the project contract first**: inspect its `AGENTS.md`, current CLI help, and local publishing skill for the requested deliverable. The [package overview](references/packages.md) is orientation, not a replacement for the current schema or publication policy. 1. **Package pipeline**: prepare and review the article and channel deliverables inside the package before publication; `draft.txt` contains raw notes that agents never edit; see [Package layout](references/packages.md). …
Read the whole file at its exact version.
How to install
mdr add fmind/dot/technical-publishing@git:20260923.2988db2mdr add fmind/dot/technical-publishing@sha256:87212c88d05a9c83Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_l22masbacopwgvpw)
0 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260923.2988db2 latest | 2026-09-23 | 2988db2 | 3,632 B | A | view · diff |
| git:20260916.50d6810 | 2026-09-16 | 50d6810 | 3,229 B | A | view · diff |
| git:20260913.ef23060 | 2026-09-13 | ef23060 | 3,180 B | A | view · diff |
| git:20260909.17296ea | 2026-09-09 | 17296ea | 2,942 B | A | view · diff |
| git:20260906.ede7325 | 2026-09-06 | ede7325 | 2,550 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 (3632 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
fmind/dot · 9 stars · license MIT · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_l22masbacopwgvpw GET https://markdownregistry.com/api/v1/resolve?ref=fmind/dot/technical-publishing GET https://markdownregistry.com/api/v1/blob/87212c88d05a9c83c21dc5b0dc99d0e4e5123da4b36da41752ff0392ce8725ca
Your agent 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.