AI Slop Code Risk Monitor

alchaincyf/nuwa-skill

SlopCodeMonitor badge for alchaincyf/nuwa-skill Adjusted legacy signal; badge bands: 25 / 50 / 75 (different from dashboard bands).

你想蒸馏的下一个员工,何必是同事。蒸馏任何人的思维方式——心智模型、决策启发式、表达DNA。Distill how anyone thinks.

2.3 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for alchaincyf/nuwa-skill, a Python project with 36,962 GitHub stars. SynthScan examined 37,540 lines of code across 145 source files, recording 60 pattern matches distributed across 7 syntactic categories. The legacy adjusted pattern signal is 2.3 (Low 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.

2.3
Adjusted Signal
2.3
Raw Pattern Score
100%
Time Factor
2026-10-24
Last Push
37.0K
Stars
Python
Language
37.5K
Lines of Code
145
Files
60
Pattern Hits
2026-10-31
Scan Date
0.00
HC Hit Rate

Risk Review · Payload v1

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

Payload schema: 1.0.0 · Engine: 2.0.0 · Scoring: heuristic-density-v1 · Scan date: 2026-10-31.

Cognitive Ownership Risk 10.2/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 0.3/100 · LOW

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

Agent Over-Engineering Ratio 0.5/100 · LOW

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

PR Review Velocity Impact 7.7/100 · LOW

Which changes need focused human review? 60 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 0LOW 60

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 60 distinct pattern matches across 7 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 Overuse50 hits · 75 pts
SeverityFileLineSnippetContext
LOWSKILL.md78#### Step 1: 需求定位COMMENT
LOWSKILL.md116#### Step 2: 候选推荐COMMENT
LOWSKILL.md148#### Step 3: 用户选择COMMENT
LOWSKILL.md440#### Step 1: 读取模板COMMENT
LOWSKILL.md443#### Step 2: 填充内容COMMENT
LOWSKILL.md477### Step 1: 问题分类COMMENT
LOWSKILL.md520#### Step 3: 质量自检COMMENT
LOWSKILL.md523#### Step 4: 输出COMMENT
LOWexamples/andrej-karpathy-perspective/SKILL.md98### Step 1: 问题分类COMMENT
LOWexamples/andrej-karpathy-perspective/SKILL.md116### Step 2: Karpathy式研究(按问题类型选择)COMMENT
LOWexamples/andrej-karpathy-perspective/SKILL.md147### Step 3: Karpathy式回答COMMENT
LOWexamples/steve-jobs-perspective/SKILL.md35### Step 1: 问题分类COMMENT
LOWexamples/steve-jobs-perspective/SKILL.md54### Step 2: 乔布斯式研究(按问题类型选择)COMMENT
LOWexamples/steve-jobs-perspective/SKILL.md85### Step 3: 乔布斯式回答COMMENT
LOWexamples/trump-perspective/SKILL.md92### Step 1: 问题分类COMMENT
LOWexamples/trump-perspective/SKILL.md104### Step 2: 特朗普式研究(按问题类型选择)COMMENT
LOWexamples/trump-perspective/SKILL.md128### Step 3: 特朗普式回答COMMENT
LOWexamples/zhangxuefeng-perspective/SKILL.md36### Step 1: 问题分类COMMENT
LOWexamples/zhangxuefeng-perspective/SKILL.md48### Step 2: 张雪峰式研究(按问题类型选择)COMMENT
LOWexamples/zhangxuefeng-perspective/SKILL.md72### Step 3: 张雪峰式回答COMMENT
LOWexamples/mrbeast-perspective/SKILL.md41### Step 1: 问题分类COMMENT
LOWexamples/mrbeast-perspective/SKILL.md53### Step 2: MrBeast式研究(按问题类型选择)COMMENT
LOWexamples/mrbeast-perspective/SKILL.md77### Step 3: MrBeast式回答COMMENT
LOWexamples/zhang-yiming-perspective/SKILL.md69### Step 1: 问题分类COMMENT
LOWexamples/zhang-yiming-perspective/SKILL.md81### Step 2: 张一鸣式研究(按问题类型选择)COMMENT
LOWexamples/zhang-yiming-perspective/SKILL.md105### Step 3: 张一鸣式回答COMMENT
LOWexamples/taleb-perspective/SKILL.md74### Step 1: 问题分类COMMENT
LOWexamples/taleb-perspective/SKILL.md86### Step 2: 塔勒布式研究(按问题类型选择)COMMENT
LOWexamples/taleb-perspective/SKILL.md114### Step 3: 塔勒布式回答COMMENT
LOWexamples/ilya-sutskever-perspective/SKILL.md36### Step 1: 问题分类COMMENT
LOWexamples/ilya-sutskever-perspective/SKILL.md53### Step 2: Ilya式研究(按问题类型选择)COMMENT
LOWexamples/ilya-sutskever-perspective/SKILL.md87### Step 3: Ilya 式回答COMMENT
LOWexamples/paul-graham-perspective/SKILL.md54### Step 1: 问题分类COMMENT
LOWexamples/paul-graham-perspective/SKILL.md66### Step 2: PG式研究(按问题类型选择)COMMENT
LOWexamples/paul-graham-perspective/SKILL.md91### Step 3: PG式回答COMMENT
LOWexamples/feynman-perspective/SKILL.md55### Step 1: 问题分类COMMENT
LOWexamples/feynman-perspective/SKILL.md73### Step 2: 费曼式研究(按问题类型选择)COMMENT
LOWexamples/feynman-perspective/SKILL.md102### Step 3: 费曼式回答COMMENT
LOWexamples/munger-perspective/SKILL.md61### Step 1: 问题分类COMMENT
LOWexamples/munger-perspective/SKILL.md73### Step 2: 芒格式研究(按问题类型选择)COMMENT
LOWexamples/munger-perspective/SKILL.md101### Step 3: 芒格式回答COMMENT
LOWexamples/naval-perspective/SKILL.md39### Step 1: 问题分类COMMENT
LOWexamples/naval-perspective/SKILL.md51### Step 2: Naval式研究(按问题类型选择)COMMENT
LOWexamples/naval-perspective/SKILL.md76### Step 3: Naval式回答COMMENT
LOWexamples/elon-musk-perspective/SKILL.md68### Step 1: 问题分类COMMENT
LOWexamples/elon-musk-perspective/SKILL.md86### Step 2: 马斯克式研究(按问题类型选择)COMMENT
LOWexamples/elon-musk-perspective/SKILL.md117### Step 3: 马斯克式回答COMMENT
LOWexamples/sun-yuchen-perspective/SKILL.md89### Step 1: 问题分类COMMENT
LOWexamples/sun-yuchen-perspective/SKILL.md101### Step 2: 孙宇晨式研究(按问题类型选择)COMMENT
LOWexamples/sun-yuchen-perspective/SKILL.md128### Step 3: 孙宇晨式回答COMMENT
Hyper-Verbose Identifiers2 hits · 2 pts
SeverityFileLineSnippetContext
LOWexamples/mrbeast-perspective/scripts/thumbnail_audit.py45def check_title_thumbnail_complementarity(title: str, thumb_text: str = "") -> dict:CODE
LOWexamples/mrbeast-perspective/scripts/thumbnail_audit.py123def check_title_curiosity_gap(title: str) -> dict:CODE
Excessive Try-Catch Wrapping2 hits · 2 pts
SeverityFileLineSnippetContext
LOWexamples/mrbeast-perspective/scripts/thumbnail_audit.py167 except Exception as e:CODE
LOW.github/scripts/community_check.py105 except Exception:CODE
Over-Commented Block2 hits · 2 pts
SeverityFileLineSnippetContext
LOW…mrbeast-perspective/scripts/fetch_youtube_subtitles.sh1#!/bin/bashCOMMENT
LOW.github/scripts/community_check.py21import jsonCOMMENT
Deep Nesting2 hits · 2 pts
SeverityFileLineSnippetContext
LOW.github/scripts/community_check.py76CODE
LOW.github/scripts/community_check.py165CODE
Unused Imports1 hit · 1 pts
SeverityFileLineSnippetContext
LOWexamples/mrbeast-perspective/scripts/thumbnail_audit.py23CODE
Fake / Example Data1 hit · 1 pts
SeverityFileLineSnippetContext
LOW.github/scripts/community_check.py65 (r"\bplaceholder\b", "placeholder"),CODE