Skill Creator
Author, refine, and package reusable agent skills when you want consistent SKILL.md structure instead of one-off prompt dumps.
Overview
skill-creator is an agent skill most often used in Build (also Validate scope, Ship review) that helps solo builders author and tighten reusable SKILL.md agent capabilities.
Install
npx skills add https://github.com/freshtechbro/claudedesignskills --skill skill-creatorWhat is this skill?
- Guides creation of SKILL.md packages with triggers, constraints, and handoffs other agents can follow
- Supports iterative improvement loops typical of skill-creator workflows (draft → test → tighten invokeWhen)
- Fits solo builders maintaining a personal or team skill library alongside application code
- Pairs naturally with brainstorming and writing-plans skills when turning ideas into installable procedures
- Apache 2.0 licensed packaging suitable for fork-and-customize skill repos
Adoption & trust: 663 installs on skills.sh; 227 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You keep re-explaining the same multi-step agent workflow in chat and nothing stable lands in the repo for Claude Code or Cursor to reuse.
Who is it for?
Indie developers bootstrapping a skills folder, forking a design-skills repo, or standardizing how agents handle recurring rituals (reviews, scaffolds, checklists).
Skip if: Builders who only need a single ad-hoc answer with no reusable procedure, or teams that already enforce skill templates elsewhere and will not maintain SKILL.md.
When should I use this skill?
When authoring, splitting, or hardening agent skills for repeatable use in the repo.
What do I get? / Deliverables
You get a structured skill package with clear invokeWhen rules and deliverables you can commit, share, and chain into stacks like brainstorm → plan → implement.
- SKILL.md with name, description, invokeWhen, and structured body sections
- Optional supporting references bundled with the skill package
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Skill authoring is canonical on the Build shelf because the deliverable is agent capability you ship into the repo—not a one-time feature ticket. agent-tooling is the right subphase because the output is procedural knowledge files and eval harnesses for Claude/Cursor-style agents.
Where it fits
Decide which recurring rituals deserve their own skill before you commit to a full Build sprint.
Draft SKILL.md with permissions, deliverables, and faq-style invokeWhen for a design or review workflow.
Tighten anti-patterns and handoffs after a skill misfires during code review or implementation.
How it compares
Use as a skill-authoring workflow, not as a domain integration like an MCP server or a third-party API wrapper.
Common Questions / FAQ
Who is skill-creator for?
Solo and indie builders shipping with Claude Code, Cursor, or Codex who want repeatable agent procedures checked into the project instead of fragile chat history.
When should I use skill-creator?
During Validate when scoping what agents should own; during Build when drafting or splitting skills; and during Ship when tightening invokeWhen and deliverables after real usage.
Is skill-creator safe to install?
Review the Security Audits panel on this Prism page and inspect the skill files in your fork before granting agent permissions; do not assume pass/fail counts from this listing alone.
SKILL.md
READMESKILL.md - Skill Creator
Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this