SkillAgentSearch skills...

skill-authoring-workflow

Turn raw PM content into a compliant, publish-ready skill

Install / Use

npx skills add deanpeters/Product-Manager-Skills --skill skill-authoring-workflow

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

88/100

Category

Automation

Supported Platforms

Universal

Tags

Our assessment of skill-authoring-workflow

skill-authoring-workflow scores 88/100 on our quality scale, 1494th of 2,790 Automation skills we index.

Its SKILL.md is 7.7 KB long, well organised into 21 sections with 6 code examples: a thorough specification that gives an agent plenty to work with.

With 7,063 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
29/30
Structure
20/20
Description
8/15
Adoption
16/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 3 months ago, so skill-authoring-workflow is actively maintained.
  • Our last check on 2026-10-31 found the source still online.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-27. Automated pattern scan on 2026-09-27. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

skill-authoring-workflow compared with similar skills

All 4 of these similar skills score higher than skill-authoring-workflow; compare them before choosing.

SkillScoreStarsUpdatedFormat
skill-authoring-workflow (this skill)by deanpeters887.1k3mo agoSKILL.md
Agent-Reachby Panniantong100112.3k8d agoCLAUDE.md
rufloby ruvnet10081.9ktodayCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10039.7k7d agoCLAUDE.md
Scraplingby D4Vinci100103.6k2d agoMCP Server

Frequently asked questions

How do I install skill-authoring-workflow?
Run npx skills add deanpeters/Product-Manager-Skills --skill skill-authoring-workflow. The install tabs above show the steps for each supported agent.
Which AI agents does skill-authoring-workflow work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is skill-authoring-workflow safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is skill-authoring-workflow still maintained?
The repository was last updated about 3 months ago, so skill-authoring-workflow is actively maintained.

name: skill-authoring-workflow argument-hint: "[source content or skill to update]" description: Turn raw PM content into a compliant, publish-ready skill. Use when creating or updating a repo skill without breaking standards. intent: >- Create or update PM skills without chaos. This workflow turns rough notes, workshop content, or half-baked prompt dumps into compliant skills/<skill-name>/SKILL.md assets that actually pass validation and belong in this repo. type: workflow best_for:

  • "Creating a new repo skill from notes or source material"
  • "Updating an existing skill while keeping standards intact"
  • "Running the full authoring and validation workflow before commit" scenarios:
  • "Help me turn these workshop notes into a new PM skill"
  • "I need to update an existing skill without breaking the repo standards"
  • "What workflow should I use to author a new skill in this repo?" theme: meta-authoring estimated_time: "45-90 min"

Purpose

Create or update PM skills without chaos. This workflow turns rough notes, workshop content, or half-baked prompt dumps into compliant skills/<skill-name>/SKILL.md assets that actually pass validation and belong in this repo.

Use it when you want to ship a new skill without "looks good to me" roulette.

Input

Bring the raw material and the intent — rough is fine; the workflow exists to get it the rest of the way:

  • Works best with: the source content (notes, transcript, framework, prompt sequence) or the existing skill you want to update
  • Also useful: the intended skill type (component/interactive/workflow), target audience, and any naming preference

If you supply this inline with your request (e.g., "turn research/pricing-workshop-notes.md into an interactive advisor"), the workflow starts at Phase 1 with that context — it won't re-ask for what you already gave. If you provide nothing, it opens by asking what content you want to turn into a skill and offers the entry modes from the facilitation protocol.

Example: Use skill-authoring-workflow: convert research/pricing-workshop-notes.md into an interactive pricing advisor.

Key Concepts

Dogfood First

Use repo-native tools and standards before inventing a custom process:

  • scripts/find-a-skill.sh
  • scripts/add-a-skill.sh
  • scripts/build-a-skill.sh
  • scripts/test-a-skill.sh
  • scripts/check-skill-metadata.py

Pick the Right Creation Path

  • Guided wizard (build-a-skill.sh): Best when you have an idea but not final prose.
  • Content-first generator (add-a-skill.sh): Best when you already have source content.
  • Manual edit + validate: Best for tightening an existing skill.

Definition of Done (No Exceptions)

A skill is done only when:

  1. Frontmatter is valid (name, description, intent, type)
  2. Section order is compliant (Purpose, Input, Key Concepts, Application, Examples, Common Pitfalls, References)
  3. Metadata limits are respected (name <= 64 chars, description <= 200 chars)
  4. Description says both what the skill does and when to use it
  5. The Input section says what the user can bring, shows an example invocation, tells the agent to use inline input instead of re-asking, and makes clear that arriving with partial or zero input is fine — in plain language, never runtime template syntax like $ARGUMENTS (rationale: CONTRIBUTING.md, "Why We Don't Use $ARGUMENTS")
  6. Intent carries the fuller repo-facing summary without replacing the trigger-oriented description
  7. Cross-references resolve
  8. README catalog counts and tables are updated (if adding/removing skills)

