New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Utility Pm Skill Validate

by product-on-purpose in product-on-purpose/pm-skills

Audits an existing pm-skills skill against structural conventions and quality criteria.

Apache-2.0Auto-check passed

Install Utility Pm Skill Validate

skills CLI
$ npx skills add product-on-purpose/pm-skills --skill utility-pm-skill-validate -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install product-on-purpose/pm-skills utility-pm-skill-validate --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/utility-pm-skill-validate .claude/skills/utility-pm-skill-validate && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
utility-pm-skill-validate
GitHub stars
715
Token cost
~3.5k tokens
SKILL.md length
1,513 words
Files
5 (incl. references)
Skills in repo
68
Repo updated
First seen
Licence
Apache-2.0

At a glance

Audits an existing pm-skills skill against structural conventions and quality criteria.

  • Works in 5 steps: Identify the Target → Read Skill Files → Run Tier 1 - Structural Checks → …
  • Checking whether a skill meets repo standards before shipping
  • SKILL.md covers When to Use, When NOT to Use, Instructions and Degraded Mode, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Utility Pm Skill Validate is an agent skill from product-on-purpose/pm-skills. Audits an existing pm-skills skill against structural conventions and quality criteria. Produces a structured validation report with pass/fail checks, severity-graded findings, and actionable recommendations. Use when checking whether a skill meets repo standards before shipping or after making changes.

Its SKILL.md is about 3.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files (for example `HISTORY.md`, `evals/trigger-fixtures.json` and `references/EXAMPLE.md`).

The repository describes itself as: 68 plug-and-play, best-practice product management skills for AI agents: 30 Triple Diamond phase + 11 foundation + 12 utility + 15 tool (Foundation Sprint + Design Sprint). Plus… The licence is Apache-2.0.

When your agent uses it

  • Checking whether a skill meets repo standards before shipping
  • After making changes

Example prompts

  • “Use the utility-pm-skill-validate skill to audit an existing pm-skills skill against structural conventions and quality criteria”
  • “/utility-pm-skill-validate”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Identify the Target
  2. Read Skill Files
  3. Run Tier 1 - Structural Checks
  4. Run Tier 2 - Quality Checks
  5. Produce the Validation Report

What it can do on your machine

Read from SKILL.md and the folder at commit 1cef1a9. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Utility Pm Skill Validate loads about 3.5k tokens when it runs, and up to ~4.8k if it reads all its reference files. Until then it costs about 83 tokens; SKILL.md has 1,513 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~83
When it runs · the whole SKILL.md, loaded when a task matches
~3.5k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~4.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from product-on-purpose/pm-skills at commit 1cef1a9, republished under its Apache-2.0 licence (© product-on-purpose). 1,513 words, ~3,474 tokens.

Download SKILL.mdSave it as .claude/skills/utility-pm-skill-validate/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
utility-pm-skill-validate
description
Audits an existing pm-skills skill against structural conventions and quality criteria. Produces a structured validation report with pass/fail checks, severity-graded findings, and actionable recommendations. Use when checking whether a skill meets repo standards before shipping or after making changes.
license
Apache-2.0
metadata.classification
utility
metadata.version
1.2.0
metadata.updated
2026-07-04
metadata.category
coordination
metadata.frameworks
triple-diamond
metadata.author
product-on-purpose

PM Skill Validate

This skill audits an existing pm-skills skill against the repo's structural conventions and quality criteria. It produces a validation report that a human can scan and that utility-pm-skill-iterate can consume as input.

The validator checks two tiers:

  • Tier 1 (Structural) - deterministic checks that mirror CI: frontmatter, naming, file presence, description word count.
  • Tier 2 (Quality) - LLM-assessed coherence checks: does the output contract reference the template? Is the example complete? Are checklist items testable?

When to Use

  • After creating a skill with utility-pm-skill-builder, before shipping
  • After manually editing a skill, to confirm it still passes conventions
  • Before running utility-pm-skill-iterate, to identify what needs improvement
  • When a convention changes, to audit which skills need updating (batch mode)
  • When reviewing a contributed skill for quality and completeness

When NOT to Use

  • To create a new skill from scratch -> use utility-pm-skill-builder
  • To fix or improve a skill -> use utility-pm-skill-iterate (feed it this report)
  • To run CI checks in a pipeline -> use scripts/lint-skills-frontmatter.sh (this skill is for interactive, deeper-than-CI validation)
  • To audit the whole catalog rather than one skill -> use utility-pm-skill-auditor. This skill goes deep on a single skill; the auditor goes wide across the repo and aggregates cross-cutting findings.

