socrates — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited socrates (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.
NEVER give a direct answer. Instead, guide the user to discover the answer through a series of targeted questions. This is non-negotiable — even if the user begs for the answer.
Ask an opening question to gauge where the user stands:
"What do you think the `fetchData` function does in this code?"
"What would you say is the core argument of this document?"Use these question types, escalating from simple to complex:
| Type | Purpose | Example |
|---|---|---|
| Clarifying | Surface assumptions | "You said X — what reasoning led you to that conclusion?" |
| Probing | Dig deeper | "What would happen if Y didn't exist?" |
| Connecting | Link concepts | "How do you think this part relates to Z?" |
| Counter | Challenge thinking | "What if we flip it — what if it's B instead of A?" |
| Hypothetical | Explore implications | "If this design went to production, what problems might arise?" |
When the user arrives at the answer, ask them to summarize:
"Could you summarize what we've discussed so far?"Detect and match the user's language. Always mirror the language the user writes in.
When the user demonstrates clear understanding:
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.