Team shared skill library

Goal: Stand up a small shared library with five starter skills, clear owners, and test-before-production edits.

Best for: 2–15 person teams that repeat the same AI chores weekly.

A library is a folder (Notion/Drive/git) with a one-page index: skill name, owner, when to use, link. Start with 5 skills, not 50. Each skill needs an owner who updates it when the process changes—and a version note (versioning). Without owners and a “how to try” card, the library becomes a graveyard of half-working prompts.

Why beginners skip this

Keeping skills private feels like less coordination—teammates will re-hit the same traps. Shared library + boundaries + version.

Step 1 — Pick the first five

Vote the five most painful repeat jobs first (status mail, repro asks, notes→actions)—do not start with an empty library.

Our weekly AI chores:
[list]
Recommend 5 starter skills for a shared library.
For each: name · owner role · success look · 1 risk (draft-only / needs-approval).

Team folder has 11 skills; 4 unused 30+ days; 1 can send Slack.
Draft shared-library hygiene: inventory, owner per skill, monthly prune, no orphan send skills.
Return a 8-bullet playbook for tomorrow standup.

Step 2 — Index page template

Build an index table with at least: name, one-line purpose, link, owner, version, last review, risk.

Draft a markdown index table for our skill library with columns Name, Use, Link, Owner, Version, Last reviewed, Risk.
Add a “How to propose a new skill” section in 5 lines.

Library audit: 11 skills, 4 unused 30+ days, one can post to #customers.
Playbook: owner column, prune rule, ban orphan send skills.
8 bullets for standup.

Step 3 — Review rhythm

Calendar: 15 minutes every two weeks. Archive unused skills. Click through one example each. Silent edits without a version bump create drift—see anti-patterns.

Write a 15-minute biweekly review agenda for a skill library (beginner team).
Include archive decision + one live example test.

15-minute biweekly skill library review agenda for a 6-person ops+PM team.
Context: live job for skills-team-shared-library — “keep a small shared set of skills so teammates stop” Keep never-invent / draft-only.

Index or graveyard

Owner + version + risk column—or the library becomes a prompt cemetery.

Close the loop

Write one line: next time I keep a skill private with no share, I refuse siloed work.

Red flag

Skill lands with no owner or version—reject until both exist.

Save this card

Card: owner · version · purpose sentence. No owner, no land in the shared library.

Before you start

Open the skill card (or blank one-pager). Purpose must be one job for “keep a small shared set of skills so teammates.” Golden example slot cannot stay empty. Guide: skills-team-shared-library. Keep the real job visible the whole time; a blank box means stop and fetch the artifact first.

How to use this week

This week put a real skill in the shared library: boundaries, version, fixture all three; no “shareable” until all three land.

Close the week by quoting aloud the refuse line you actually used once. If you cannot, rerun Practice now and date the pass/fail (Asia/Shanghai).

Pitfalls

Temptation: skip the habit for skills-team-shared-library to save five minutes.
Job still: keep a small shared set of skills so
Smallest correct pass: Done visible · checkable artifact · Unknowns [?].
Boundaries: draft only; no silent send; no invented metrics.
Return: artifact + refuse-line said aloud.

Practice now

Review SLA: max days before a shared skill gets review (Asia/Shanghai).

Library drill: add ownership + version to one shared skill card (Asia/Shanghai).

Thin-spot drill: rewrite the Save card with real nouns from your work (repo, doc, inbox). Generic placeholders fail the drill.

Tonight set three-line naming+version+owner rules; ingest one real skill by those rules.

Reality check: after Practice now, write one sentence you will refuse next time—and keep it on the Save card dated Asia/Shanghai.

Today card (copy) — skills-team-shared-library: 1. Artifact I will produce: ___ 2. Pass/fail check: ___ 3. Refuse-line if tempted to skip verify/send: ___ (date: Asia/Shanghai) 4. One never-do from this guide: ___

Extra pass: do the card on a real file today—reading alone does not count.

One sentence takeaway

Shared library: boundaries, version, fixture all three; no “shareable” until all three.

Next

Versioning and changelog · Skill anti-patterns · Package for teammates

团队共享 Skill 库

目标： 用五个起步 skill、清晰负责人，以及「先测再改生产副本」的流程，撑起小团队共享库。

适合： 6 人左右的运维/产品小队，想避免口口相传和直接改线上副本的人。

库会自己变胖。双周 15 分钟回顾要含归档，不只含新增。

为什么新手跳过

各自私藏 skill 像省协调；队友会重复踩坑。共享库 + 边界 + 版本。

步骤 1——先定五个

先投票选出最痛的五个重复活：状态邮件、复现提问、会议变行动项之类；别一上来建空库。

我们每周的 AI 杂务：
[列表]
推荐 5 个共享库起步 skill。
每个：名称 · 负责人角色 · 成功长什么样 · 1 个风险（仅草稿 / 需批准）。

杂务：客户状态邮件、会议→行动、竞品速览、PR 说明草稿、双语打磨。
请给 5 个起步 skill，并加风险标签。严格只要五个。
边界：不编造；未知标 [?]；发送前停下。
完成检查：一分钟内能判过/不过。

步骤 2——索引页模板

做一张索引表，至少包括：名称、一句话用途、链接、负责人、版本、上次审阅、风险等级。

起草 skill 库 Markdown 索引表，列：名称、用途、链接、负责人、版本、上次审阅、风险。
再加「如何提议新 skill」5 行。

请写 5 步：新队友如何找到、测试、反馈共享 skill，并且不直接改生产副本。
分支 → 测试 → 类似 PR 再替换。
边界：不编造；未知标 [?]；发送前停下。
完成检查：一分钟内能判过/不过。

步骤 3——回顾节奏

在日历上钉死每两周 15 分钟：不用的归档掉，每次会点开一个例子现场跑一遍。有人偷偷改生产副本却不升版本，库会悄悄漂移；详见反模式。

写 15 分钟双周回顾议程（入门团队的 skill 库）。
含归档决定 + 一次现场例子测试。

请为 6 人运维+产品团队写一份 15 分钟的双周 skill 库回顾议程。
背景：这是本周真实工作。要求：不编造；只出草稿；新手也要能看懂。
边界：不编造；未知标 [?]；发送前停下。
完成检查：一分钟内能判过/不过。

索引或坟场

每条 skill 都要写清负责人、版本和风险列，不然这个库很快会变成提示词公墓。

闭环

写下一行：下次私藏 skill 不共享，我拒绝再各干各的。

红旗

各自私藏 skill，队友会重复踩坑；共享库 + 边界 + 版本。

保存这张卡

记下：skill 名 + 版本号 + 红线夹具是否测过。标上日期。

开始前

信任该 skill 前，先确认已有完成标准 + 一个实例。

本周怎么用

本周把一个真 skill 放进共享库：边界、版本、夹具三件齐；缺一件不宣布可共享。

常见坑

现在就练一次

今晚就练：把一个真 skill 放进共享库：边界、版本、夹具三件齐；缺一件不宣布可共享。

一句话带走

共享库：边界、版本、夹具三件齐；缺一件不宣布可共享。

下一步

版本与变更说明 · Skill 反模式 · 打包给队友