Find Release
flutter/flutter
A skill to find the lowest Dart and Flutter release containing a given commit.
Interpret drata-inspector findings generated from drata-cli workflows and turn Drata control, monitor, evidence, personnel, and integration posture into GRC action.
MITAuto-check passed
Install Drata Inspector Expert
$ npx skills add GRCEngClub/claude-grc-engineering --skill drata-inspector-expert -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install GRCEngClub/claude-grc-engineering drata-inspector-expert --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/GRCEngClub/claude-grc-engineering.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/connectors/drata-inspector/skills/drata-inspector-expert .claude/skills/drata-inspector-expert && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "drata-inspector-expert" agent skill from https://github.com/GRCEngClub/claude-grc-engineering/tree/main/plugins/connectors/drata-inspector/skills/drata-inspector-expert into .claude/skills/drata-inspector-expert/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "drata-inspector-expert", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/GRCEngClub/claude-grc-engineering/tree/main/plugins/connectors/drata-inspector/skills/drata-inspector-expertType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add GRCEngClub/claude-grc-engineering --skill drata-inspector-expert -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install GRCEngClub/claude-grc-engineering drata-inspector-expert --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/GRCEngClub/claude-grc-engineering.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/connectors/drata-inspector/skills/drata-inspector-expert .agents/skills/drata-inspector-expert && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "drata-inspector-expert" agent skill from https://github.com/GRCEngClub/claude-grc-engineering/tree/main/plugins/connectors/drata-inspector/skills/drata-inspector-expert into .agents/skills/drata-inspector-expert/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "drata-inspector-expert", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add GRCEngClub/claude-grc-engineering --skill drata-inspector-expert -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install GRCEngClub/claude-grc-engineering drata-inspector-expert --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/GRCEngClub/claude-grc-engineering.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/connectors/drata-inspector/skills/drata-inspector-expert .cursor/skills/drata-inspector-expert && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "drata-inspector-expert" agent skill from https://github.com/GRCEngClub/claude-grc-engineering/tree/main/plugins/connectors/drata-inspector/skills/drata-inspector-expert into .cursor/skills/drata-inspector-expert/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "drata-inspector-expert", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/GRCEngClub/claude-grc-engineering.git --path plugins/connectors/drata-inspector/skills/drata-inspector-expert--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add GRCEngClub/claude-grc-engineering --skill drata-inspector-expert -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install GRCEngClub/claude-grc-engineering drata-inspector-expert --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/GRCEngClub/claude-grc-engineering.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/connectors/drata-inspector/skills/drata-inspector-expert .gemini/skills/drata-inspector-expert && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "drata-inspector-expert" agent skill from https://github.com/GRCEngClub/claude-grc-engineering/tree/main/plugins/connectors/drata-inspector/skills/drata-inspector-expert into .gemini/skills/drata-inspector-expert/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "drata-inspector-expert", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install GRCEngClub/claude-grc-engineering drata-inspector-expertInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add GRCEngClub/claude-grc-engineering --skill drata-inspector-expert -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/GRCEngClub/claude-grc-engineering.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/connectors/drata-inspector/skills/drata-inspector-expert .github/skills/drata-inspector-expert && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "drata-inspector-expert" agent skill from https://github.com/GRCEngClub/claude-grc-engineering/tree/main/plugins/connectors/drata-inspector/skills/drata-inspector-expert into .github/skills/drata-inspector-expert/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "drata-inspector-expert", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add GRCEngClub/claude-grc-engineering --skill drata-inspector-expert -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install GRCEngClub/claude-grc-engineering drata-inspector-expert --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/GRCEngClub/claude-grc-engineering.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/connectors/drata-inspector/skills/drata-inspector-expert .opencode/skills/drata-inspector-expert && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "drata-inspector-expert" agent skill from https://github.com/GRCEngClub/claude-grc-engineering/tree/main/plugins/connectors/drata-inspector/skills/drata-inspector-expert into .opencode/skills/drata-inspector-expert/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "drata-inspector-expert", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
drata-inspector-expert- GitHub stars
- 419
- Token cost
- ~463 tokens
- SKILL.md length
- 176 words
- Files
- 1
- Skills in repo
- 12
- Repo updated
- First seen
- Licence
- MIT
At a glance
Interpret drata-inspector findings generated from drata-cli workflows and turn Drata control, monitor, evidence, personnel, and integration posture into GRC action.
- SKILL.md covers Source, Output Shape, Review Guidance and Remediation Patterns
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Drata Inspector Expert is an agent skill from GRCEngClub/claude-grc-engineering. Interpret drata-inspector findings generated from drata-cli workflows and turn Drata control, monitor, evidence, personnel, and integration posture into GRC action.
Its SKILL.md is about 460 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Open-source GRC toolkit from the GRC Engineering Club. Claude Code plugins for evidence collection, SCF crosswalks, multi-framework gap reports, OSCAL workflows. The licence is MIT.
Example prompts
- “/drata-inspector-expert”
What it can do on your machine
Read from SKILL.md and the folder at commit 784fd9a. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
github.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Drata Inspector Expert loads about 463 tokens when it runs. Until then it costs about 47 tokens; SKILL.md has 176 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from GRCEngClub/claude-grc-engineering at commit 784fd9a, republished under its MIT licence (© GRCEngClub). 176 words, ~463 tokens.
Download SKILL.mdSave it as
.claude/skills/drata-inspector-expert/SKILL.md (or your agent's skills folder).- name
- drata-inspector-expert
- description
- Interpret drata-inspector findings generated from drata-cli workflows and turn Drata control, monitor, evidence, personnel, and integration posture into GRC action.
- license
- MIT
Drata Inspector Expert
Use this skill when reviewing drata-inspector output or planning remediation from Drata workflow findings.
Source
drata-inspector wraps the MIT-licensed drata-cli workflow commands. It does not reimplement Drata APIs and does not require Drata MCP.
Output Shape
Findings are written to:
~/.cache/claude-grc/findings/drata-inspector/<run_id>.jsonResource types:
drata_tenant: summary status across controls, monitors, personnel, and integrationsdrata_control: failing or incomplete controls fromdrata controls failingdrata_monitor: failed automated checks fromdrata monitors failingdrata_connection: disconnected, failed, or never-connected integrationsdrata_personnel: personnel/device compliance issuesdrata_evidence: stale or expiring evidence fromdrata evidence expiring
Review Guidance
- Treat Drata-native control codes as source metadata. The connector emits SCF IDs for normalized downstream reporting.
- Keep Drata as the evidence source of record; use these Findings for cross-framework gap analysis and engineering remediation.
inconclusivemeans adrata-cliworkflow failed or permissions were insufficient.
Remediation Patterns
- Assign owners for ownerless controls.
- Refresh stale evidence and repair disconnected evidence sources.
- Investigate failed monitors before assuming a control is ineffective.
- Resolve personnel device compliance failures or document approved exceptions.
- Reconnect Drata integrations that feed automated evidence.
© GRCEngClub, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in plugins/connectors/drata-inspector/skills/drata-inspector-expert of GRCEngClub/claude-grc-engineering.
Open the folder on GitHubat commit 784fd9a
Compare with similar skills
Drata Inspector Expert next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Drata Inspector Expert this skillGRCEngClub/claude-grc-engineering | 419 | — | ~463 | Automated safety check: Pass | MIT | |
| Find Releaseflutter/flutter | 180k | — | ~545 | Automated safety check: Pass | BSD-3-Clause | |
| Fd Findpenpot/penpot | 61k | — | ~882 | Automated safety check: Pass | MPL-2.0 | |
| TransformerLens InterpretabilityOrchestra-Research/AI-Research-SKILLs | 13k | 3 repos | ~3k | Automated safety check: Pass | MIT | |
| Nnsight Remote InterpretabilityOrchestra-Research/AI-Research-SKILLs | 13k | 2 repos | ~3.3k | Automated safety check: Pass | MIT | |
| Find Matching Tenderssickn33/agentic-awesome-skills | 47k | 1 repos | ~1k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Fd Find
penpot/penpot
A fast and user-friendly alternative to 'find' - simple syntax, smart defaults, respects gitignore.
TransformerLens Interpretability
Orchestra-Research/AI-Research-SKILLs
Guides mechanistic interpretability work with TransformerLens: loading models, caching activations, using HookPoints, activation patching and attention-pattern analysis.
Nnsight Remote Interpretability
Orchestra-Research/AI-Research-SKILLs
Provides guidance for interpreting and manipulating neural network internals using nnsight with optional NDIF remote execution.
Find Matching Tenders
sickn33/agentic-awesome-skills
Find open AU/NZ government tenders matching what a company does, ranked by fit with why and gap analysis.
- Official
Finding Replay For Issue
PostHog/posthog
Finds the most informative session recording linked to an error tracking issue.
More from GRCEngClub/claude-grc-engineering
All 12 skills in this repoTrust Center Builder
GRCEngClub/claude-grc-engineering
Builds and deploys a serverless trust center that publishes a company's compliance posture, with gated access to audit reports and an admin dashboard.
GRC Report Context Bootstrap
GRCEngClub/claude-grc-engineering
Checks that plugins, collected findings and history exist before a GRC /report command runs, and walks the user through setup instead of producing an empty report.
Draw.io Diagram Generator
GRCEngClub/claude-grc-engineering
Generates draw.io diagrams as native .drawio files, including GRC workflows and control maps, with optional PNG, SVG or PDF export that stays editable.
Academic Research Companion
GRCEngClub/claude-grc-engineering
Guide a research project through the full academic lifecycle — from raw idea to concrete research question, literature grounding, methodology, writing, feedback, and publication.
Access Review Triage
GRCEngClub/claude-grc-engineering
Helps you triage a quarterly user access review from an Okta, Azure AD, AWS IAM, GitHub, or generic CSV/JSON export.
Audit Ready PR Reviewer
GRCEngClub/claude-grc-engineering
Reviews pull requests for compliance regressions. An agent skill from GRCEngClub/claude-grc-engineering.
Questions about Drata Inspector Expert
What does Drata Inspector Expert do?
Interpret drata-inspector findings generated from drata-cli workflows and turn Drata control, monitor, evidence, personnel, and integration posture into GRC action. Drata Inspector Expert is an agent skill from GRCEngClub/claude-grc-engineering. Interpret drata-inspector findings generated from drata-cli workflows and turn Drata control, monitor, evidence, personnel, and integration posture into GRC action.
How do I install Drata Inspector Expert in Claude Code?
Run `npx skills add GRCEngClub/claude-grc-engineering --skill drata-inspector-expert -a claude-code`. Or copy the skill folder (plugins/connectors/drata-inspector/skills/drata-inspector-expert in GRCEngClub/claude-grc-engineering) into .claude/skills/drata-inspector-expert in your project. Claude Code loads it when a task matches its description.
How do I install Drata Inspector Expert in Codex?
Run `npx skills add GRCEngClub/claude-grc-engineering --skill drata-inspector-expert -a codex`. Or copy the skill folder (plugins/connectors/drata-inspector/skills/drata-inspector-expert in GRCEngClub/claude-grc-engineering) into .agents/skills/drata-inspector-expert in your project. Codex loads it when a task matches its description.
Can I use Drata Inspector Expert in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add GRCEngClub/claude-grc-engineering --skill drata-inspector-expert -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/drata-inspector-expert, .gemini/skills/drata-inspector-expert, .github/skills/drata-inspector-expert and .opencode/skills/drata-inspector-expert in your project.
What does Drata Inspector Expert need to run?
SKILL.md names no scripts, command-line tools or credentials: Drata Inspector Expert is instructions for the agent only.
Does Drata Inspector Expert access the network?
SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.
Is Drata Inspector Expert safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Drata Inspector Expert use?
Drata Inspector Expert is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Drata Inspector Expert use?
About 463 tokens (SKILL.md is roughly 1.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Drata Inspector Expert?
Skills that share tags, products or a category with Drata Inspector Expert: Find Release (flutter/flutter, 180k stars), Fd Find (penpot/penpot, 61k stars), TransformerLens Interpretability (Orchestra-Research/AI-Research-SKILLs, 13k stars) and Nnsight Remote Interpretability (Orchestra-Research/AI-Research-SKILLs, 13k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Drata Inspector Expert?
GRCEngClub (a GitHub organization) maintains it in GRCEngClub/claude-grc-engineering, which has 419 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on October 4, 2026.
Source: GRCEngClub/claude-grc-engineering on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.