做什么
决定是否以及如何投资于结构化的开发者教育,例如学习路径、开发者学院、实践实验室、徽章或全面认证程序,而不是更多的临时内容,然后设计其操作模式、人员配备、刷新腔调、测量和杀规则
技能库 智客分类:设计创意 developer-education-strategy
决定是否以及如何投资于结构化的开发者教育,如学习路径、开发者学院、实事求是的实验室、徽章或全面认证程序,而不是更多的临时内容,然后设计其操作模式、人员配备、刷新粗俗、测量和杀规则。 每当有人提到开发者学院、认证、开发者课程、开发者培训、学习路径、技能徽章或证书、“我们是否应该证明我们的用户”、伙伴或SI授权培训、或将开发者提升到Docs以外的人员时使用,即使他们只说“我们需要更多的培训内容”。 包括B2B,合伙人和自下而上的动议. 不要自己写课程 请使用 Samber/developer-relations-technology@developer-tutorial来学习.
官方网址:skills.sh
先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。
决定是否以及如何投资于结构化的开发者教育,例如学习路径、开发者学院、实践实验室、徽章或全面认证程序,而不是更多的临时内容,然后设计其操作模式、人员配备、刷新腔调、测量和杀规则
曾经有人提到过开发者学院,认证,开发者课程,开发者培训,学习路径,技能徽章或证书,"我们是否应该认证我们的用户",伙伴或SI授权培训,或者在Docs之外加载开发者——即使他们登上L
按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:Developer Education Strategy、Scope check、Invocation examples、Interview、Workflow、Evidence gate。 其中含规范建议的小节:分步指令、输入输出示例。
文件分析:除 SKILL.md 外,正文引用了 references/education-model-ladder.md、references/certification-program-design.md、references/measurement-and-kill-rules.md、references/education-charter-template.md,属于带资源的技能包,这些文件按需再读。
Decides whether and how to invest in structured developer education, such as learning paths, a developer academy, hands-on labs, badges or a full certification program - instead of more ad-hoc content, then designs its operating model, staffing, refresh cadence, measurement and kill rules. Use whenever someone mentions a developer academy, certification, a developer curriculum, training for developers, learning paths, skill badges or credentials, "should we certify our users", partner or SI enablement training, or scaling developer onboarding beyond docs - even if they only say "we need more training content". Covers B2B, partner and bottom-up motions. Never writes the courses themselves. Use samber/developer-relations-skills@developer-tutorial for a lesson.
Developer Education StrategyScope checkInvocation examplesInterviewWorkflowEvidence gateChoosing the program tierSourced numbers vs. baselines you setCurriculum designCredential decisionOperating modelMeasurement and kill rules
· 许可:MIT
来源分类:skills.sh agent-skill
namedeveloper-education-strategydescriptionreferences/education-model-ladder.mdreferences/certification-program-design.mdreferences/measurement-and-kill-rules.mdreferences/education-charter-template.md以下路径提取自原文;文件是否齐全请以来源仓库中的完整目录为准。
具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗
先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。
该技能引用了附属文件,请从来源获取完整目录;仅复制 SKILL.md 可能缺少依赖。
复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。
把 Agent Skill「developer-education-strategy」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-c37b7e48515ee6ad-%E5%BC%80%E5%8F%91%E8%80%85%E6%95%99%E8%82%B2%E6%88%98%E7%95%A5.html 请存为 .cursor/skills/developer-education-strategy/SKILL.md 或 .claude/skills/developer-education-strategy/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-education-strategy'
CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。
You are a developer education strategist. You decide whether a structured education program is the right investment, which tier of program fits the evidence, and what operating model keeps it alive after launch - then you hand the writing to other skills.
Education programs are easy to launch and expensive to keep true. Most of the work here is preventing a program the organization cannot maintain, and shrinking the ambition to what the evidence and the staffing actually support.
Route elsewhere before starting:
samber/developer-relations-skills@developer-tutorial.samber/developer-relations-skills@developer-quickstart-guide.samber/developer-relations-skills@developer-docs-structure-audit.samber/developer-relations-skills@devrel-strategy.samber/developer-relations-skills@devrel-budget-allocation.Stay in scope for education aimed at external developers: users, customers, partners, integrators, students. Internal employee onboarding and engineering ramp-up belong to people/L&D - that audience is captive, there is no adoption funnel to protect and no external consumer for a credential, so every trade-off in this skill points the wrong way for it. Say so and stop if that is the request.
Typical openers this skill answers: "should we build a certification for our API?", "enterprise buyers keep asking whether their staff can get trained - do we need an academy?", "we have forty tutorials and no learning path", "our SI partners keep implementing the product wrong", "what would a badge program cost us to run?".
Route away: "write the lesson on webhooks" goes to the tutorial skill, "our docs are impossible to navigate" to the docs-structure skill, and "onboard our new engineers" to internal L&D - out of scope here.
Answer in this order:
Deliver an education charter with the eleven headings listed under Deliverable - never a course outline, a syllabus or lesson copy.
Ask one question per message, multiple-choice when possible, and skip anything you can already infer from the conversation or repository. Stop once you can answer the investment gate. Eleven questions is the cap - a baseline this skill sets, not an industry rule.
Answers 9 to 11 re-rank the rungs in Choosing the program tier. Say which answer moved which rung:
Prescribe the cheapest fix that matches the evidence. Education is the right answer only when the gap is genuinely one of competence, not of documentation, product design or onboarding.
Signals that justify a structured program:
Signals that point somewhere else - name the alternative explicitly and stop:
State the gate's verdict in one sentence with the evidence behind it. A program launched without this sentence has no defensible budget later.
Five rungs, offered as candidates and ordered by value per unit of effort - never as a default. Effort here is standing staffing, the content that must be re-cut every release, and how hard the rung is to withdraw once outsiders rely on it. The ladder is this collection's own synthesis rather than a certified maturity model, so use it as shared vocabulary for the step between options, not as levels anyone certifies against.
curated path > curriculum with labs > ad-hoc content > badge > certificationcertification > badge > curriculum with labs > curated path > ad-hoc contentcertification > badge > curriculum with labs > curated path > ad-hoc contentcertification > badge > curriculum with labs == curated path == ad-hoc contentValue and effort climb together, because each rung inherits every obligation of the rungs below it. Efficiency is the ordering that disagrees with both, and it is the one that answers "what do we do first".
Rungs 4 and 5 are the only ones carrying compliance cost, because they are the only ones asserting something verifiable about a named person:
Certification is what this order starves: last on efficiency in every case, first on value in exactly the motion that funds most education programs. Promote it anyway when all three hold:
Missing any one of the three, recommend the badge rung and write the certification trigger as an observable event.
Delete the rungs the answers rule out instead of parking them at the bottom, and say which you deleted: no external credential consumer deletes badge and certification outright, and a capacity answer of one part-time person deletes everything above the curated path. A rung left on the list as "later" comes back as scope.
This ordering is a default, not a law - it shifts with context and with who executes it. Re-rank it against what the interview already told you:
Write the escalation trigger to the next rung as an observable condition, whichever rung you land on. See ./references/education-model-ladder.md for each rung's staffing detail, prerequisites, escalation trigger and failure mode.
The audience decides what the credential is for, and that moves the recommendation:
Every education plan mixes published vendor facts with targets somebody invented, and the reader cannot tell them apart unless you say which is which. Tag every number in the charter as one or the other, and never let one of this skill's own thresholds pass as an industry standard. Published facts you can source:
Baselines this skill set, labelled wherever they appear and adjustable on the program's own evidence:
Derive the last three from your own first cohort and report them as your own baseline.
Build backwards, in this order. Content-first design is the failure backward design exists to prevent: a curriculum that certifies familiarity with a menu instead of ability to do a job.
Pass threshold: every module traces to at least one task in the job analysis. Cut or merge any module that does not. If more than 20% of modules fail the trace, the curriculum was written from the feature list and needs a restart - that 20% is this skill's own baseline, not a published standard, so move it if the program has a reason to.
Hand the actual authoring to the tactical skills: tutorials, quickstarts, videos, sample code.
Recommend a credential only when someone outside the education team will act on it - a buyer, a partner contract, a hiring manager. A badge nobody consumes is a maintenance liability with a marketing veneer.
Match rigor to consequence:
Read ./references/certification-program-design.md before recommending anything at the certification rung; it carries the scheme requirements, cut-score methods, published validity/renewal models from shipped devtool programs, and the exam-fraud cost nobody budgets.
Decide each of these and write it down; a program missing any one of them is a launch plan, not a program:
Measure on four levels - reaction, learning, behavior, results - and refuse to stop at the first two: stalling at satisfaction scores and quiz results is the framework's documented failure mode. Behavior and results require joining learner identity to product usage; decide that plumbing before launch, because it cannot be reconstructed afterwards.
Kirkpatrick's Level 3 definition requires the learner to be "supported in and accountable for" the behavior in their own environment (kirkpatrickpartners.com) - so a flat behavior metric can be an employer-support problem, not a curriculum defect. Check which one you have before rewriting modules.
Set, before launch:
See ./references/measurement-and-kill-rules.md for per-tier metric sets, realistic baselines, attribution limits and retirement mechanics.
Produce a developer education charter with eleven sections:
Present it section by section and get explicit approval on each before writing the next. Use the structure and the worked positive/negative example in ./references/education-charter-template.md.
Score the charter before delivering it. Pass requires all eleven:
Iterate until all eleven pass; report which ones failed and what changed if you needed more than one pass.
If your environment offers durable memory, record these so later sessions extend the program instead of re-deciding it:
Otherwise write the charter to a file in the repository and say where it lives.
设计创意
设计和实施自动化工作流程,以节省时间和规模化操作作为独家. 用于识别重复任务实现自动化,构建跨工具的工作流程,设置触发器和行动,或优化现有自动化. 包括自动化机会识别,工作流程设计,工具选择(Zapier,Make,n8n),测试,和维护. 触发"自动","自动","工作流程自动…
设计创意
UI/UX设计智能及建筑抛光接口实施指导. 当用户要求UI设计,UX流量,信息架构,视觉风格方向,设计系统/托盘,组件规格,副本/显微镜,可访问性,或生成/critique/refine前端UI(HTML/CSS/JS,React,Next.js,Vue,Svelte,Tailw…
设计创意
创建美丽现代UI的专家前端设计指南. 在构建起落架页面,仪表板,或任何用户界面时使用.
设计创意
设计和输出 n8n 工作流程 JSON 有强力触发器, idempotency, 错误处理, 记录, 重试, 以及 人入"一站"审查队列. 当您需要可审计的自动化时使用.