project-core-dev SKILL.md skillA
project-core-dev from n-n-code/n-n-code-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add n-n-code/n-n-code-skills/project-core-dev@git:20260819.151acd9Pins git:20260819.151acd9 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- n-n-code/n-n-code-skills
- Path
.agents/skills/project-core-dev/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260819.151acd9, committed Aug 19, 2026
- First version recorded
- Mar 31, 2026
- Size
- 1,599 bytes
- Repository stars
- 4
- License
- MIT
Project overlay for discovering and reporting repository-specific completion checks for routine repo-owned changes. Use when the validation path is unclear; prefer specialized project overlays for config, platform, release, or vendor concerns.
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
# Project Core Dev This is a thin project overlay, not a standalone implementation workflow. Use it with matching implementation guidance only when repository-specific checks or gaps remain unclear. Omit it when another selected skill plus repo context already supplies exact commands and reporting obligations. ## When to use The task is a routine repo-owned change whose completion path is not yet concrete. ## Not for Use `project-config-and-tests`, `project-platform-diagnose`, `project-release-maintainer`, or `project-vendor-boundary` when that specialized concern leads. Do not use this skill to restate a generic validation checklist. ## Completion Workflow 1. Read the applicable repository instructions, README, CI configuration, contributor docs, and presets. Identify authoritative commands and mandatory gates; do not invent a second workflow. 2. Map the touched surface to the narrowest honest repo-defined proof. Do not run broad checks merely because they exist. 3. Execute within the task's authority. Prefer check modes for read-only work; do not install tools, start services, or mutate the environment just to close a checklist. …
Read the whole file at its exact version.
How to install
mdr add n-n-code/n-n-code-skills/project-core-dev@sha256:55870902dbbbe9e2The line at the top of this page pins the label git:20260819.151acd9, 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_mhaxphgtrgj75c6y)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Mar 31, 2026 and Aug 19, 2026, about one every 35 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260819.151acd9 latest | 2026-08-19 | 151acd9 | 1,599 B | A | view · diff |
| git:20260423.b0aeb97 | 2026-04-23 | b0aeb97 | 1,476 B | A | view · diff |
| git:20260405.002addc | 2026-04-05 | 002addc | 1,316 B | A | view · diff |
| git:20260402.c132152 | 2026-04-02 | c132152 | 1,340 B | A | view · diff |
| git:20260331.b0817a1 | 2026-03-31 | b0817a1 | 838 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 (1599 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
n-n-code/n-n-code-skills · 4 stars · license MIT · pushed 2026-11-01 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_mhaxphgtrgj75c6y GET https://markdownregistry.com/api/v1/resolve?ref=n-n-code/n-n-code-skills/project-core-dev GET https://markdownregistry.com/api/v1/blob/55870902dbbbe9e25d2545b16d53965c93f2ff39c0794a3550e05bbd9d5a50fe
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.