Install any skill in seconds. Free to start, no credit card required.
Get Started Free →grcengclub/drata-inspector-expert
Interpret drata-inspector findings generated from drata-cli workflows and turn Drata control, monitor, evidence, personnel, and integration posture into GRC action.
Passed 21 of 24 test cases with the skill, and 13 of 24 without it.
and 5 more in the full report
8 fixed13 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
When running the drata-inspector workflow, which command-line interface tool does it execute under the hood to pull audit findings?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies drata-cli as the underlying tool wrapped by drata-inspector. | Missed | Passed |
The instructions your model reads when the skill loads.
Use this skill when reviewing drata-inspector output or planning remediation from Drata workflow findings.
drata-inspector wraps the MIT-licensed drata-cli workflow commands. It does not reimplement Drata APIs and does not require Drata MCP.
Findings are written to:
~/.cache/claude-grc/findings/drata-inspector/<run_id>.json
Resource types:
drata_tenant: summary status across controls, monitors, personnel, and integrationsdrata_control: failing or incomplete controls from drata controls failingdrata_monitor: failed automated checks from drata monitors failingdrata_connection: disconnected, failed, or never-connected integrationsdrata_personnel: personnel/device compliance issuesdrata_evidence: stale or expiring evidence from drata evidence expiringinconclusive means a drata-cli workflow failed or permissions were insufficient.test cases passed, vs 13 / 24 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.