developer-quickstart-guide skill (samber): write or audit a developer quickstart

• Asks up to twelve questions one at a time until the success moment and budget are clear.

  Question 8 asks whether you can run the steps yourself on a clean machine or need a verification plan someone else executes.

  Interview

• Chooses greenfield or audit; an audit cold-runs the existing page first.

  SKILL.md says never rewrite from reading alone.

  Runs code · Set the mode

• Names the product visibly working and sets a baseline time budget per product class.

  The table covers seven classes from a 5-minute hosted API to a 30 to 60 minute self-hosted service. SKILL.md labels the per-class budgets as its own baseline.

  Pick the success moment and time budget

• Cuts setup the reader does not need and lists the rest before step 1.

  The ranking runs from no account at all down to a sales-gated sandbox.

  Delete prerequisites, then list what survives

• Gives each step a heading, one copy-paste block, expected output and a fail branch.

  Commands and output sit in separate blocks and placeholders look unmistakable.

  Write each step

• Ships only when five checks pass on a clean environment with a fresh account.

  Every command works as written, real output matches, no prerequisite appears after step 1, time is inside budget, and a newcomer reaches success without leaving the page.

  Runs code · Verify by cold run

• Logs every hesitation during the run and defines step-level drop-off as the first metric.

  It also suggests running the quickstart commands in CI against the published package.

  Friction log and KPIs

• Returns six parts, from success moment and budget to a verification plan.

  It never emits a page without the budget and the verification plan.

  Try: “We're launching a Go SDK next week, write the quickstart.”

  Output

Watch out for

• The cold run executes your quickstart commands

  SKILL.md wants a clean environment and a fresh account with no cached credentials. Our advice: use a test account, never real credentials, and read each command before it runs. 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