gr-ai-content-ops SKILL.md skillA
gr-ai-content-ops 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-ai-content-ops@v1.5.0Pins v1.5.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-ai-content-ops/SKILL.md- Versions recorded
- 2
- Latest version
- v1.5.0, committed Nov 15, 2026
- First version recorded
- Nov 12, 2026
- Size
- 16,910 bytes
- Repository stars
- 91
- License
- MIT
Build or audit an evidence-led AI content operation: competitor research, SEO/GEO keyword and content positioning, source libraries, channel roles, weekly calendars, editorial gates, repurposing, distribution receipts and business measurement. Use when planning 内容运营、内容矩阵、周排期、多平台分发、素材库 and content workflow recovery, 选题、内容日历、内容SOP、一鱼多吃、内容复盘 and publishing receipts. For a single supplied article rewrite, keep the scope to that deliverable.
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
# AI Content Operations / AI 内容运营 Turn real material into a manageable content operation whose delivery and outcomes can be checked. Work in the user's language. Deliver the requested scope; a single-platform team does not need a multi-channel matrix. ## Start with the reader's reason to care The primary editorial goal is useful, engaging content for the intended reader. Workflow completion, word count, keywords and publishing volume are supporting constraints, not evidence of good content. Before choosing a format or drafting, identify a concrete reader situation, what is at stake, and the new understanding or useful outcome the piece delivers. Use actual customer questions, sales/support conversations, relevant audience discussions and observed content responses where available. Label inferred audience needs; don't pretend an imagined persona has validated them. …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_fkvs4z36i2rfzxr4/042a4c0e4b158a7ed7e8c89ae32938374b8a3718f04f85e6728decf85d04563a.json
Then /plugin install gr-ai-content-ops@markdownregistry-fkvs4z36i2rfzxr4 in Claude Code. It installs v1.5.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-ai-content-ops@sha256:042a4c0e4b158a7eThe line at the top of this page pins the label v1.5.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_fkvs4z36i2rfzxr4)
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/gr-ai-content-ops 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-ai-content-ops from somewhere else? Ask it: where did my gr-ai-content-ops 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 12, 2026 and Nov 15, 2026, about one every 3 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.5.0 latest | 2026-11-15 | 1f223dd | 16,910 B | A | view · diff |
| v1.0.0 | 2026-11-12 | 0ae9dfe | 8,668 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-ai-content-ops/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 (16910 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_fkvs4z36i2rfzxr4 GET https://markdownregistry.com/api/v1/resolve?ref=gingiris-1031/gingiris-skills/gr-ai-content-ops GET https://markdownregistry.com/api/v1/blob/042a4c0e4b158a7ed7e8c89ae32938374b8a3718f04f85e6728decf85d04563a
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.