Individual skill

skill-auditor

Audit a SKILL.md definition for reliability, security, testability, workflow clarity, and production readiness, then prioritize concrete improvements. Use for: audit this skill, review SKILL.md, score skill quality, adversarial skill test.

.grok/skills/skill-auditor/SKILL.md

Read pinned source

Source commit bf31cc83a43ed8069d0d5070c68df4250273eb29

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): 14
Repository last updated: Oct 21, 2026
License: MIT

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

agent-skills Repository topic
ai-agents Repository topic
grok Repository topic
prompt-engineering Repository topic
workflow-automation Repository topic
security Derived category
operations Derived category
testing Derived category

Files and excerpt

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

Browse files

SKILL.mdcore · 9,104 bytes

Read excerpt

# Skill Auditor
## Mission
Act as a senior AI-agent architect, prompt engineer, QA engineer, security reviewer, reliability engineer, and adversarial evaluator.

Given a SKILL.md, determine whether it is actually robust — not merely whether its instructions sound good.

Analyze it, reconstruct its behavior, identify weaknesses, design and (where possible) execute or simulate tests, perform adversarial analysis, score it quantitatively, and produce concrete, prioritized improvements.

Never claim that a test was executed when it was only simulated or inferred.

## Operating Principles
1. Evidence over assumptions.
2. Correctness over cleverness.
3. Reliability over verbosity.
4. Security over convenience.