oss-growth-attribution SKILL.md skillA
oss-growth-attribution from gingiris-1031/gingiris-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add gingiris-1031/gingiris-skills/oss-growth-attribution@git:20261015.68deea2Pins git:20261015.68deea2 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- gingiris-1031/gingiris-skills
- Path
skills/oss-growth-attribution/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261015.68deea2, committed Oct 15, 2026
- First version recorded
- Aug 18, 2026
- Size
- 3,858 bytes
- Repository stars
- 91
- License
- MIT
Reconstruct an open-source project's growth channels, key content, and stage-by-stage attribution from GitHub history and public web evidence. Use this skill when asked to research GitHub star growth, identify launch and amplification channels, explain viral milestones, find representative posts or videos, compare Product Hunt/Show HN/Reddit/KOL impact, or produce an evidence-backed OSS growth attribution report.
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
# OSS Growth Attribution Produce an auditable growth reconstruction, not a generic marketing checklist. ## Workflow 1. Resolve the canonical repository and validate it against the product domain. 2. Fetch GitHub repository metadata, releases, earliest commits, and timestamped stargazers. 3. Build a star timeline with daily resolution around spikes and monthly resolution elsewhere. 4. Search GitHub Trending, Reddit, Hacker News, Product Hunt, X, LinkedIn, Instagram, TikTok, YouTube, developer media, technical blogs, and localized communities. 5. Extract original content URLs; never substitute search-result URLs when an original URL is available. 6. Normalize items to [the evidence schema](references/evidence-schema.md). 7. Align publication times with star velocity using [the attribution model](references/attribution-model.md). 8. Divide history into preparation, community seed, accumulation, breakout, localization/SEO, and ecosystem stages. Omit unsupported stages. 9. Report representative content per channel with hook, format, audience, funnel role, and original link. 10. List channels searched but not evidenced. Absence of public evidence is not proof an event never happened. …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_yaybwfp4gloqryst/6cf32e7143cfe643d828a4db08e62258c176dead13bd9cbfbac378f85bbfc10c.json
Then /plugin install oss-growth-attribution@markdownregistry-yaybwfp4gloqryst in Claude Code. It installs git:20261015.68deea2, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add gingiris-1031/gingiris-skills/oss-growth-attribution@sha256:6cf32e7143cfe643The line at the top of this page pins the label git:20261015.68deea2, 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_yaybwfp4gloqryst)
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 gingiris-1031/gingiris-skills/oss-growth-attribution 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 oss-growth-attribution from somewhere else? Ask it: where did my oss-growth-attribution 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 Aug 18, 2026 and Oct 15, 2026, about one every 57 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261015.68deea2 latest | 2026-10-15 | 68deea2 | 3,858 B | A | view · diff |
| git:20260818.cd8ff37 | 2026-08-18 | cd8ff37 | 3,037 B | A | view |
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/oss-growth-attribution/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 (3858 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
gingiris-1031/gingiris-skills · 91 stars · license MIT · pushed 2026-11-17 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_yaybwfp4gloqryst GET https://markdownregistry.com/api/v1/resolve?ref=gingiris-1031/gingiris-skills/oss-growth-attribution GET https://markdownregistry.com/api/v1/blob/6cf32e7143cfe643d828a4db08e62258c176dead13bd9cbfbac378f85bbfc10c
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.