PlugWiki

developer-education-strategy skill (samber): decide on an academy or certification

Decides whether a developer academy, learning path, badge or certification is worth building, then writes the charter to run it.

Installs
12.8K
on skills.sh
Stars
7
on GitHub
Files
5
besides SKILL.md
Updated
Nov 2026
last repo commit

developer-education-strategy makes your agent test whether structured training is the right fix before you build any. It checks the evidence, picks one of five program tiers, and then writes an education charter with an operating model, measurement plan and kill rule.

It triggers on a developer academy, developer curriculum, learning paths, partner or SI enablement training, or "we need more training content". It is for external developers only. The folder holds SKILL.md and four reference files and bundles no scripts.

Good for

  • Developer education or DevRel leads asked whether to build an academy
  • Product and partner teams whose enterprise buyers ask for certified staff
  • Teams with plenty of tutorials and no learning path

Install developer-education-strategy

Claude Code

  1. 1

    Copy this prompt.

    Install the developer-education-strategy skill in Claude Code. Run this command:
    
    /plugin marketplace add samber/developer-relations-skills
    /plugin install developer-relations-skills@developer-relations-skills
    
    Then check that it loaded and tell me how to use it.
  2. 2

    Paste it into Claude Code. It shows the change and asks before running it.

The README recommends installing the whole collection because its skills reference each other, and developer-education-strategy names other skills in the collection to hand work to. The whole-collection routes add all 93 skills in the repo (counted from the git tree); the repo holds no hooks, agents, commands or MCP server files, and 14 of its skills bundle a script. Pick one route per agent.

From the project README. Source.

What's in the skill

When it loads

Decides whether and how to invest in structured developer education, such as learning paths, a developer academy, hands-on labs, or a badge or certification rung on top - 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, a developer curriculum, training for developers, learning paths, 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 courses - use samber/developer-relations-skills@developer-tutorial. Do NOT use for designing the credential itself - use samber/developer-relations-skills@developer-certification-program.

Sections in SKILL.md

  1. Scope check
  2. Invocation examples
  3. Interview
  4. Workflow
  5. Evidence gate
  6. Choosing the program tier
  7. Sourced numbers vs. baselines you set
  8. Curriculum design
  9. Credential decision
  10. Operating model
  11. Measurement and kill rules
  12. Deliverable
  13. Self-review scorecard
  14. Failure modes
  15. Persisting decisions
  16. References

Key facts

Installs on skills.sh
12,772 (as of Nov 2, 2026)
Version in SKILL.md
1.1.3

What it includes

  • Routes tutorials, quickstarts, docs structure and workshops to other skills first.

    It also stops if the request is internal employee onboarding, which SKILL.md leaves to people or L&D teams.

    Scope check

  • Asks up to eleven questions, one per message, then runs the investment gate.

    Answers 9 to 11 (date, one-off or compounding goal, effort ceiling) re-rank the program tiers and it says which answer moved which rung.

    Interview

  • Prescribes the cheapest fix that matches the evidence and gives a one-sentence verdict.

    Four signals justify a structured program. Four others point elsewhere, such as docs navigation or a missing quickstart.

    Evidence gate

  • Ranks five rungs from a curated learning path up to proctored certification.

    Curated learning path, curriculum with labs, ad-hoc content, completion or skill badge, certification. It deletes rungs your answers rule out instead of listing them.

    Choose the program tier

  • Builds backwards from a job task analysis; every module must trace to a task.

    If more than 20% of modules fail the trace, the curriculum was written from the feature list and needs a restart. SKILL.md labels that 20% as its own baseline.

    Curriculum design

  • Recommends a credential only when someone outside the education team will act on it.

    Three types: completion badge, skill badge, certification. Designing the credential itself is handed to developer-certification-program.

    Credential decision

  • Writes down seven decisions, from owner and staffing to refresh trigger and pricing.

    A program missing any one of them is called a launch plan, not a program.

    Operating model

  • Sets one metric per level of the Kirkpatrick model and a kill rule stated as a number.

    Covers reaction, learning, behavior and results, with the learner-to-product-usage join decided before launch.

    Measurement and kill rules

  • Delivers an education charter with eleven sections, approved one at a time.

    Gate verdict through to a list of where each number came from, then a self-review scorecard of eleven checks. If there is no durable memory, SKILL.md says to write the charter to a file in the repository.

    Try: “we have forty tutorials and no learning path”

    Write · Education charter

From the official docs

Permissions

Low risk

The agent can save notes about your company or project to a file called devrel-context.md, so check that file before you commit or share the folder.

What it can do

  • Read your data
  • Create and change things
  • Delete things
  • Read-only mode

Watch out for

  • The charter may be written into your repository

    When there is no durable memory, SKILL.md says to write the charter to a file in the repository and say where it lives. Our advice: name the target folder first and review the file before committing it. github.com

  • It may keep notes in devrel-context.md

    SKILL.md tells the agent to store a few details about the current task or project, and to use a file called devrel-context.md when its memory lives in a file. Our advice: open that file before you commit or share the folder. github.com

  • The plugin route installs the whole collection

    The README's plugin and extension routes add every skill in the repo; its git tree holds 93. The repo has no hooks, agents, commands or MCP server files, and 14 of its skills bundle a script. Our advice: use the skills CLI command for this skill if you want only it. github.com

Security advisories

No published security advisories as of Nov 2, 2026.

Technical details
Turning on read-onlySKILL.md describes no read-only mode.
Scopes
  • May write the finished charter to a file in your repository when no durable memory exists (SKILL.md, Persisting decisions)

Questions

How do I install developer-education-strategy?

The README says to install every skill in the collection, because its skills reference each other. In Claude Code that is the plugin route in the install box above, which adds all 93 skills in the repo. The skills CLI can add just this one. Our advice: pick one route per agent.

What do I get at the end?

A developer education charter with eleven sections, from the gate verdict to a list of where each number came from. The agent presents it section by section and scores it against an eleven-point self-review before delivering.

Does it write the courses?

It does not. SKILL.md says it never writes courses and sends tutorial writing to developer-tutorial, which the README describes as the skill that writes or audits a teaching tutorial.

developer-education-strategy vs developer-certification-program?

Use this skill to decide whether any structured education or credential is worth it, and developer-certification-program to design the credential. SKILL.md says not to use it for designing the credential itself, and the README describes the other skill as planning tier, exam format, proctoring, renewal and fees.

Can I use it for onboarding my own employees?

It is not meant for that. SKILL.md says internal employee onboarding and engineering ramp-up belong to people or L&D teams, and tells the agent to say so and stop if that is the request.

Does developer-education-strategy need an API key, and where does it work?

SKILL.md names no API key, account or environment variable. The README documents installs for Claude Code, Claude.ai (add the repo as a plugin marketplace), Codex, Cursor, Gemini CLI and any Agent Skills-compatible tool through the skills CLI. The install box has the steps for each.

Is developer-education-strategy safe to install?

It is instructions plus four reference files, and the folder bundles no scripts. SKILL.md tells the agent to keep project notes in memory and, if there is none, to write the charter to a file in your repository. Our advice: tell it which folder the charter should go in before you start.

Information

updated Nov 2, 2026

Folder
skills/developer-education-strategy

samber/developer-relations-skillsskills.sh

Sources

Docs, issue trackers and discussions this page is built from.

Show all 2
  1. developer-relations-skills README · github.com
  2. developer-education-strategy SKILL.md · github.com

Updated Nov 2, 2026.