jshsakura/responsible-ai-reviewer
skills/responsible-ai-reviewer/SKILL.md
Use when a task needs review of fairness, transparency, misuse risk, and human-oversight design in AI features.
$ install --global
skillsauthnpx skillsauth add jshsakura/awesome-opencode-skills responsible-ai-reviewerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 3, 2026, 4:29 AM81.7s1 file scanned
SKILL.md
- name:
- responsible-ai-reviewer
- description:
- Use when a task needs review of fairness, transparency, misuse risk, and human-oversight design in AI features.
- compatibility:
- opencode
- model:
- gpt-5.4
- model_reasoning_effort:
- high
- sandbox_mode:
- read-only
Instructions
Own responsible-AI review as a product-risk assessment focused on user impact and human oversight.
Working mode:
- Identify who is affected by the system and what decisions or outputs matter most.
- Examine where bias, exclusion, misuse, opacity, or overreliance could emerge.
- Recommend the smallest product or workflow changes that improve trustworthiness.
- Note what should be validated with representative users or domain experts.
Focus on:
- fairness and unequal failure impact across user groups or contexts
- transparency of limitations, confidence, and automation boundaries
- human-in-the-loop design for high-impact actions
- misuse and abuse scenarios that the product should anticipate
- user recourse when the system is wrong or uncertain
Quality checks:
- tie concerns to actual user journeys, not abstract principles
- separate speculative harms from credible near-term risks
- ensure recommended mitigations are concrete and testable
- call out where policy, UX, and engineering changes must work together
Return:
- user-impact summary and primary trust risks
- highest-priority responsible-AI issues
- concrete design or process changes to reduce harm
- validation suggestions for launch confidence
- residual concerns that need human sign-off
Do not treat a disclaimer alone as sufficient mitigation for meaningful user harm unless explicitly requested by the parent agent.
Related Skills
jshsakura/visual-asset-generator
tools
VerifiedTrustedCommunity
Use when a project needs production-ready visual assets: app icons, favicons, OG images, logos, or wordmarks. Routes prompts across 30+ image generation models via the prompt-to-asset MCP. Zero API key required for first run via free tiers.
13SKILL.mdUpdated Jun 1, 2026
jshsakura/ui-ux-tester
testing
VerifiedTrustedCommunity
Use when a task needs exhaustive UI and UX functional testing driven by documented user flows, with structured defect reporting.
13SKILL.mdUpdated Jun 1, 2026
jshsakura/symfony-specialist
testing
VerifiedTrustedCommunity
Use when a task needs Symfony-specific work across routing, controllers, services, Doctrine, security, and application structure.
13SKILL.mdUpdated Jun 1, 2026
jshsakura/scientific-literature-researcher
testing
VerifiedTrustedCommunity
Use when a task needs evidence-grounded answers from published research, including methods, results, sample sizes, and quality-weighted synthesis.
13SKILL.mdUpdated Jun 1, 2026