dbs-skill-maker picks a route by the size of the change: new or major rewrite, fixing a reported problem, a small edit, a read-only diagnosis, or publishing to GitHub. Every route that touches files delivers a plan first and waits for your confirmation. For new skills it asks requirement questions, finds the established solution to the problem at a depth you choose, and anchors each judgement step in a theory with its limits.
After writing it runs a structure validator, then compares old and new versions on the same real tasks and reports keep, keep testing or roll back. Publishing is an optional extra and only starts when you ask for it.
What You Get
- A plan for a new, changed or repaired skill with files, theory anchors, test plan and rollback
- The skill files written after your confirmation, with a project skeleton script if wanted
- A structure validation pass that checks front matter, links, placeholders, local paths and secret-like strings
- A before-and-after comparison and a keep, continue or roll back verdict
- Optional GitHub packaging with a README and an install command check
Common Use Cases
- Turning a problem you keep solving by hand into a reusable skill
- Fixing a skill that misbehaves on a specific case without breaking what already works
- Preparing a finished skill for sharing through a GitHub repository
What Makes It Unique
It treats a skill as something to be tested as well as written. Each judgement step needs a theory anchor or an admitted gap, each edit has to explain a stable class of failures and not a single example, and executors in tests never see the expected answers. Remote actions such as creating a repository, pushing, tagging or releasing need your explicit request.
Under The Hood
The skill is an instruction file with reference documents and four helper scripts. They create a skill skeleton, validate a skill folder, stage a public copy for GitHub and test an install. Following it can make the agent write and edit files in your project, run Python and shell commands, and, only when you ask to publish, use git and gh to create a repository, push and install from the network with npx skills add. It looks things up online only when a fact would change the plan.