做什么
将客户的实际生产部署转化为技术案例研究 工程师们相信 - 测量数字与如何测量, 前后结构,公布限制, 并清除命名和引用批准
技能库 智客分类:运维与云 developer-case-study
将客户的真实生产部署转化为技术案例研究工程师们认为——测量数字与测量方法挂钩,前后结构,公布限制,并清除命名和引用批准. 每当用户提到客户案例研究,技术案例研究,开发者收养或成功故事,参考客户,或想将用户采访,迁移或出品推出变成已公布的证明时使用——即使他们只说"关于Acme如何利用我们的文章". 使用 Samber/developer-relations-skills@engineering-blog-post;为您自己的项目进行中的进展使用 Samber/developer-relations-skills@building-in-public.
官方网址:skills.sh
先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。
将客户的实际生产部署转化为技术案例研究 工程师们相信 - 测量数字与如何测量, 前后结构,公布限制, 并清除命名和引用批准
用户提到客户案例研究、技术案例研究、开发商领养或成功故事、参考客户, 或想将用户访谈、迁移或生产推广变成公布的证据, 这样做
按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:Developer Case Study、Scope check、Interview、Workflow、Invocation examples、Story qualification gates。 其中含规范建议的小节:分步指令、输入输出示例、边界情况。
文件分析:除 SKILL.md 外,正文引用了 references/source-interview-guide.md、references/case-study-outline.md、references/approval-and-anonymization.md、references/evidence-and-sources.md,属于带资源的技能包,这些文件按需再读。
Turns a customer's real production deployment into a technical case study engineers believe - measured numbers tied to how they were measured, before-and-after architecture, published limitations, and cleared naming and quote approval. Use whenever the user mentions a customer case study, a technical case study, a developer adoption or success story, a reference customer, or wants to turn a user interview, migration or production rollout into published proof - even if they only say "a post about how Acme uses us". Do NOT use for a post about your own system - use samber/developer-relations-skills@engineering-blog-post; for your own project's ongoing progress use samber/developer-relations-skills@build-in-public.
Developer Case StudyScope checkInterviewWorkflowInvocation examplesStory qualification gatesWhich story to chase firstNumber disciplineThe spineLimitations are the differentiationApproval trackHumanizer pass
· 许可:MIT
来源分类:skills.sh agent-skill
namedeveloper-case-studydescriptionreferences/source-interview-guide.mdreferences/case-study-outline.mdreferences/approval-and-anonymization.mdreferences/evidence-and-sources.md以下路径提取自原文;文件是否齐全请以来源仓库中的完整目录为准。
具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗
先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。
该技能引用了附属文件,请从来源获取完整目录;仅复制 SKILL.md 可能缺少依赖。
复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。
把 Agent Skill「developer-case-study」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-8e669b44ac9ec58b-%E5%BC%80%E5%8F%91%E8%80%85%E6%A1%88%E4%BE%8B%E7%A0%94%E7%A9%B6.html 请存为 .cursor/skills/developer-case-study/SKILL.md 或 .claude/skills/developer-case-study/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。 该技能还带 scripts/、references/、assets/ 等文件,请从 https://github.com/samber/developer-relations-skills 取完整目录,不要只建一个 SKILL.md。
需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。
npx skills add 'https://github.com/samber/developer-relations-skills' --list
npx skills add 'https://github.com/samber/developer-relations-skills' --skill 'developer-case-study'
CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。
You are writing someone else's engineering story. A developer case study says: these engineers ran this technology in production, here is what changed, here is what it cost them. The reader is an engineer deciding whether the same move works in their own system - not a buyer looking for reassurance.
That reader discounts an all-upside narrative on sight. Your leverage is evidence discipline and honesty about the parts that hurt, not prose polish.
Confirm the artefact before starting. Route elsewhere when:
See the References section for the exact identifiers.
Ask the case-study owner these before touching the story, one question at a time, multiple-choice where you can. Stop as soon as you can judge whether the story is publishable.
If your harness has persistent memory, store the answers to 5, 6 and 7. Those are per-customer and per-program conventions that stay true across every story you write with them.
Unless the user asks for something else, deliver six parts in this order:
Produce the verdict and the ledger before any drafting. A ledger built after the prose is a ledger written to justify it.
Five gates - this skill's own checklist, not a published standard. A publishable story clears all five:
Failing one gate does not always mean no story:
When several adopters could carry a study, the choice is not which one is most impressive - it is which one returns the most published proof per hour spent, counting the customer's own time and goodwill as the scarcest input. Adopter type predicts both sides of that ratio, so rank candidates by it and chase in this order.
The value line assumes the reader is evaluating for a team inside a company. It inverts when the product's own adopters are solo developers and maintainers - then the indie story is the strongest proof available and the enterprise one reads as irrelevant. Re-rank against who actually buys before using the default.
In efficiency order, with what each type costs and buys, and the craft difference each forces:
What this order starves is the named enterprise production reference: the strongest proof available to a reader who has to justify the choice internally, and the most expensive story on the list in both legal review and customer goodwill. An efficiency ranking demotes it every quarter, and the story bank fills with small stories that never move an enterprise evaluation. Promote it above everything when a live deal is stalled for want of a peer reference at that size, or when the coverage table's enterprise row is empty - that gap has no cheap substitute, and three startup studies do not add up to one.
Delete rather than demote. A customer whose legal team will not approve a public reference is removed from the candidate list, not parked at the bottom. Keep them only if a rung of the anonymization ladder still clears the qualification gates.
Otherwise, the candidate is gone: a "maybe next quarter" name keeps consuming account-team asks and the relationship capital that goes with them. A candidate still in evaluation rather than production is deleted the same way, since it fails the first gate and waiting for it is not a plan.
This order is a default, not a law: it shifts with context and with who chases the story.
Every number carries four attributes or it does not ship:
| Evidence class | What you have | How to write it | | ------------------ | ------------------------------------------------ | ------------------------------------------------- | | Measured | Both sides from the same instrument | State it directly, with the instrument and window | | Partially measured | After-value instrumented, before-value estimated | State it, and mark the estimate as an estimate | | Reported | The customer's number, uninstrumented | Attribute it: "the team estimates…" | | Directional | Only a qualitative claim survived | Drop the number; use the engineer's own words |
Two well-sourced numbers beat six loose ones. Ratios travel better than absolutes when the customer will not clear absolutes ("cut infra cost by a third"), and cycle-time and reliability figures travel better than raw volume, because a reader can compare them to their own system without knowing the customer's scale.
Don't:
Hold this skill's own numbers to the same rule. ./references/evidence-and-sources.md splits every threshold in this file into sourced or self-set. Quote a self-set baseline only as a working baseline - never to an adopter as an industry standard.
Published studies converge on Challenge / Solution / Results: four independent instances carry the same three beats - two vendor studies and two generic marketing-skill templates (sources in ./references/evidence-and-sources.md). Keep them, and add the three those templates leave out: alternatives rejected, metric provenance, limitations.
The word budgets below are self-set proportions for a 1,200-1,800-word target - itself self-set, chosen to sit just under the three measured vendor studies (~1,650, ~2,100 and ~2,400 words, none with a dedicated limitations section). Scale them to the material.
Sections 4, 5 and 7 are what separate this from a testimonial. If the material only fills 1, 2, 6 and 8, you have a quote card - publish it as one.
Read ./references/case-study-outline.md for the per-section guidance and worked positive/negative examples before drafting. The examples there (Acme, the Grafana figures) are invented illustrations, not measured cases - never cite them as evidence.
A limitation is a cost the reader would inherit, not a plan.
Roadmap: "We plan to consolidate the two languages."
Cost: "We shipped the orchestration layer in Go while the rest of the team
writes Python, and that split is now a hiring constraint."
One of the compared studies carries three of the former and none of the latter - do not accept that trade.
The gap is a publisher's choice, not a genre constraint. Across the four compared studies - a small sample, and both vendor ones from the same vendor:
Section lists and sources: ./references/evidence-and-sources.md.
Fill the section from the interview:
State who should not copy this architecture.
Read the contract's publicity clause before asking anyone for anything. Standard self-serve SaaS terms often already license the customer's name and logo and the statement that they are a customer - Vercel's terms carry such a clause, quoted verbatim in ./references/approval-and-anonymization.md.
The clause grants nothing else:
Ask for exactly what it leaves open.
Four permissions remain, often held by four different people:
Ask who holds each at first contact.
Pre-redact what security review predictably strikes:
Send the full draft with the decisions marked, a dated deadline, and a stated default.
When naming is refused, descend the anonymization ladder one rung at a time rather than dropping the story:
Each rung costs credibility, and the last one is no longer a case study.
This ladder is deliberately not ranked by effort or efficiency: the rungs are not alternatives anyone picks between, since every one below the top is cheaper only because someone refused the one above it. Take the highest rung approval allows, and read the descent as loss, not as a trade-off.
Full ladder, redaction classes and a request template: ./references/approval-and-anonymization.md.
Run the prose through your preferred humanizer skill before the gate. Model-flavoured filler reads as vendor copy, which is the register this artefact most needs to avoid.
Preserve exactly as written: every quote, every number, version strings, component names and the architecture description. A humanised quote is a fabricated quote.
Seven checks - a working gate, not a published standard. Hold the study until all seven pass. Report which check failed and what you changed, then re-check.
Then two human reads happen before publishing:
One approved study feeds several artefacts. Ask which are needed before approval, so permission covers them, and build them in reuse-per-hour order - every rung below reuses material the approved study already cleared, so the ranking is about where the reuse lands, not about writing effort:
File the study's atoms - each metric, each quote, the architecture diagram - into a proof library alongside the narrative, with a public/private flag. Assets built later pull from the atoms; nobody re-reads a 1,500-word study to find one number.
Republication in a paid or ad context usually needs its own permission. Re-verify any study older than roughly 18 months before reusing it - a self-set convention, not a measured shelf life; shorten it for adopters who ship fast or churn.
| Symptom | Cause | Fix | | ------------------------------------- | --------------------------------------------------- | ------------------------------------------------------------------------------------ | | Reads like a testimonial | Only sections 1, 2, 6, 8 have material | Go back for alternatives, architecture, cost - or publish a quote card | | Customer strikes half the numbers | Metrics never had provenance | Rebuild each metric with instrument and window, resubmit | | Approval stalls for weeks | Review chain engaged after drafting | Open the approval track at first contact; set a dated default | | Engineers dispute it publicly | Architecture written from vendor assumption | Have the interviewed engineer confirm the technical sections | | Quotes sound like marketing | Paraphrased instead of transcribed | Restore verbatim from the recording; accept the customer's own edits | | Story dies after the interview | Qualification gates skipped | Run the gates before booking the call | | Numbers overclaim | Product credited for a multi-change rollout | Name everything else that changed in the same window | | Customer disputes an "approved" study | The contract's logo clause read as blanket approval | Treat the clause as name and logo only; get quotes, metrics and narrative separately | | Limitations section says nothing | Roadmap items accepted as costs | Ask again for engineer-weeks, dual-running, what broke - a plan is not a cost | | Churned customer's study still live | No re-verification date set at publication | Date every study, re-verify on schedule, unpublish rather than leave it up |
Judge a study on whether it moved evaluations forward, not on traffic. No published metric isolates case studies aimed specifically at developers: general B2B-technology-buyer research puts vendor-produced case studies well behind product demos and free trials for buying-decision impact (see ./references/evidence-and-sources.md), but nothing narrower than that exists. Treat the signals below as things to weigh, never targets to hit:
Do not attribute revenue to a single case study. Overclaiming attribution is the same credibility failure the artefact exists to avoid.
运维与云
用于容器管理,图像操作,调试的基本道克命令和工作流程.
运维与云
从开放的代理技能生态系统中发现并安装技能. 使用时:(1)用户问"我如何做X",X可能拥有现有技能,(2)用户说"为X找到技能"或"是否为X有技能",(3)用户问"你能否做X",X是专门能力,(4)用户想扩展代理能力,(5)用户想搜索工具,模板,或工作流程,(6)用户提到他们希望…
运维与云
构建,部署,评价,优化,微调,管理微软创始代理,模型,资源最终结束. 用法:铸造、azd ai代理、azd 提供/部署、托管代理脚手架/开发/运行/部署/拖放、即时代理创建、创建代理、更新代理、添加代理工具、援引代理、代理.yaml、评估代理、批量活化、连续活化、持续监测、代理C…
运维与云
执行已有.azure/部署计划.md和基础设施文件的ALREADY-PREPARED应用程序的Azure部署。 当用户向 CREATE 请求新应用程序时, 请不要使用此技能 。 这种技能运行了 azd上行, azd 部署, trarraform 应用, 和 az 部署命令带有内置…