Project analyse critique
Skill JasonWarrenUK/goblin-mode/skills/project-analyse-critique
{{ πππ }} Probe the project for architectural weaknesses, technical debt, and risk β a deliberately critical read, not a balanced overviewFrom its SKILL.md
npx -y skills add JasonWarrenUK/goblin-mode --skill project-analyse-critiqueAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.1 KB, 109 tokens by cl100k_base, as published. Nobody here has run it
Repo Critique
<overview> Identify weaknesses in this codebase's implementation. </overview> <steps> <step num="1">Analyse the codebase as a developer would when reading unfamiliar code.</step> <step num="2">If $ARGUMENTS contains content, focus analysis on that area.</step> <step num="3">Provide practical overview of weaknesses in implemented code only (not missing features).</step> </steps> <inputs> $ARGUMENTS </inputs>What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most review quality skills give in 109 tokens
Counted across 1,048 of the 1,783 authors here whose files we hold, read 2026-08-07
- Ask questions one at a timein 81 of 1048, across 64 files
- Provide a recommended answer for each questionin 73 of 1048, across 50 files
- Explore the codebase instead of asking answerable questionsin 66 of 1048, across 42 files
- Resolve dependencies between decisions one-by-onein 42 of 1048, across 17 files
- Interview the user relentlessly about the planin 38 of 1048, across 13 files
- Order findings by severityin 31 of 1048
- Resolve each branch of the decision treein 27 of 1048, across 5 files
- Run a grilling sessionin 26 of 1048, across 5 files
- Update CONTEXT.md immediately when a term is resolvedin 26 of 1048, across 11 files
- Propose precise canonical terms for vague languagein 25 of 1048, across 7 files
- Create documentation files lazilyin 24 of 1048, across 5 files
- Assign severity to every findingin 24 of 1048
Said here and by no other author read
- analyze the codebase as an unfamiliar developer would
- provide practical overview of implemented code weaknesses
- evaluate architectural weaknesses and technical debt
- perform a deliberately critical read
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.