Loading the registry…
Edit or write external-facing prose so it doesn't read as AI-generated. Apply to documentation, blog posts, tutorials, public READMEs, customer-facing slide decks, marketing copy, and competitive briefs — whenever the user asks to write, edit, review, or style-check such content, even if they don't mention AI. Apply when creating this kind of content from scratch. Do NOT apply to internal communications (Slack, Notion, internal PRs, meeting notes) unless the user explicitly asks for a style review. Trigger phrases include "write a blog post", "edit this doc", "review this tutorial", "write copy for", "external-facing", "customer-facing", "public README", "slide deck for customers", "competitive brief", "does this sound AI-generated", "check this for AI tells", "make this less AI", "remove the slop".
Claude Skills are markdown + scripts loaded into Claude Code; scanned with the same pipeline.
We found this by crawling public sources and nobody has attested to it. That is how most of the registry gets here, and it is not a mark against the artifact — it only means no authenticated act of publication is on record. An artifact can be the vendor's own and still appear here.
github_release: https://github.com/reidworks-io/reidworks-skills, 0 findings
Claude Skills install to a single target, no runtime picker.
nerlo install -- 'reidworks-io/reidworks-skills (human-voice)'
Manual alternative: copy the skill folder into ~/.claude/skills/ so Claude Code loads it on next launch.
cp -r -- 'reidworks-io/reidworks-skills (human-voice)' ~/.claude/skills/
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
4 of 11 scanners examined this package. The rest do not apply to it — language, ecosystem and packaging decide which analyzers can say anything, and a scanner that cannot examine an artifact reports nothing rather than passing it.
v2.0.11
11 findings · 8.7s
v0.3.74
1 finding · 0.8s
v0.1.0
0 findings · 3.2s
v0.1.0
0 findings · 8.6s
v1.4.0
None of the entry points this scanner reads were found in this artifact. What each scanner covers
0 findings · 0.2s
v0.1.0
No source files this scanner can analyze were found in this artifact. What each scanner covers
0 findings · 3.2s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.1s
v0.71.0
No dependency manifest or lockfile was found in this artifact. What each scanner covers
0 findings · 0.3s
v2.3.8
No dependency manifest or lockfile was found in this artifact. What each scanner covers
0 findings · 0.2s
v0.71.0
No container image was published for this artifact. What each scanner covers
0 findings · 0.0s
vv1.6.0
No Go modules were found in this artifact. What each scanner covers
0 findings · 0.1s
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 16, 2026 | Caution93 | — | agentshield ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral ·n/a: not applicablenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source: completetrivy ·n/a: not applicableosv-scanner ·n/a: not applicabletrivy_image ·n/a: not applicablegovulncheck ·n/a: not applicable | completed |
Findings in files this artifact installs stand as reported; a model re-read the rest and said which ones it believes are false positives. This is a second opinion published beside the evidence, not a correction to it: the per-scanner reports above are unchanged, every dismissed finding is still listed there at its original severity, and the score and the Caution badge are computed from those raw severities alone. Nothing below moved them.
This review has not run for this scan yet. It runs once per scan, in the background, and is kept; it appears here when it has. Until then all 12 findings above stand exactly as their scanners reported them, at full severity.