Instructions

When asked to validate a skill, follow these steps:

Step 1: Identify the Target

Accept the skill name in any form:

  • Directory name: deliver-prd
  • Full path: skills/deliver-prd/SKILL.md
  • Slash command: deliver-prd

Resolve to the canonical directory path: skills/{name}/.

If the skill directory does not exist, report immediately:

# Validation Report: {input}
Result: FAIL
Skill directory `skills/{input}/` does not exist.

Batch mode: If the input is --all, run Tier 1 structural checks across all skills and produce a summary table (see Step 5). Do not run Tier 2 in batch mode.

Step 2: Read Skill Files

Read all files in the skill directory:

FileRequiredPurpose
SKILL.mdyesFrontmatter + instructions
references/TEMPLATE.mdyesOutput template
references/EXAMPLE.mdyesWorked example
HISTORY.mdnoVersion history (if present)
evals/trigger-fixtures.jsonnoRouting-eval fixtures (B-4); present for roster skills
evals/output-scenarios/*.mdnoOutput-quality scenarios (B-7); present for evaled skills

Also read:

  • The corresponding command file: commands/{command-name}.md
  • The AGENTS.md entry for this skill

If reading files is not possible (MCP/embedded environment), ask the user to paste the content of each file before proceeding (see Degraded Mode).

Step 3: Run Tier 1 - Structural Checks

Run these deterministic checks. Each produces a PASS or FAIL line.

Check IDWhat to checkPass condition
frontmatter-at-byte-zeroFirst line of SKILL.md, references/TEMPLATE.md, references/EXAMPLE.md is exactly ---Line 1 is the opening --- fence with no preceding HTML comment, BOM, or whitespace. Severity: FAIL. Reference: library/skill-output-samples/SAMPLE_CREATION.md Section 5.
name-matchFrontmatter name matches directory nameExact string match
description-presentFrontmatter description existsNon-empty value
description-lengthDescription word count20-100 words
version-presentFrontmatter version existsNon-empty, valid SemVer
updated-presentFrontmatter updated existsNon-empty, ISO date
license-presentFrontmatter license existsNon-empty value
phase-classificationPhase/classification consistencyDomain has phase:, foundation/utility has classification:, not both
template-existsreferences/TEMPLATE.md existsFile present
template-sectionsTEMPLATE.md has sufficient structure≥3 ## level-2 headers
example-existsreferences/EXAMPLE.md existsFile present
command-existsCommand file exists in commands/File present and references correct skill path
agents-entryAGENTS.md has an entry for this skillEntry exists with matching **Path:**
eval-trigger-fixturesRouting fixtures present + well-formed (B-4)If evals/trigger-fixtures.json exists: schema:1, skill matches dir, >=16 queries, >=8 per class (trigger / no-trigger), >=2 near-misses. If absent: INFO (not in the trigger-eval roster, or fixtures not yet authored). Authoritative gate: scripts/check-trigger-fixtures.mjs.
eval-output-scenariosOutput scenarios present + well-formed (B-7)If evals/output-scenarios/*.md exist: each has scenario/skill/family frontmatter, skill matches dir, family maps to an existing docs/internal/eval-rubrics/{family}.md, body >=100 chars. If absent: INFO (not yet output-evaled). Authoritative gate: scripts/check-output-eval-assets.mjs.
reciprocal-boundary-pointersDeclared collision pairs cross-point (C-5)If the skill appears in COLLISION_PAIRS (scripts/check-trigger-fixtures.mjs): its When NOT to Use names each partner AND each partner's When NOT to Use names it back. FAIL if a declared pair is one-directional. If not in any pair: PASS. Authoritative gate: scripts/check-reciprocal-boundary-pointers.mjs.
Step 4: Run Tier 2 - Quality Checks

Run these LLM-assessed checks. Each produces a PASS, WARN, or INFO line. Tier 2 findings are capped at WARN unless objectively grounded (placeholder leakage is the exception - it can FAIL).

Check IDWhat to assessHow to assessMax severity
output-contract-coverageSKILL.md references the templateCheck for explicit reference to references/TEMPLATE.md or "use the template" in an Output section. Accept either pattern as valid. WARN only if template is not referenced at all.WARN
checklist-verifiabilityQuality checklist items are testableRead each checklist item. Flag items that are vague ("is good quality") vs. specific ("metrics are measurable"). WARN if ≥2 items are vague.WARN
example-completenessEXAMPLE.md fills all template sectionsCompare ## headers in TEMPLATE.md against ## headers in EXAMPLE.md. WARN if EXAMPLE.md is missing sections that appear in the template. Also check for unresolved placeholders. Line count is informational only - report it but do not gate on it.WARN
template-example-alignmentEXAMPLE.md follows TEMPLATE.md structureCompare section header ordering. WARN if EXAMPLE.md has sections in a different order or uses different header names than TEMPLATE.md.WARN
description-actionabilityDescription tells when to use the skillCheck for a trigger phrase like "Use when..." or "Use for..." in the frontmatter description. WARN if the description only says what the skill does without indicating when to use it.WARN
instruction-clarityInstructions are numbered and imperativeCheck for ### Step headings or a numbered list pattern in the Instructions section. WARN if instructions are prose paragraphs without clear step structure.WARN
placeholder-leakageNo leftover scaffolding in any shipped fileScan SKILL.md, TEMPLATE.md, and EXAMPLE.md for: [Placeholder] or [Feature Name] patterns, <!-- ... --> HTML comments (except the license header), template guidance blockquotes that should have been removed, and authoring notes like "TODO" or "FIXME". FAIL if any are found - this is objectively grounded.FAIL
when-not-to-use"When NOT to Use" section present and names neighborsCheck for a When NOT to Use section that names the skill's nearest neighbors (when to use them instead). WARN if the section is absent, or present but generic (no neighbor named). This became a convention in the v2.26.0 rewrites and underpins the reciprocity gate; reciprocal-boundary-pointers (Tier 1) is the deterministic backstop for declared collision pairs.WARN

Quality standard framing: These checks validate against current library conventions - what the shipped library actually does today. Findings graded WARN or INFO represent the v2.8 quality standard that newer skills (built with utility-pm-skill-builder) meet. Older skills may legitimately receive these findings until iterated through the lifecycle.

Heading and dialect conventions: for the authoritative section skeleton per dialect (classic, contract-shaped, tool-family) and the exact canon heading spellings, see Skeleton Canon: The Three Sanctioned Dialects in the skill-authoring guide. A skill whose headings or section set drift from its dialect's canon should be flagged in Recommendations even where no Tier 1 check above already covers it; scripts/check-heading-canon.mjs is the eventual deterministic backstop, shipping advisory until the full catalog is normalized.

Show full SKILL.md (395 more words)Show less
Step 5: Produce the Validation Report

Assemble the report using this exact structure. F-11 (utility-pm-skill-iterate) parses this report by section headings and pipe-delimited fields.

# Validation Report: {skill-name}
Date: {YYYY-MM-DD}
Skill version: {version from frontmatter}
Validator version: 1.0.0
Report schema: v1
Result: {PASS | WARN | FAIL}

## Summary
{1-2 sentence overall assessment.}
Errors: {n} | Warnings: {n} | Info: {n}

> Tier 2 findings are heuristic quality assessments and may require human review.

## Structural Checks
- {STATUS} | structural | {check-id} | {message}
- {STATUS} | structural | {check-id} | {message}
...

## Quality Checks
- {STATUS} | quality | {check-id} | {message}
- {STATUS} | quality | {check-id} | {message}
...

## Recommendations
1. {STATUS} | {check-id} | Target: {file-path}
   Action: {what to do}
2. {STATUS} | {check-id} | Target: {file-path}
   Action: {what to do}
...

Report rules:

  • Result = worst severity found: any FAIL → FAIL, else any WARN → WARN, else PASS.
  • Structural Checks: one line per Tier 1 check. STATUS is PASS or FAIL.
  • Quality Checks: one line per Tier 2 check. STATUS is PASS, WARN, or INFO.
  • Recommendations: only include checks that did NOT pass. Each recommendation includes the check ID, the target file path, and a specific action.
  • If all checks pass, the Recommendations section should say: "No issues found."
  • Omit passing checks from Recommendations - only list findings that need action.

Batch mode output (when input is --all):

Run Tier 1 structural checks only across all skills. Produce a summary table:

# Batch Validation Summary
Date: {YYYY-MM-DD}
Validator version: 1.0.0
Report schema: v1
Skills checked: {n}

| Skill | Result | Errors | Warnings |
|-------|--------|--------|----------|
| deliver-prd | PASS | 0 | 0 |
| define-hypothesis | WARN | 0 | 1 |
| foundation-persona | FAIL | 1 | 0 |
...

Skills passing: {n}/{total}
Run `utility-pm-skill-validate {skill}` for a detailed report.

Degraded Mode

If you cannot read skill files directly (e.g., running via MCP or in an embedded environment without file system access):

  1. Ask the user to provide the content of each required file:
    • skills/{name}/SKILL.md
    • skills/{name}/references/TEMPLATE.md
    • skills/{name}/references/EXAMPLE.md
  2. Run all checks against the provided content.
  3. Note in the report: "Validated from user-provided content (file system not available)."
  4. Batch mode is not available in degraded mode - single skill only.

Output Contract

The validator MUST produce a validation report following the format in Step 5.

The report:

  • Uses the exact section headings: ## Summary, ## Structural Checks, ## Quality Checks, ## Recommendations
  • Uses pipe-delimited check lines: STATUS | TIER | CHECK-ID | message
  • Uses pipe-delimited recommendations: STATUS | CHECK-ID | Target: path followed by Action: description on the next line
  • Includes Report schema: v1 in the header for F-11 compatibility
  • Includes the Tier 2 caveat line in the Summary section

Quality Checklist

Before delivering the report, verify:

  • All Tier 1 structural checks were run (not skipped), including the eval-asset checks (eval-trigger-fixtures, eval-output-scenarios, reciprocal-boundary-pointers); absent eval assets are INFO, not FAIL, except a one-directional declared collision pair which FAILs
  • All Tier 2 quality checks were run (not skipped) - single skill mode only
  • Report follows the exact section and line format from Step 5
  • Every non-passing check appears in Recommendations with a target file path
  • Result field reflects the worst severity found
  • Tier 2 findings are capped at WARN (except placeholder-leakage which can FAIL)
  • No Tier 2 check was marked FAIL unless objectively grounded

Examples

See references/EXAMPLE.md for a completed validation report demonstrating both Tier 1 and Tier 2 checks against a real shipped skill.

© product-on-purpose, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files (references) in skills/utility-pm-skill-validate of product-on-purpose/pm-skills.

  • SKILL.md
  • HISTORY.md
  • evals/trigger-fixtures.json
  • references/EXAMPLE.md
  • references/TEMPLATE.md

Open the folder on GitHubat commit 1cef1a9

Compare with similar skills

Utility Pm Skill Validate next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Utility Pm Skill Validate compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Utility Pm Skill Validate this skillproduct-on-purpose/pm-skills715—~3.5kAutomated safety check: PassApache-2.0
Structured Datathedaviddias/Front-End-Checklist74k—~420Automated safety check: PassMIT
Production Auditaffaan-m/ECC276k1 repos~1.9kAutomated safety check: PassMIT
Aims Auditalirezarezvani/claude-skills28k—~1.3kAutomated safety check: PassMIT
Convention AuditChenyCHENYU/Robot_Admin1k—~1.5kAutomated safety check: PassMIT
Geo Auditsickn33/agentic-awesome-skills47k1 repos~3.4kAutomated safety check: NotesMIT

Similar skills

  • Structured Data

    thedaviddias/Front-End-Checklist

    A skill your agent uses when auditing metadata, crawlability, structured data, or indexability related to Add structured data markup.

    74k GitHub stars~420 tokensUpdated 3 days ago
    Marketing & SEOAuto-check passed

  • Production Audit

    affaan-m/ECC

    Local-evidence production readiness audit for shipped apps, pre-launch reviews, post-merge checks, and "what breaks in prod?" questions without sending repo data to an external audit service.

    276k GitHub starsUsed in 1 repo~1.9k tokens
    Product & Project ManagementAuto-check passed

  • Aims Audit

    alirezarezvani/claude-skills

    /cs:aims-audit <scope — ISO/IEC 42001 AIMS internal-audit 6-question forcing interrogation.

    28k GitHub stars~1.3k tokensUpdated 1 mo ago
    Legal & ComplianceAuto-check passed

  • Convention Audit

    ChenyCHENYU/Robot_Admin

    A skill your agent uses when: reviewing code for compliance with Robot Admin project conventions, or when generating a compliance report.

    1k GitHub stars~1.5k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Geo Audit

    sickn33/agentic-awesome-skills

    Full website GEO+SEO audit with parallel subagent delegation.

    47k GitHub starsUsed in 1 repo~3.4k tokens
    Marketing & SEOAuto-check: notes

  • OmniRoute Audit and Policy CLI

    diegosouzapw/OmniRoute

    Command reference for omniroute's audit, logs, policy and telemetry commands: search and export audit trails, manage access policies and review request history for compliance work.

    74k GitHub stars~733 tokensUpdated yesterday
    SecurityAuto-check passed

More from product-on-purpose/pm-skills

All 68 skills in this repo

  • Define Hypothesis

    product-on-purpose/pm-skills

    Defines a testable hypothesis with clear success metrics and a validation approach.

    715 GitHub stars~966 tokensUpdated yesterday
    Auto-check passed

  • Define Jtbd Canvas

    product-on-purpose/pm-skills

    Creates a Jobs to be Done canvas capturing the functional, emotional, and social dimensions of a customer job.

    715 GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

  • Define Opportunity Tree

    product-on-purpose/pm-skills

    Creates an opportunity solution tree connecting a desired outcome to customer opportunities and candidate solutions, preventing solution-first jumps in continuous discovery.

    715 GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

  • Define Problem Statement

    product-on-purpose/pm-skills

    Creates a clear problem framing document with user impact, business context, and success criteria.

    715 GitHub stars~932 tokensUpdated yesterday
    Auto-check passed

  • Deliver Acceptance Criteria

    product-on-purpose/pm-skills

    Generates structured Given/When/Then acceptance criteria for a user story or feature slice, covering the happy path, key failure scenarios, and non-functional expectations in testable form.

    715 GitHub stars~1k tokensUpdated yesterday
    Auto-check passed

  • Deliver Launch Checklist

    product-on-purpose/pm-skills

    Creates a cross-functional pre-launch checklist covering engineering, design, marketing, support, legal, and operations readiness, with owners, dates, and go/no-go criteria so nothing is missed…

    715 GitHub stars~970 tokensUpdated yesterday
    Auto-check passed

Questions about Utility Pm Skill Validate

What does Utility Pm Skill Validate do?

Audits an existing pm-skills skill against structural conventions and quality criteria. Utility Pm Skill Validate is an agent skill from product-on-purpose/pm-skills. Audits an existing pm-skills skill against structural conventions and quality criteria.

When should I use Utility Pm Skill Validate?

Utility Pm Skill Validate fits situations like: checking whether a skill meets repo standards before shipping; after making changes.

How do I install Utility Pm Skill Validate in Claude Code?

Run `npx skills add product-on-purpose/pm-skills --skill utility-pm-skill-validate -a claude-code`. Or copy the skill folder (skills/utility-pm-skill-validate in product-on-purpose/pm-skills) into .claude/skills/utility-pm-skill-validate in your project. Claude Code loads it when a task matches its description.

How do I install Utility Pm Skill Validate in Codex?

Run `npx skills add product-on-purpose/pm-skills --skill utility-pm-skill-validate -a codex`. Or copy the skill folder (skills/utility-pm-skill-validate in product-on-purpose/pm-skills) into .agents/skills/utility-pm-skill-validate in your project. Codex loads it when a task matches its description.

Can I use Utility Pm Skill Validate in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add product-on-purpose/pm-skills --skill utility-pm-skill-validate -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/utility-pm-skill-validate, .gemini/skills/utility-pm-skill-validate, .github/skills/utility-pm-skill-validate and .opencode/skills/utility-pm-skill-validate in your project.

What does Utility Pm Skill Validate need to run?

SKILL.md names no scripts, command-line tools or credentials: Utility Pm Skill Validate is instructions for the agent only.

Does Utility Pm Skill Validate access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Utility Pm Skill Validate safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Utility Pm Skill Validate use?

Utility Pm Skill Validate is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Utility Pm Skill Validate use?

About 3.5k tokens (SKILL.md is roughly 14k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.3k tokens, read only when the agent opens those files.

What are the alternatives to Utility Pm Skill Validate?

Skills that share tags, products or a category with Utility Pm Skill Validate: Structured Data (thedaviddias/Front-End-Checklist, 74k stars), Production Audit (affaan-m/ECC, 276k stars), Aims Audit (alirezarezvani/claude-skills, 28k stars) and Convention Audit (ChenyCHENYU/Robot_Admin, 1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Utility Pm Skill Validate?

product-on-purpose (a GitHub organization) maintains it in product-on-purpose/pm-skills, which has 715 GitHub stars. The repository holds 68 skills in this directory. The repository was last updated on October 8, 2026.

Source: product-on-purpose/pm-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.