ci-for-your-solution SKILL.md skillA
This file is byte-identical to the first copy the registry indexed, one of 3 indexed copies. Same content hash, so the same checks give both the same grade.
ci-for-your-solution from leanmeancleanapps/cleanwebapi is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add leanmeancleanapps/cleanwebapi/ci-for-your-solution@git:20261117.e3cfdd4Pins git:20261117.e3cfdd4 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- leanmeancleanapps/cleanwebapi
- Path
.agents/skills/ci-for-your-solution/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261117.e3cfdd4, committed Nov 17, 2026
- First version recorded
- Nov 5, 2026
- Size
- 5,080 bytes
- Repository stars
- 4
- License
- MIT
How CI works in a solution made from this template - the ci.yml that dotnet new ships, the Build Pipeline a "Use this template" copy keeps, and how to add security scans or a container check, or move the pipeline to Azure Pipelines, GitLab or another CI system. Use when CI fails on a fresh solution, when adding a check, or when the engineer asks how to set up CI anywhere other than GitHub Actions.
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
# CI for your solution ## The rule Every solution starts with a simple pipeline that runs the commands in `AGENTS.md`: format, build, and test with the 95% coverage gate. It needs no secrets, no paid features and no setup, so it's green on the first push. Anything more is added on purpose, with the engineer, one check at a time. | Made with | Pipeline | What runs | | --- | --- | --- | | `dotnet new` | `.github/workflows/ci.yml` | Restore, format, build, test and the coverage gate | | "Use this template" on GitHub | `.github/workflows/build-pipeline.yml`, the template's own | Format, build and test. The scans and the template's pack, verify and release jobs only run in the LeanMeanCleanApps organisation, and show as not run anywhere else | The **Set up CI** guide for your template on the [Lean Mean Clean Apps docs site](https://leanmeanclean.dev/) shows both, and links the template's full Build Pipeline as a worked example of every check below. ## Adding a check | Check | Local command | Fails when | Needs | | --- | --- | --- | --- | …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_v2oxxqeod4gyvums/1958b615cfd9c21aa2a119a5a6fd2614a289350e419fdc2e8129b46e4b7bace3.json
Then /plugin install ci-for-your-solution@markdownregistry-v2oxxqeod4gyvums in Claude Code. It installs git:20261117.e3cfdd4, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add leanmeancleanapps/cleanwebapi/ci-for-your-solution@sha256:1958b615cfd9c21aThe line at the top of this page pins the label git:20261117.e3cfdd4, 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_v2oxxqeod4gyvums)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in leanmeancleanapps/cleanwebapi/ci-for-your-solution since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of ci-for-your-solution from somewhere else? Ask it: where did my ci-for-your-solution come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 2 versions of this file, between Nov 5, 2026 and Nov 17, 2026, about one every 12 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261117.e3cfdd4 latest | 2026-11-17 | e3cfdd4 | 5,080 B | A | view · diff |
| git:20261105.583c434 | 2026-11-05 | 583c434 | 5,090 B | A | view |
Copies
2 files in 2 other repositories hold the exact bytes of one of this file's versions, each committed after this file had them: all of them hold the newest version.
A copy does not update when this file does. Whoever holds one can learn which version it is with the Check your copy box below, or by asking their agent. Matched on exact bytes and commit dates only.
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/ci-for-your-solution/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
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 (5080 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
leanmeancleanapps/cleanwebapi · 4 stars · license MIT · pushed 2026-11-17 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_v2oxxqeod4gyvums GET https://markdownregistry.com/api/v1/resolve?ref=leanmeancleanapps/cleanwebapi/ci-for-your-solution GET https://markdownregistry.com/api/v1/blob/1958b615cfd9c21aa2a119a5a6fd2614a289350e419fdc2e8129b46e4b7bace3
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.
More from leanmeancleanapps/cleanwebapi
Every file in leanmeancleanapps/cleanwebapi
Other files named ci-for-your-solution
Browse by kind, by grade A, or by owner.
Kept in .agents/skills, the folder Codex reads. More agent skills for Codex.