gr-oss-marketing SKILL.md skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.
gr-oss-marketing 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/gr-oss-marketing@v0.2.0Pins v0.2.0 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/gr-oss-marketing/SKILL.md- Versions recorded
- 7
- Latest version
- v0.2.0, committed Oct 15, 2026
- First version recorded
- Apr 17, 2026
- Size
- 6,961 bytes
- Repository stars
- 91
- License
- MIT
开源项目发布与场景主题营销,含 Web/CLI 数据采集验证。覆盖 GitHub star 增长、KOL 合作、Reddit / HN / Discord / Telegram 社群分发、 多语言落地(中英日韩)。从 gingiris-opensource 提炼。适用场景:要发布一个开源项目, 想在 6 个月内冲 10k star,或已发布但流量卡住要破局。.
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
# gr-oss-marketing — 开源营销 ## 先执行:发布契约 在给渠道建议前,输出 `Go / Fix / No-Go` 表,检查:定位、陌生人 Quick Start、 可复现 Demo、License/安全/隐私、发布周响应 owner、Star 之后的激活与商业承接。 任何关键项为 No-Go 时先修复,不用铺量掩盖产品问题。 把源 TODO 表统一成 5 个视图: 1. 研究表:ICP、社区规则、近期高质量内容、风险、核验日期。 2. 内容表:原生角度、证据、素材、CTA、审批、状态。 3. 分发表:Owner、账号、当地时间与时区、UTM/source、实际链接。 4. 数据表:基线、2h、24h、72h、7d、成本、结论。 5. 总控表:依赖、Go/No-Go、事故 owner、停止条件、复盘日期。 统一漏斗为 `曝光 → repo 访问 → install/quickstart → activation → D7 → contributor/qualified lead → paid`。Star 只是开发者兴趣信号。原生指标缺失时写 `数据不可用`,不得从曝光或互动推算。 红线:不买 Star/账号、不刷榜或协调虚假 Upvote、不隐藏付费合作、不批量骚扰、 不让 AI 冒充真人参与社区。Reddit/HN/Discord/群组逐个核对规则并披露关联。 ## 什么时候用 - "我要发一个开源项目,从 0 怎么起" - "GitHub star 增长卡在 xxx 不动了" - "如何找开发者 KOL 合作" - "Reddit / HN 怎么发不被 ban" - "如何做 dev.to / Zenn / CSDN 内容矩阵" --- ## 核心框架(3 阶段) ### 阶段 1:Pre-launch(T-30 到 T-0) - [ ] README 起好(英文主,首屏截图 < 3s 读懂) - [ ] Demo video ≤ 60s,有字幕 - [ ] License 选对(MIT/Apache-2/AGPL 各有陷阱) - [ ] 3-5 个早鸟 maintainer / contributor - [ ] 社群频道就位(Discord 或 Telegram,英文为主) ### 阶段 2:Launch(T-0 到 T+14) - [ ] Product Hunt 发(联动 `gr-ph-launch`) - [ ] Hacker News Show HN(只有真实技术新意且团队能在线答疑时;发布时间按近期同类帖验证) - [ ] Reddit:选 3 个相关 sub(r/selfhosted / r/programming / 细分技术 sub) …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_mrffchtghd2qdxfa/20a4d822e041820c862e1453fe1ec047356c352c4ab5869aedad257900d4e3c7.json
Then /plugin install gr-oss-marketing@markdownregistry-mrffchtghd2qdxfa in Claude Code. It installs v0.2.0, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add gingiris-1031/gingiris-skills/gr-oss-marketing@sha256:20a4d822e041820cThe line at the top of this page pins the label v0.2.0, 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_mrffchtghd2qdxfa)
3 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/gr-oss-marketing 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 gr-oss-marketing from somewhere else? Ask it: where did my gr-oss-marketing 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 7 versions of this file, between Apr 17, 2026 and Oct 15, 2026, about one every 30 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v0.2.0 latest | 2026-10-15 | 68deea2 | 6,961 B | A | view · diff |
| v0.2.0 | 2026-10-08 | 0e5c75a | 6,140 B | A | view · diff |
| v0.1.0 | 2026-09-20 | 1204478 | 5,673 B | A | view · diff |
| v0.1.0 | 2026-07-06 | 6f73c2e | 4,422 B | A | view · diff |
| v0.1.0 | 2026-06-18 | ff8c0b8 | 3,070 B | A | view · diff |
| v0.1.0 | 2026-06-16 | fccec03 | 2,832 B | A | view · diff |
| v0.1.0 | 2026-04-17 | 72183c2 | 2,797 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/gr-oss-marketing/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 (6961 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_mrffchtghd2qdxfa GET https://markdownregistry.com/api/v1/resolve?ref=gingiris-1031/gingiris-skills/gr-oss-marketing GET https://markdownregistry.com/api/v1/blob/20a4d822e041820c862e1453fe1ec047356c352c4ab5869aedad257900d4e3c7
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 gingiris-1031/gingiris-skills
Every file in gingiris-1031/gingiris-skills