skill-authoring-workflow
by deanpetersskill-authoring-workflow helps you turn rough notes, workshop output, or draft prompts into a compliant, repo-ready skills/<skill-name>/SKILL.md. Use this skill-authoring-workflow skill to create or update PM skills with less guesswork, follow repo standards, and validate before commit.
This skill scores 78/100, which means it is a solid directory candidate with useful workflow leverage for agents. Directory users should see it as install-worthy if they need a guided process for authoring or updating repo skills, but it is not yet a best-in-class, fully packaged workflow because it relies on repo-native scripts and has no supporting references or install command.
- Clear trigger and intent for creating or updating PM skills without breaking repo standards.
- Operational workflow guidance is specific and repo-native, including named scripts like `find-a-skill.sh`, `add-a-skill.sh`, `build-a-skill.sh`, `test-a-skill.sh`, and `check-skill-metadata.py`.
- Good structural depth for execution, with valid frontmatter, substantial body length, and multiple headings covering workflow choices and constraints.
- No install command, support files, or references are provided, so users must already be comfortable navigating the repo and its scripts.
- The excerpted content shows strong process framing, but directory users may still need to read the full skill to understand edge cases and exact authoring flow.
Overview of skill-authoring-workflow skill
The skill-authoring-workflow skill helps you turn rough PM notes, workshop output, or a draft prompt into a repo-compliant skills/<skill-name>/SKILL.md file. It is for people authoring a skill in the deanpeters/Product-Manager-Skills ecosystem who want a workflow that passes validation, matches repo standards, and avoids cleanup churn later.
What this skill is for
skill-authoring-workflow is a creation-and-update workflow, not a generic writing prompt. Its job is to help you structure a new skill from source material, then validate it before commit so the result is usable in the repo.
Who should use it
This skill-authoring-workflow skill is best for contributors who have:
- raw notes or a messy draft to convert into a skill
- an existing skill that needs revision without breaking conventions
- a need to choose between guided creation paths and repo-native tooling
Why it is different
The main value is process discipline. The skill-authoring-workflow skill emphasizes repo-native commands, standards, and validation steps, which reduces the risk of shipping a skill that looks complete but fails checks or misses required structure.
How to Use skill-authoring-workflow skill
Install the skill in your repo
Use the repo install flow that the skill points to:
npx skills add deanpeters/Product-Manager-Skills --skill skill-authoring-workflow
For skill-authoring-workflow install, confirm you are adding it into the same environment where you plan to author or validate skills, so the command output, file paths, and checks line up with your repo state.
Start with the source files that matter
Read SKILL.md first, then inspect the repo’s supporting materials in this order if present:
README.mdAGENTS.mdmetadata.jsonrules/resources/references/scripts/
In this repository, SKILL.md is the only visible source file, so the practical first step is to read it closely and treat it as the workflow reference for the skill-authoring-workflow guide.
Turn rough input into a usable prompt
The best skill-authoring-workflow usage starts with a clear source package, not a vague request. Give the skill:
- the target skill name
- source notes or draft text
- whether you are creating or updating
- the intended repo path
- any constraints on tone, length, or validation
Strong input example: “Convert these workshop notes into skills/onboarding-checklist/SKILL.md, keep repo conventions, and flag any missing metadata before finalizing.”
Follow the authoring path that fits your state
If you have an idea but not final prose, use the guided path. If you already have source content, use the content-first path. The workflow’s value is in matching the creation path to your starting point, rather than forcing every project through the same sequence.
skill-authoring-workflow skill FAQ
Is skill-authoring-workflow only for new skills?
No. The skill-authoring-workflow skill is also useful when you are updating an existing skill and need to preserve standards while changing content or structure.
Do I need to know the repo conventions first?
Not completely, but you should be ready to read them. The workflow is designed to reduce guesswork by pointing you toward the repo-native tools and the right files to inspect before you author.
Is this just another prompt template?
No. A normal prompt can draft text, but skill-authoring-workflow is about a full authoring loop: source intake, path selection, compliance, and validation. That matters if you care about installability and repo fit.
When should I not use it?
Skip it if you only need a quick one-off answer and do not plan to create or update a repo skill. It is most useful when the output must live inside skills/<skill-name>/SKILL.md and survive validation.
How to Improve skill-authoring-workflow skill
Give the skill cleaner source material
The biggest quality boost comes from better input. Provide the raw notes, intended audience, and a short statement of the job the skill should do. If you already know what must remain unchanged, say so up front.
Include validation expectations early
If your priority is passing repo checks, say that explicitly. The workflow is strongest when it can align prose decisions with structural constraints instead of discovering problems after drafting.
Watch for common failure modes
The usual misses are vague scope, unclear creation path, and skipping file inspection. If the first output feels generic, it usually means the input did not distinguish between a new build, an update, and a compliance pass.
Iterate on structure, not just wording
For skill-authoring-workflow for Skill Authoring, the fastest improvement is to revise the input package: name the target file, list the source artifacts, and specify any repo rules that matter. Then rerun the workflow and compare the resulting SKILL.md against the required path and validation needs.