PM Skills Marketplace: 100+ agentic skills, commands, and plugins — from discovery to strategy, execution, launch, and growth.
This report presents the forensic synthetic code analysis of phuryn/pm-skills with 23,667 GitHub stars. SynthScan v2.0 examined 13,136 lines of code across 139 source files, recording 249 pattern matches distributed across 8 syntactic categories. The overall adjusted score of 34.3 places this repository in the Strong AI signal band.
The scanner applied 160+ deterministic lexical heuristics, multi-line block detectors, abstract syntax tree depth profilers, and a cross-file Jaccard similarity matrix to construct a statistically normalised synthetic code estimate. All matches are individually weighted by severity coefficient and contextual multiplier before summation, and the resulting headline score is temporally discounted to account for the repository's development history relative to the commercial emergence of large language model coding tooling (November 2022 onward).
This chart maps the temporal evolution of the adjusted synthetic code score across successive scan runs. An upward trajectory indicates ongoing incorporation of AI-generated code or expanding LLM-assisted scaffolding; a stable or declining trajectory may reflect active human refactoring, code removal, or the adoption of stricter authorship policies. The dashed secondary line (right axis) independently tracks total raw pattern hit count, which can diverge from the normalised score when codebase size changes significantly between scans.
Classifies detected patterns by their diagnostic confidence and structural impact. CRITICAL patterns (coefficient 10) represent definitive synthetic signatures — hallucinated imports, explicit LLM attribution metadata — virtually never produced by human authors. HIGH (5) indicates strong structural tells such as cross-file repetition or cross-linguistic idioms. MEDIUM (2) covers recognisable conversational padding and AI-specific vocabulary. LOW (1) captures subtle indicators like tautological comments and generic boilerplate that require density to carry independent signal.
This horizontal bar chart decomposes the repository's raw synthetic code score by top-level directory, allowing you to pinpoint precisely which modules or components carry the highest AI authorship density. Directories with disproportionately high scores relative to their size warrant targeted manual review: concentrated AI signatures often trace back to mass-generated configuration layers, auto-ported test suites, LLM-scaffolded boilerplate classes, or entire subsystems authored under heavy copilot assistance. Use this view to prioritise your human code-review effort.
The scanner identified 249 distinct pattern matches across 8 syntactic categories. Each entry below represents a discrete location in the source code where the engine recorded a statistically significant AI authorship indicator. 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 diagnostic confidence level (CRITICAL / HIGH / MEDIUM / LOW). The Context column identifies whether the match occurred inside executable code, an inline comment, or a string literal — comment-context matches receive a ×1.5 weight because LLMs systematically over-annotate. The ⚡ bolt icon marks clustered matches: three or more patterns within a 10-line window, each receiving an additional ×1.5 density multiplier as dense clusters constitute far stronger evidence of synthetic authorship than isolated hits.
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | README.md | 67 | # Step 1: Add the marketplace | COMMENT |
| LOW | README.md | 70 | # Step 2: Install individual plugins | COMMENT |
| LOW | README.md | 87 | # Step 1: Add the marketplace | COMMENT |
| LOW | README.md | 90 | # Step 2: Install the plugins you want | COMMENT |
| LOW | pm-product-strategy/commands/pricing.md | 20 | ### Step 1: Understand the Pricing Context | COMMENT |
| LOW | pm-product-strategy/commands/pricing.md | 29 | ### Step 2: Analyze Pricing Models | COMMENT |
| LOW⚡ | pm-product-strategy/commands/pricing.md | 43 | ### Step 3: Competitive Pricing Analysis | COMMENT |
| LOW⚡ | pm-product-strategy/commands/pricing.md | 51 | ### Step 4: Willingness to Pay Estimation | COMMENT |
| LOW⚡ | pm-product-strategy/commands/pricing.md | 61 | ### Step 5: Generate Pricing Recommendation | COMMENT |
| LOW | pm-product-strategy/commands/pricing.md | 115 | ### Step 6: Offer Next Steps | COMMENT |
| LOW | pm-product-strategy/commands/market-scan.md | 20 | ### Step 1: Understand the Context | COMMENT |
| LOW | pm-product-strategy/commands/market-scan.md | 28 | ### Step 2: Run the Analysis | COMMENT |
| LOW | pm-product-strategy/commands/market-scan.md | 49 | ### Step 3: Synthesize | COMMENT |
| LOW | pm-product-strategy/commands/market-scan.md | 57 | ### Step 4: Generate Report | COMMENT |
| LOW | pm-product-strategy/commands/market-scan.md | 115 | ### Step 5: Offer Next Steps | COMMENT |
| LOW⚡ | pm-product-strategy/commands/business-model.md | 157 | ### Step 1: Gather Context | COMMENT |
| LOW⚡ | pm-product-strategy/commands/business-model.md | 165 | ### Step 2: Generate the Selected Framework(s) | COMMENT |
| LOW⚡ | pm-product-strategy/commands/business-model.md | 169 | ### Step 3: Save and Iterate | COMMENT |
| LOW | pm-product-strategy/commands/strategy.md | 20 | ### Step 1: Understand the Product | COMMENT |
| LOW | pm-product-strategy/commands/strategy.md | 33 | ### Step 2: Build the Strategy Canvas | COMMENT |
| LOW | pm-product-strategy/commands/strategy.md | 51 | ### Step 3: Generate Strategy Document | COMMENT |
| LOW | pm-product-strategy/commands/strategy.md | 105 | ### Step 4: Offer Next Steps | COMMENT |
| LOW | pm-product-strategy/commands/value-proposition.md | 20 | ### Step 1: Understand the Product and Market | COMMENT |
| LOW | pm-product-strategy/commands/value-proposition.md | 32 | ### Step 2: Build the Value Proposition | COMMENT |
| LOW | pm-product-strategy/commands/value-proposition.md | 59 | ### Step 3: Save and Offer Next Steps | COMMENT |
| LOW | pm-market-research/commands/research-users.md | 20 | ### Step 1: Accept Research Inputs | COMMENT |
| LOW⚡ | pm-market-research/commands/research-users.md | 35 | ### Step 2: Build Personas | COMMENT |
| LOW⚡ | pm-market-research/commands/research-users.md | 44 | ### Step 3: Segment Users | COMMENT |
| LOW⚡ | pm-market-research/commands/research-users.md | 53 | ### Step 4: Map the Customer Journey | COMMENT |
| LOW⚡ | pm-market-research/commands/research-users.md | 62 | ### Step 5: Generate Research Report | COMMENT |
| LOW | pm-market-research/commands/research-users.md | 108 | ### Step 6: Offer Next Steps | COMMENT |
| LOW | pm-market-research/commands/analyze-feedback.md | 20 | ### Step 1: Accept Feedback Data | COMMENT |
| LOW | pm-market-research/commands/analyze-feedback.md | 32 | ### Step 2: Analyze | COMMENT |
| LOW | pm-market-research/commands/analyze-feedback.md | 42 | ### Step 3: Generate Analysis Report | COMMENT |
| LOW | pm-market-research/commands/analyze-feedback.md | 91 | ### Step 4: Offer Next Steps | COMMENT |
| LOW⚡ | pm-market-research/commands/competitive-analysis.md | 20 | ### Step 1: Understand the Competitive Context | COMMENT |
| LOW⚡ | pm-market-research/commands/competitive-analysis.md | 28 | ### Step 2: Identify Competitors | COMMENT |
| LOW⚡ | pm-market-research/commands/competitive-analysis.md | 37 | ### Step 3: Analyze Each Competitor | COMMENT |
| LOW⚡ | pm-market-research/commands/competitive-analysis.md | 47 | ### Step 4: Generate Competitive Analysis | COMMENT |
| LOW | pm-market-research/commands/competitive-analysis.md | 85 | ### Step 5: Offer Next Steps | COMMENT |
| LOW⚡ | pm-data-analytics/commands/analyze-cohorts.md | 20 | ### Step 1: Accept Data or Define Analysis | COMMENT |
| LOW⚡ | pm-data-analytics/commands/analyze-cohorts.md | 26 | ### Step 2: Define Cohorts | COMMENT |
| LOW⚡ | pm-data-analytics/commands/analyze-cohorts.md | 34 | ### Step 3: Analyze | COMMENT |
| LOW | pm-data-analytics/commands/analyze-cohorts.md | 51 | ### Step 4: Generate Report | COMMENT |
| LOW | pm-data-analytics/commands/analyze-cohorts.md | 88 | ### Step 5: Offer Next Steps | COMMENT |
| LOW | pm-data-analytics/commands/write-query.md | 20 | ### Step 1: Understand the Question | COMMENT |
| LOW | pm-data-analytics/commands/write-query.md | 28 | ### Step 2: Determine Schema | COMMENT |
| LOW | pm-data-analytics/commands/write-query.md | 39 | ### Step 3: Generate Query | COMMENT |
| LOW | pm-data-analytics/commands/write-query.md | 49 | ### Step 4: Present and Iterate | COMMENT |
| LOW⚡ | pm-data-analytics/commands/analyze-test.md | 20 | ### Step 1: Accept Test Data | COMMENT |
| LOW⚡ | pm-data-analytics/commands/analyze-test.md | 28 | ### Step 2: Validate Test Design | COMMENT |
| LOW⚡ | pm-data-analytics/commands/analyze-test.md | 38 | ### Step 3: Analyze Results | COMMENT |
| LOW⚡ | pm-data-analytics/commands/analyze-test.md | 48 | ### Step 4: Generate Analysis | COMMENT |
| LOW | pm-data-analytics/commands/analyze-test.md | 96 | ### Step 5: Offer Next Steps | COMMENT |
| LOW⚡ | pm-data-analytics/skills/sql-queries/SKILL.md | 13 | ### Step 1: Understand Your Database Schema | COMMENT |
| LOW⚡ | pm-data-analytics/skills/sql-queries/SKILL.md | 18 | ### Step 2: Process Your Request | COMMENT |
| LOW⚡ | pm-data-analytics/skills/sql-queries/SKILL.md | 23 | ### Step 3: Generate Optimized Query | COMMENT |
| LOW⚡ | pm-data-analytics/skills/sql-queries/SKILL.md | 29 | ### Step 4: Explain and Test | COMMENT |
| LOW⚡ | pm-data-analytics/skills/cohort-analysis/SKILL.md | 13 | ### Step 1: Read and Validate Your Data | COMMENT |
| LOW⚡ | pm-data-analytics/skills/cohort-analysis/SKILL.md | 19 | ### Step 2: Generate Quantitative Analysis | COMMENT |
| 164 more matches not shown… | ||||
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| MEDIUM | validate_plugins.py | 28 | # ─── Configuration ─────────────────────────────────────────────────────────── | COMMENT |
| MEDIUM | validate_plugins.py | 47 | # ─── ANSI Colors ───────────────────────────────────────────────────────────── | COMMENT |
| MEDIUM | validate_plugins.py | 60 | # ─── Helpers ───────────────────────────────────────────────────────────────── | COMMENT |
| MEDIUM | validate_plugins.py | 94 | # ─── Validators ────────────────────────────────────────────────────────────── | COMMENT |
| MEDIUM | validate_plugins.py | 313 | # ─── Main Validator ────────────────────────────────────────────────────────── | COMMENT |
| MEDIUM | .github/workflows/tag-on-merge.yml | 101 | # ── Release gates ──────────────────────────────────────────────────── | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | validate_plugins.py | 289 | def validate_cross_references(plugin_dir: str, skill_names: list[str]) -> ValidationResult: | CODE |
| LOW | tests/test_consistency.py | 59 | def test_marketplace_lists_exactly_the_plugins_on_disk(self): | CODE |
| LOW | tests/test_consistency.py | 69 | def test_sources_point_at_matching_directories(self): | CODE |
| LOW | tests/test_consistency.py | 81 | def test_all_versions_identical_and_match_changelog(self): | CODE |
| LOW | tests/test_consistency.py | 100 | def test_headings_well_formed_dated_unique_descending(self): | CODE |
| LOW | tests/test_consistency.py | 135 | def test_root_readme_headline_counts(self): | CODE |
| LOW | tests/test_consistency.py | 148 | def test_marketplace_description_counts(self): | CODE |
| LOW | tests/test_consistency.py | 164 | def test_root_readme_per_plugin_counts(self): | CODE |
| LOW | tests/test_consistency.py | 184 | def test_plugin_readme_section_counts(self): | CODE |
| LOW | tests/test_consistency.py | 209 | def test_plugin_readme_command_refs_exist(self): | CODE |
| LOW⚡ | tests/test_validator.py | 21 | def test_none_without_frontmatter(self): | CODE |
| LOW⚡ | tests/test_validator.py | 24 | def test_none_when_unterminated(self): | CODE |
| LOW⚡ | tests/test_validator.py | 33 | def test_excludes_frontmatter(self): | CODE |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| MEDIUM | validate_plugins.py | 478 | print(f"Error: {base_path} is not a directory") | CODE |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | validate_plugins.py | 370 | CODE | |
| LOW | tests/test_validator.py | 40 | CODE |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | validate_plugins.py | 260 | # Check if command references skills (informational) | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | validate_plugins.py | 24 | CODE |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | .github/workflows/tag-on-merge.yml | 1 | name: Tag and release from CHANGELOG | COMMENT |