github-surface skillA
github-surface is agent-read markdown (skill) from wangchangxin0809/cc-repo-harness: Write what GitHub itself reads: README, CONTRIBUTING, the community-health files (SECURITY, CODE_OF_CONDUCT, LICENSE, issue and PR templates) and the workflows under .github/workflows/. Use when creating or rewriting any of these, when Community Standards reports a gap, when adding or reviewing CI, or when a repository goes public. Not for docs/, which is writing-docs..
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
# The GitHub surface Three documents answering three different questions. Mixing them is the expensive mistake in this category, because the result reads complete. | File | Answers | Reader | Failure mode | |---|---|---|---| | `README.md` | What is this, and how do I run it | Someone passing through | Becomes a shrunken architecture document | | `CONTRIBUTING.md` | How do I take part, and what do you want | Someone about to change it | **Becomes a second quick start** | | Community health | Conduct, disclosure, licence, templates | The platform, and outside arrivals | Missing — and GitHub publishes the gap for you | **Writing CONTRIBUTING as a second quick start is the standard failure.** It reads fine: install the dependencies, run it, here is the directory layout. And every single thing that actually stops a contributor is absent — who reviews their pull request, how long before anyone replies, what kind of change will simply not be accepted, where to send a vulnerability. Unable to answer those, they guess, or they leave. ## These files need conventions of their own `docs/` conventions are designed for someone already inside: a scope header …
Read the whole file at its exact version.
How to install
mdr add wangchangxin0809/cc-repo-harness/github-surface@git:20260903.c1a383cmdr add wangchangxin0809/cc-repo-harness/github-surface@sha256:93d666bbeeeac125Pin 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_ibkoxxithi5zetfk)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260903.c1a383c latest | 2026-09-03 | c1a383c | 10,219 B | A | view · diff |
| git:20260902.0375378 | 2026-09-02 | 0375378 | 10,367 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 (10219 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
wangchangxin0809/cc-repo-harness · 5 stars · license MIT · pushed 2026-09-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ibkoxxithi5zetfk GET https://markdownregistry.com/api/v1/resolve?ref=wangchangxin0809/cc-repo-harness/github-surface GET https://markdownregistry.com/api/v1/blob/93d666bbeeeac12593c99ec68bac86f504c9097f5655cbc513e75e2ed265736f
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.