/finding-generator
Generates professional audit findings using the Condition-Criteria-Cause-Effect format. Creates management letter comments and remediation recommendations.
$ npx -y skills add GRCEngClub/claude-grc-engineering --skill finding-generator --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/finding-generator
Context preview
The summary Claude sees to decide when to auto-load this skill.
Generates professional audit findings using the Condition-Criteria-Cause-Effect format. Creates management letter comments and remediation recommendations.
SKILL.md
finding-generator.SKILL.mdname: finding-generator
description: Generates professional audit findings using the Condition-Criteria-Cause-Effect format. Creates management letter comments and remediation recommendations.
allowed-tools: Read, Write
Finding Generator
Creates professional audit findings and management letter comments.
Capabilities
- **Finding Documentation**: Structures findings per professional standards
- **Root Cause Analysis**: Identifies underlying causes of deficiencies
- **Risk Assessment**: Evaluates finding severity and impact
- **Remediation Guidance**: Provides actionable recommendations
Finding Format (CCCE)
- **Condition**: What was found (the deficiency)
- **Criteria**: What should be (the standard/requirement)
- **Cause**: Why it happened (root cause)
- **Effect**: What could result (risk/impact)
Finding Severity Levels
- **High**: Material weakness, significant deficiency
- **Medium**: Control deficiency with moderate risk
- **Low**: Opportunity for improvement
Output Formats
- Formal audit findings with management response sections
- Management letter comments
- Gap analysis reports
- Remediation tracking worksheets
Example Usage
When documenting an access control finding:
- Condition: 3 of 25 terminated users retained access for >30 days
- Criteria: Policy requires access removal within 24 hours
- Cause: Manual termination process lacks HR integration
- Effect: Risk of unauthorized access to sensitive data
Read more
name: finding-generator description: Generates professional audit findings using the Condition-Criteria-Cause-Effect format. Creates management letter comments and remediation recommendations. allowed-tools: Read, Write
Finding Generator
Creates professional audit findings and management letter comments.
Capabilities
- **Finding Documentation**: Structures findings per professional standards
- **Root Cause Analysis**: Identifies underlying causes of deficiencies
- **Risk Assessment**: Evaluates finding severity and impact
- **Remediation Guidance**: Provides actionable recommendations
Finding Format (CCCE)
- **Condition**: What was found (the deficiency)
- **Criteria**: What should be (the standard/requirement)
- **Cause**: Why it happened (root cause)
- **Effect**: What could result (risk/impact)
Finding Severity Levels
- **High**: Material weakness, significant deficiency
- **Medium**: Control deficiency with moderate risk
- **Low**: Opportunity for improvement
Output Formats
- Formal audit findings with management response sections
- Management letter comments
- Gap analysis reports
- Remediation tracking worksheets
Example Usage
When documenting an access control finding:
- Condition: 3 of 25 terminated users retained access for >30 days
- Criteria: Policy requires access removal within 24 hours
- Cause: Manual termination process lacks HR integration
- Effect: Risk of unauthorized access to sensitive data
Open-source GRC Engineering resource for Claude. claude-grc-engineering turns technical evidence from cloud, SaaS, code, and security tools into framework-aligned findings, gap reports, remediation guidance, evidence packages, and OSCAL workflows.
Repo: GRCEngClub/claude-grc-engineering
Other skills on trust-center.
- /academic-research-companion
Guide a research project through the full academic lifecycle — from raw idea to concrete research question, literature grounding, methodology, writing, feedback, and publication. Use this skill whenever the user shares a research idea, asks to "flesh out" a topic, wants sources
Open skill - /aws-inspector-expert
Expertise in evaluating AWS accounts for compliance — what checks are meaningful, which SCF controls they map to, and how to interpret aws CLI output.
Open skill - /azure-inspector-expert
Expertise in evaluating Azure subscription findings from azure-inspector and mapping them to SCF controls.
Open skill - /crowdstrike-inspector-expert
Interpret CrowdStrike Falcon findings for sensor coverage, policy visibility, and host group scoping.
Open skill - /datadog-inspector-expert
Interpret datadog-inspector findings and translate Datadog monitoring, audit, log-retention, SSO, and RBAC results into GRC evidence and remediation.
Open skill - /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.
Open skill