Facilitation Source of Truth

When running this workflow as a guided conversation, use workshop-facilitation as the interaction protocol.

It defines:

  • session heads-up + entry mode (Guided, Context dump, Best guess)
  • one-question turns with plain-language prompts
  • progress labels (for example, Context Qx/8 and Scoring Qx/5)
  • interruption handling and pause/resume behavior
  • numbered recommendations at decision points
  • quick-select numbered response options for regular questions (include Other (specify) when useful)

This file defines the workflow sequence and domain-specific outputs. If there is a conflict, follow this file's workflow logic.

Application

Phase 1: Preflight (Avoid Duplicate Work)

  1. Search for overlapping skills:
./scripts/find-a-skill.sh --keyword "<topic>"
  1. Decide type:
  • Component: one artifact/template
  • Interactive: 3-5 adaptive questions + numbered options
  • Workflow: multi-phase orchestration

Phase 2: Generate Draft

If you have source material:

./scripts/add-a-skill.sh research/your-framework.md

If you want guided prompts:

./scripts/build-a-skill.sh

Phase 3: Tighten the Skill

Manually review for:

  • Clear "when to use" guidance
  • One concrete example — optimally two, from different business domains (one SaaS, one industrial/non-SaaS), so the framework visibly generalizes; reuse the repo's fictional universes (Fieldlight/Wrenchline for SaaS, Helix/Northfield/Corvid for industrial) and suffix the second file by domain (sample-industrial.md)
  • A template.md when the skill produces an artifact — the output schema as a copy/paste fill-in with quality checks
  • One explicit anti-pattern
  • No filler or vague consultant-speak

Phase 4: Validate Hard

Run strict checks before thinking about commit:

./scripts/test-a-skill.sh --skill <skill-name> --smoke
python3 scripts/check-skill-metadata.py skills/<skill-name>/SKILL.md
python3 scripts/check-skill-triggers.py skills/<skill-name>/SKILL.md --show-cases

Phase 5: Integrate with Repo Docs

If this is a new skill:

  1. Add it to the correct README category table
  2. Update skill totals and category counts
  3. Verify link paths resolve

Phase 6: Optional Packaging

If targeting Claude custom skill upload:

./scripts/zip-a-skill.sh --skill <skill-name>
# or zip one category:
./scripts/zip-a-skill.sh --type component --output dist/skill-zips
# or use a curated starter preset:
./scripts/zip-a-skill.sh --preset core-pm --output dist/skill-zips

Examples

Example: Turn Workshop Notes into a Skill

Input: research/pricing-workshop-notes.md
Goal: new interactive advisor

./scripts/add-a-skill.sh research/pricing-workshop-notes.md
./scripts/test-a-skill.sh --skill <new-skill-name> --smoke
python3 scripts/check-skill-metadata.py skills/<new-skill-name>/SKILL.md

Expected result:

  • New skill folder exists
  • Skill passes structural and metadata checks
  • README catalog entry added/updated

Anti-Pattern Example

"We wrote a cool skill, skipped validation, forgot README counts, and shipped anyway."

Result:

  • Broken references
  • Inconsistent catalog numbers
  • Confusion for contributors and users

Common Pitfalls

  • Shipping vibes, not standards.
  • Choosing workflow when the task is really a component template.
  • Bloated descriptions that exceed upload limits.
  • Descriptions that say what the skill is but not when Claude should trigger it.
  • Descriptions that silently hit the 200-char limit and get cut off mid-thought.
  • Letting intent become a substitute for a weak trigger description.
  • Forgetting to update README counts after adding a skill.
  • Treating generated output as final without review.

References

  • README.md
  • AGENTS.md
  • CLAUDE.md
  • docs/Building PM Skills.md
  • docs/Add-a-Skill Utility Guide.md
  • Anthropic's Complete Guide to Building Skills for Claude
  • scripts/add-a-skill.sh
  • scripts/build-a-skill.sh
  • scripts/find-a-skill.sh
  • scripts/test-a-skill.sh
  • scripts/check-skill-metadata.py
  • scripts/check-skill-triggers.py
  • scripts/zip-a-skill.sh

Related Skills

View on GitHub
GitHub Stars7.1k
CategoryAutomation
Updated2mo ago
Forks846

Languages

Shell

Trust signals

88/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium