Control readiness

How many of your controls are ready, and why the rest are not — in scope versus out, the ready share, and the not-ready ones broken down by cause.

Plugin	Area	Access
drata-grc-skills	Compliance & Audit Readiness	Read-only

Purpose

Splits the control library into in-scope and out-of-scope.
Reports what share of in-scope controls are ready.
Breaks the not-ready ones down by cause: test failing, evidence not satisfying readiness, policy not satisfying readiness, or nothing mapped.

Access: This skill cannot change anything in Drata.

MCP tools used

MCP tool	Level	OAuth scope
Get Company	Read	`read:company`
Search Controls	Read	`read:controls`

This skill uses every scope listed above; without them it fails partway through. What any tool returns is bounded by your Drata role as well as the scope — see MCP Server setup.

Run it

Copy

Copied

/plugin marketplace add drata/drata-claude-plugin
/plugin install drata-grc-skills@drata

Then run the skill by name:

Copy

Copied

/drata-grc-skills:drata-control-report

Or ask for it in your own words:

"how many controls are ready"
"why are controls not ready"

Before you start

Connect the Drata MCP server. See MCP Server setup.
Your MCP OAuth configuration must grant the scopes behind the tools listed above.

Related skills

Controls needing work — Two worklists over your not-ready controls — the ones with nothing mapped, and the ones whose manual evidence is out of date — plus any control missing an owner or a description.
Fix controls — Work through control gaps from a single menu with live counts.