Home / phuryn / pm-skills
AI Slop Code RIsk Monitor

phuryn/pm-skills

PM Skills Marketplace: 100+ agentic skills, commands, and plugins — from discovery to strategy, execution, launch, and growth.

33.6 High pattern signal View on GitHub

Maintenance and Governance Review

This report summarizes scanner evidence for phuryn/pm-skills with 26,871 GitHub stars. SynthScan examined 13,809 lines of code across 143 source files, recording 253 pattern matches distributed across 9 syntactic categories. The legacy adjusted pattern signal is 33.6 (High pattern signal); it is not an authorship estimate.

Use the findings to ask whether maintainers can explain intent, verify dependencies, simplify unnecessary scaffolding, and focus review effort. Risk Payload v1 adds ownership, supply-chain, over-engineering, and review-effort vectors when available. These are prompts for human verification, not probabilities, security findings, or measured maintenance costs.

33.6
Adjusted Signal
33.6
Raw Pattern Score
100%
Time Factor
2026-10-10
Last Push
26.9K
Stars
—
Language
13.8K
Lines of Code
143
Files
253
Pattern Hits
2026-10-12
Scan Date
0.00
HC Hit Rate

Risk Review · v3

Use each vector to guide manual verification of the underlying findings.

Cognitive Ownership Risk 79.9/100 · CRITICAL

Can maintainers explain intent, assumptions, and trade-offs? 245 finding(s).

Hallucinated Dependency & Supply Chain Risk 0.4/100 · LOW

Are imports declared and package/API names verified? 1 finding(s).

Agent Over-Engineering Ratio 11.7/100 · LOW

Are wrappers, guards, and repeated structures necessary? 20 finding(s).

PR Review Velocity Impact 62.5/100 · HIGH

Which changes need focused human review? 253 finding(s).

What These Metrics Mean

Adjusted Signal
Legacy pattern score normalized per 1,000 scanned lines and multiplied by the repository-level time factor. It is not an estimate of AI authorship.
Raw Pattern Score
Sum of severity- and context-weighted pattern findings before applying the time factor.
Time Factor
A coarse multiplier based on repository last-push metadata. It does not identify when individual code was written.
Pattern Hits
Count of configured pattern findings. Review each location and surrounding code before acting.
HC Hit Rate
High- and critical-severity findings per scanned file. Severity is a configured detector weight, not proof of a vulnerability or authorship.
Lines / Files
Scan coverage denominators used by the legacy normalized score.

Pattern-Signal History

This chart tracks the legacy adjusted pattern score across scan runs. Changes can reflect source changes, scan coverage, or detector/scoring versions; they do not measure AI adoption or prove that a team refactored code. Compare runs only when their scoring versions are compatible. The dashed line tracks the raw pattern-hit count.

Severity Breakdown

Groups findings by configured severity weight. Severity is not a confidence estimate, security rating, or proof that a package is missing. Verify imports against the project's manifests and inspect each finding in its local design context.

CRITICAL 0HIGH 0MEDIUM 9LOW 244

Directory Score Breakdown

This horizontal bar chart shows where configured pattern scores accumulate across directories. Treat the bars as locations to inspect, not as evidence of authorship or code quality. Use the file-level findings to decide whether a directory needs a focused ownership, dependency, complexity, or review check.

Pattern Findings

The scanner identified 253 distinct pattern matches across 9 syntactic categories. Each entry below represents a discrete location in the source code where the engine recorded a detector match to inspect in context. Expand any category row to inspect the individual file paths, line numbers, code snippets, and the lexical context (CODE, COMMENT, or STRING) in which each match was detected.

Reading the findings table: The Severity column indicates the configured finding weight (CRITICAL / HIGH / MEDIUM / LOW). The Context column identifies whether the match occurred inside executable code, an inline comment, or a string literal — legacy comment-context matches receive a ×1.5 score weight. The ⚡ bolt icon marks clustered matches: three or more patterns within a 10-line window, each receiving an additional ×1.5 density multiplier under the legacy scoring model.

