ron-draper — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited ron-draper (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
You can't be Don. Be Ron. A method for the brand moment where a finished idea finally gets its voice — the pitch-room distillation that makes the creator say "oh — yeah, that's exactly it." That reaction is the whole point, and it is not produced by cleverness. It is produced by recognition: surfacing something already true about the product and stating it so plainly it feels inevitable.
Like a certain fictional adman, this skill doesn't invent the product. It works with something real that already exists, gets very close to it, and finds the simple, human line the maker is too close to see. Read this whole file, then pull the reference files as each stage needs them. The crown jewel is Stage 1 — if you internalize one thing, internalize the diagnostic there.
Use it for:
— and needs its incisive name/identity/story before it ships. (This is the sweet spot.)
product, muddy story.
What it needs from the user: deep product knowledge and real stakes — they've lived with the problem enough to know what's broken about the status quo. Users are not required; conviction is.
Don't use it for:
that already exists in the material; it cannot manufacture one from a category and a hunch. If the user is there, tell them gently: live with the problem, define the product, then come back.
The best brand idea is almost always latent in the material you were already given — the name, the model number, the founder's origin story, even an offhand phrase the user dropped while explaining the thing. Your job is to find it, not to manufacture something new and impressive.
Two examples of the move (study the shape, not the specifics):
FG models — "FG" stands for Folk Guitar, and folk literally means the people. The name was one word away the whole time. The reveal wasn't invented; it was excavated.
strike a wrong number with. The double-X was already an audit/redline mark — the logo was hiding in the name.
When you find the real one, the client doesn't say "how creative" — they say "of course." Aim for of course, every time.
Ask a few sharp questions, not a survey. The ones that actually steer the work:
precise-tool / warm-helper). Pick a temperature.
trademark in the name, a trust/credibility tension, a feasibility limit). Name it now, let them decide. See references/method.md → "The honest caveat."
If the conversation already answered these, don't re-ask — extract and confirm. Do not proceed to naming/visuals until feel + audience are pinned. Prefer interactive option-pickers over long prose questions when the surface supports them.
Run this diagnostic, in order. Detailed playbook in references/method.md.
numbers, the origin story, the product's own history, the user's exact offhand phrasings. Hunt for the idea already encoded there. Ask: "what does this name/number/story literally mean, and is the brand's whole thesis hiding in that meaning?" This is the single highest-value move.
both an onramp and a reference tool — the name can only fully serve one"; "the incumbent is friendly-blue 'trust the utility'; this brand only exists because you shouldn't, so it must be the anti-incumbent."* Finding the axis tells you what every later decision optimizes for.
explanation*. Distinguish the rallying-cry (goes under the logo) from the hero line* (states the stakes on landing). See references/method.md → "Compression."
a maven who's done this for decades — show your reasoning so the click happens for them, then list 2–3 runners-up so the choice is legible. Never dump 10 equal options; that abdicates the judgment they came for. See "The maven stance" below.
Gate: get an explicit "yes, that's it" on the kernel before touching color, type, or layout.
Move in this order, confirming at each boundary. Depth in references/visual-craft.md and references/kit-and-handoff.md.
sheet, before a full mockup. Cheaper to course-correct here.
components the product needs — not just a lookbook.
kit-and-handoff.md).Gates matter more than speed. The failure mode is sprinting ahead and handing over a finished kit built on an assumption the user would have corrected in one sentence. When in doubt, show and ask.
reference and verify by rendering. Use scripts/trace_silhouette.py; see visual-craft.md.
with label + icon/arrow + (if relevant) strike-through.
references/method.md — full kernel diagnostic, question bank, reveal-hunting heuristics,compression patterns, the honest-caveat doctrine, the gate checklist.
references/visual-craft.md — "read behind the feel" (extract the system, never lift elements),multi-voice type systems, print/texture tricks, mockup approach, accessibility, and render-and-check.
references/kit-and-handoff.md — the file-kit structure, handoff conventions, and **David'sdefaults** (a clearly-marked, optional layer; strip it for other users).
scripts/trace_silhouette.py — trace a real reference image into a clean SVG outline with correctproportions, and render a PNG to verify by eye. Run it; don't draw geometry from imagination.
assets/BRAND.template.md, assets/tokens.template.css — skeletons to fill, not dictate.The method above is universal — any product, any aesthetic. The specific palettes, fonts, and file conventions you may see referenced are outputs of the method, never templates; don't reuse a past project's look. references/kit-and-handoff.md additionally contains David's workflow defaults (file-kit shape, agent-OS subordination, Claude Code/Codex handoffs). Apply them when working with David; ignore or replace them otherwise — conveniences, not the craft.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.