team-motivation-ops SKILL.md skillA
team-motivation-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/team-motivation-ops@git:20261108.f22c340Pins git:20261108.f22c340 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/team-motivation-ops/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261108.f22c340, committed Nov 8, 2026
- First version recorded
- Jul 27, 2026
- Size
- 11,355 bytes
- Repository stars
- 91
- License
- MIT
Your team has high autonomy — and standups are vague, weekly meetings drift into status reports, and 1:1s produce nothing but "I'm fine." This playbook fixes all three layers at once. What's inside: • Daily Standup system — 3-field format, good sample, 4 COO principles to keep it honest • Weekly Meeting — strict 25-min agenda, Scrum Master rotation, 0–10 pulse check • 1:1 Framework — 9-dimension quantified pulse, 5-group deep question bank, bilateral feedback structure • Diagnostic layer —…
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
> 🌍 **Language / 语言**: [中文](#团队-motivation-操作手册) | [English](references/en/README.md) | [日本語](references/ja/README.md) | [한국어](references/ko/README.md) # 团队 Motivation 操作手册 > 这套体系的底层逻辑:自由和责任是一体的。Standup 是让人想清楚,例会是让人对齐,1:1 是让人被看见。三件事做好了,motivation 不是管出来的,是长出来的。 适用场景:AI 科技公司 COO 或团队负责人,团队规模 3-30 人,高自由度、远程或半远程。 与产研运 SOP 的边界:本 Skill 诊断个人状态、信息和对齐;需求优先级、Bug、迭代范围与发布门禁交给 `gr-product-dev-ops`。1:1 发现的问题只有进入明确负责人、截止时间和验证方式的 Action Item,才算闭环。 --- ## 第一层:每日 Standup — 信息层 ### 设计哲学 Standup 的本质不是汇报,是一种强迫自己想清楚的仪式。写得出来,说明真想清楚了;写不出来,通常是因为自己也没搞清楚今天要干什么。 含糊是会传染的——COO 自己的 standup 要先写好,模式从上往下渗透。 ### 标准格式(三个必填项) 1. **今天做了什么**:具体交付,不写「继续开发」 2. **明天要做什么**:具体到别人能判断你做没做完 3. **遇到什么困难 / 晚上要聊什么**:卡点、ownership 不清楚的事 ### 好 Standup 样本 ``` 今天做了什么 - 把 XX 接口写完,本地 50 条数据跑通,平均 80ms,比上一版快一倍 - 帮队友定位 WhatsApp 会话列表渲染卡顿,根源是没做虚拟滚动,指了 react-window 方案,他十分钟搞定 - 实话实说,下午摸鱼了一小时,顺手把竞品新发的 case study 存进竞品库,算将功补过 明天要做什么 - 把批量报价接口推上 staging,拿真实场景跑一遍 - 补今天没写的接口文档 遇到什么困难 / 晚上要聊 - XXX 架构决策还没拍板,影响我这边进度,想今晚对一下 ``` ### COO 使用原则 - 不要求写完美,要求写真实。摸鱼了就写摸鱼了,但写清楚摸鱼之外做了什么。 - 不批评短 standup,但要追问「今天具体交付了什么」。问题在具体性,不在长度。 - 公开表扬一条好 standup,不批评烂的。具体也会传染。 - 好 standup 是送给队友的礼物,这个认知要反复说。 --- ## 第二层:每周例会 — 对齐层 ### 设计哲学 …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_xf2uwqlbftmhklpk/06b146996ca2f944fcce32d38b7d48847df149aff4694494dae5d60e0862810a.json
Then /plugin install team-motivation-ops@markdownregistry-xf2uwqlbftmhklpk in Claude Code. It installs git:20261108.f22c340, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add gingiris-1031/gingiris-skills/team-motivation-ops@sha256:06b146996ca2f944The line at the top of this page pins the label git:20261108.f22c340, 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_xf2uwqlbftmhklpk)
4 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/team-motivation-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 team-motivation-ops from somewhere else? Ask it: where did my team-motivation-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 4 versions of this file, between Jul 27, 2026 and Nov 8, 2026, about one every 35 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261108.f22c340 latest | 2026-11-08 | f22c340 | 11,355 B | A | view · diff |
| git:20261015.68deea2 | 2026-10-15 | 68deea2 | 11,323 B | A | view · diff |
| git:20260814.12f81b9 | 2026-08-14 | 12f81b9 | 10,502 B | A | view · diff |
| git:20260727.bb743df | 2026-07-27 | bb743df | 10,232 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/team-motivation-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 (11355 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_xf2uwqlbftmhklpk GET https://markdownregistry.com/api/v1/resolve?ref=gingiris-1031/gingiris-skills/team-motivation-ops GET https://markdownregistry.com/api/v1/blob/06b146996ca2f944fcce32d38b7d48847df149aff4694494dae5d60e0862810a
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.