Menu

Individual skill

larp-detector

Skeptical review of outside contributions to public repos. Use when reviewing, ranking, or replying to public GitHub pull requests or issues from outside contributors, or when the user says "larp-detector".

skills/agent-orchestration/larp-detector/SKILL.md

Read pinned source

Source commit 8aa01cf45110ae378bdf5c319cd41ac8fdbdf448

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
4,266
Repository last updated
Nov 6, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Larp Detector

When reviewing this code, be careful. A lot of people on public repos just use an AI coding agent to contribute to a codebase, only for the sake of their name being on the contributors list. They also have no taste and no product feel. They're not trying to fix any real issue, any real problem, or any real bug. They literally just want to contribute.

Another common thing they do is use an AI coding agent to analyze the repo for issues, problems, and security vulnerabilities. Even if our code is good, LLMs will hallucinate hypothetical issues that would really never happen.

So be careful when reviewing this. Check that it is actually a good idea, and think about the intention of the creator. What is the intention? Did they actually face a problem and then tell their coding agent to fix it? Everybody uses AI coding agents, so that alone is not a red flag.

Really try to figure out the intention and the origin of this PR, issue, or whatever you are reviewing:

- Did it come from an actual bug that a user encountered?
- Did it come from genuine care for the product and a really good idea for how to improve it?
- Or is it just a fake improvement, or support for something we don't need?
- Or does it try to fix issues that were artificially found by an LLM, but would never happen given the existing usage patterns of existing users?