dbs-skill-maker Skill for Claude Code: What It Does and How to Install It

• Asks your needs in one batch, you pick a depth, then it hands you a plan and stops

  Reads your material and the target folder, writes a problem contract, asks the gaps as one set of questions, finds a standard answer at the depth you pick (light, full or skip), anchors each step to theory, then delivers the plan and waits.

  Try: “Turn this weekly report routine into a Skill”

  Read · Route A: new or major rewrite

• Reproduces a real failure, finds the step that went wrong, proposes edits and a rollback

  Reads the Skill, its evals and scripts, locates where behaviour went off, then hands you a plan with evidence, edits, tests and rollback. After you confirm, it compares before and after on the same tasks.

  Read · Route B: fix from a failure

• Gives a few lines of plan, waits for OK, edits, then runs the structure check

  For changes you describe exactly, like lowering a question cap. No theory check.

  Write · Route C: small edit

• Reports a diagnosis or test result and changes no files

  Needs no confirmation because the route is read-only by its own definition.

  Read · Route D: diagnose or test only

• Prepares a repo only when you ask to share or publish; asks before push, tag or Release

  Reads references/github-publishing.md. The prepare script builds a local staging folder. Remote actions need your explicit request.

  Runs code · Route E: GitHub publishing

• Creates a new Skill folder with a first-draft SKILL.md

  SKILL.md says to run it when you create a new Skill.

  Runs code · scripts/init_skill_project.py

• Checks frontmatter, links and resources; syntax-checks bundled .py and .sh files

  Run as python3 scripts/validate_skill_project.py <skill-directory>. It calls bash -n on shell scripts.

  Runs code · scripts/validate_skill_project.py

• Copies the Skill into a local staging folder and writes a README and .gitignore there

  Its output says no remote repo is created and nothing is pushed.

  Runs code · scripts/prepare_github_repo.py

• Runs the skills CLI install into a temporary HOME and compares the installed files

  Runs npx -y skills add with --all against the source you give, then removes the temporary folder.

  Runs code · scripts/verify_npx_install.sh

• Guides for problem, answer, theory, build, fix, evaluation and publishing

  Loaded by route: problem-and-goal, standard-answer, theory-grounding, skill-construction, improvement, evaluation and github-publishing.

  Read · References (7 files)

Watch out for

• It writes and edits files after you confirm

  Confirm a plan only once you have read which files it will touch. SKILL.md says it checks a rollback point first (a clean git state or a copy in a temp folder). github.com

• The install check runs npx -y with --all

  scripts/verify_npx_install.sh installs from the source you give into a temporary HOME with npx -y skills add ... -g --all and then deletes the temp folder. It downloads and runs code from that source. github.com

• Publishing can push to GitHub

  The reference says gh repo create, git push, tag and Release need your explicit request. Check the repo, branch and commit range before you agree. github.com

• The plugin route installs only this plugin

  The marketplace lists dbs-skill-maker as its own plugin with source ./skills/dbs-skill-maker. The skills CLI command in the README installs all dbskill Skills to every agent it detects. github.com

Security advisories