Structural Annotation Overuse226 hits · 418 pts
SeverityFileLineSnippetContext
LOWREADME.md67# Step 1: Add the marketplaceCOMMENT
LOWREADME.md70# Step 2: Install individual pluginsCOMMENT
LOWREADME.md87# Step 1: Add the marketplaceCOMMENT
LOWREADME.md90# Step 2: Install the plugins you wantCOMMENT
LOWpm-product-strategy/commands/pricing.md20### Step 1: Understand the Pricing ContextCOMMENT
LOWpm-product-strategy/commands/pricing.md29### Step 2: Analyze Pricing ModelsCOMMENT
LOW⚡pm-product-strategy/commands/pricing.md43### Step 3: Competitive Pricing AnalysisCOMMENT
LOW⚡pm-product-strategy/commands/pricing.md51### Step 4: Willingness to Pay EstimationCOMMENT
LOW⚡pm-product-strategy/commands/pricing.md61### Step 5: Generate Pricing RecommendationCOMMENT
LOWpm-product-strategy/commands/pricing.md115### Step 6: Offer Next StepsCOMMENT
LOWpm-product-strategy/commands/market-scan.md20### Step 1: Understand the ContextCOMMENT
LOWpm-product-strategy/commands/market-scan.md28### Step 2: Run the AnalysisCOMMENT
LOWpm-product-strategy/commands/market-scan.md49### Step 3: SynthesizeCOMMENT
LOWpm-product-strategy/commands/market-scan.md57### Step 4: Generate ReportCOMMENT
LOWpm-product-strategy/commands/market-scan.md115### Step 5: Offer Next StepsCOMMENT
LOW⚡pm-product-strategy/commands/business-model.md157### Step 1: Gather ContextCOMMENT
LOW⚡pm-product-strategy/commands/business-model.md165### Step 2: Generate the Selected Framework(s)COMMENT
LOW⚡pm-product-strategy/commands/business-model.md169### Step 3: Save and IterateCOMMENT
LOWpm-product-strategy/commands/strategy.md20### Step 1: Understand the ProductCOMMENT
LOWpm-product-strategy/commands/strategy.md33### Step 2: Build the Strategy CanvasCOMMENT
LOWpm-product-strategy/commands/strategy.md51### Step 3: Generate Strategy DocumentCOMMENT
LOWpm-product-strategy/commands/strategy.md105### Step 4: Offer Next StepsCOMMENT
LOWpm-product-strategy/commands/value-proposition.md20### Step 1: Understand the Product and MarketCOMMENT
LOWpm-product-strategy/commands/value-proposition.md32### Step 2: Build the Value PropositionCOMMENT
LOWpm-product-strategy/commands/value-proposition.md59### Step 3: Save and Offer Next StepsCOMMENT
LOWpm-market-research/commands/research-users.md20### Step 1: Accept Research InputsCOMMENT
LOW⚡pm-market-research/commands/research-users.md35### Step 2: Build PersonasCOMMENT
LOW⚡pm-market-research/commands/research-users.md44### Step 3: Segment UsersCOMMENT
LOW⚡pm-market-research/commands/research-users.md53### Step 4: Map the Customer JourneyCOMMENT
LOW⚡pm-market-research/commands/research-users.md62### Step 5: Generate Research ReportCOMMENT
LOWpm-market-research/commands/research-users.md108### Step 6: Offer Next StepsCOMMENT
LOWpm-market-research/commands/analyze-feedback.md20### Step 1: Accept Feedback DataCOMMENT
LOWpm-market-research/commands/analyze-feedback.md32### Step 2: AnalyzeCOMMENT
LOWpm-market-research/commands/analyze-feedback.md42### Step 3: Generate Analysis ReportCOMMENT
LOWpm-market-research/commands/analyze-feedback.md91### Step 4: Offer Next StepsCOMMENT
LOW⚡pm-market-research/commands/competitive-analysis.md20### Step 1: Understand the Competitive ContextCOMMENT
LOW⚡pm-market-research/commands/competitive-analysis.md28### Step 2: Identify CompetitorsCOMMENT
LOW⚡pm-market-research/commands/competitive-analysis.md37### Step 3: Analyze Each CompetitorCOMMENT
LOW⚡pm-market-research/commands/competitive-analysis.md47### Step 4: Generate Competitive AnalysisCOMMENT
LOWpm-market-research/commands/competitive-analysis.md85### Step 5: Offer Next StepsCOMMENT
LOW⚡pm-data-analytics/commands/analyze-cohorts.md20### Step 1: Accept Data or Define AnalysisCOMMENT
LOW⚡pm-data-analytics/commands/analyze-cohorts.md26### Step 2: Define CohortsCOMMENT
LOW⚡pm-data-analytics/commands/analyze-cohorts.md34### Step 3: AnalyzeCOMMENT
LOWpm-data-analytics/commands/analyze-cohorts.md51### Step 4: Generate ReportCOMMENT
LOWpm-data-analytics/commands/analyze-cohorts.md88### Step 5: Offer Next StepsCOMMENT
LOWpm-data-analytics/commands/write-query.md20### Step 1: Understand the QuestionCOMMENT
LOWpm-data-analytics/commands/write-query.md28### Step 2: Determine SchemaCOMMENT
LOWpm-data-analytics/commands/write-query.md39### Step 3: Generate QueryCOMMENT
LOWpm-data-analytics/commands/write-query.md49### Step 4: Present and IterateCOMMENT
LOW⚡pm-data-analytics/commands/analyze-test.md20### Step 1: Accept Test DataCOMMENT
LOW⚡pm-data-analytics/commands/analyze-test.md28### Step 2: Validate Test DesignCOMMENT
LOW⚡pm-data-analytics/commands/analyze-test.md38### Step 3: Analyze ResultsCOMMENT
LOW⚡pm-data-analytics/commands/analyze-test.md48### Step 4: Generate AnalysisCOMMENT
LOWpm-data-analytics/commands/analyze-test.md96### Step 5: Offer Next StepsCOMMENT
LOW⚡pm-data-analytics/skills/sql-queries/SKILL.md13### Step 1: Understand Your Database SchemaCOMMENT
LOW⚡pm-data-analytics/skills/sql-queries/SKILL.md18### Step 2: Process Your RequestCOMMENT
LOW⚡pm-data-analytics/skills/sql-queries/SKILL.md23### Step 3: Generate Optimized QueryCOMMENT
LOW⚡pm-data-analytics/skills/sql-queries/SKILL.md29### Step 4: Explain and TestCOMMENT
LOW⚡pm-data-analytics/skills/cohort-analysis/SKILL.md13### Step 1: Read and Validate Your DataCOMMENT
LOW⚡pm-data-analytics/skills/cohort-analysis/SKILL.md19### Step 2: Generate Quantitative AnalysisCOMMENT
166 more matches not shown…
Decorative Section Separators6 hits · 18 pts
SeverityFileLineSnippetContext
MEDIUMvalidate_plugins.py28# ─── Configuration ───────────────────────────────────────────────────────────COMMENT
MEDIUMvalidate_plugins.py47# ─── ANSI Colors ─────────────────────────────────────────────────────────────COMMENT
MEDIUMvalidate_plugins.py60# ─── Helpers ─────────────────────────────────────────────────────────────────COMMENT
MEDIUMvalidate_plugins.py94# ─── Validators ──────────────────────────────────────────────────────────────COMMENT
MEDIUMvalidate_plugins.py313# ─── Main Validator ──────────────────────────────────────────────────────────COMMENT
MEDIUM.github/workflows/tag-on-merge.yml101 # ── Release gates ────────────────────────────────────────────────────COMMENT
Hyper-Verbose Identifiers13 hits · 14 pts
SeverityFileLineSnippetContext
LOWvalidate_plugins.py289def validate_cross_references(plugin_dir: str, skill_names: list[str]) -> ValidationResult:CODE
LOWtests/test_consistency.py59 def test_marketplace_lists_exactly_the_plugins_on_disk(self):CODE
LOWtests/test_consistency.py69 def test_sources_point_at_matching_directories(self):CODE
LOWtests/test_consistency.py81 def test_all_versions_identical_and_match_changelog(self):CODE
LOWtests/test_consistency.py100 def test_headings_well_formed_dated_unique_descending(self):CODE
LOWtests/test_consistency.py135 def test_root_readme_headline_counts(self):CODE
LOWtests/test_consistency.py148 def test_marketplace_description_counts(self):CODE
LOWtests/test_consistency.py164 def test_root_readme_per_plugin_counts(self):CODE
LOWtests/test_consistency.py184 def test_plugin_readme_section_counts(self):CODE
LOWtests/test_consistency.py209 def test_plugin_readme_command_refs_exist(self):CODE
LOW⚡tests/test_validator.py21 def test_none_without_frontmatter(self):CODE
LOW⚡tests/test_validator.py24 def test_none_when_unterminated(self):CODE
LOW⚡tests/test_validator.py33 def test_excludes_frontmatter(self):CODE
Modern AI Meta-Vocabulary2 hits · 6 pts
SeverityFileLineSnippetContext
MEDIUMpm-ai-shipping/commands/performance-audit-static.md30## Model and orchestrationCOMMENT
MEDIUMpm-ai-shipping/commands/security-audit-static.md38## Model and orchestrationCOMMENT
Excessive Try-Catch Wrapping1 hit · 2 pts
SeverityFileLineSnippetContext
MEDIUMvalidate_plugins.py478 print(f"Error: {base_path} is not a directory")CODE
Deep Nesting2 hits · 2 pts
SeverityFileLineSnippetContext
LOWvalidate_plugins.py370CODE
LOWtests/test_validator.py40CODE
Redundant / Tautological Comments1 hit · 2 pts
SeverityFileLineSnippetContext
LOWvalidate_plugins.py260 # Check if command references skills (informational)COMMENT
Unused Imports1 hit · 1 pts
SeverityFileLineSnippetContext
LOWvalidate_plugins.py24CODE
Over-Commented Block1 hit · 1 pts
SeverityFileLineSnippetContext
LOW.github/workflows/tag-on-merge.yml1name: Tag and release from CHANGELOGCOMMENT