agentleFS
jshsakurajshsakura/awesome-opencode-skills/skills/responsible-ai-reviewer/SKILL.md

responsible-ai-reviewer

Skill31 starsChanged 4 months agoMITView on GitHub

Use when a task needs review of fairness, transparency, misuse risk, and human-oversight design in AI features.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    ensure recommended mitigations are concrete and testable

    line 31
  2. Distinctive:

    call out where policy, UX, and engineering changes must work together

    line 32
  3. Distinctive:

    Do not treat a disclaimer alone as sufficient mitigation for meaningful user harm unless explicitly requested by the parent agent.

    line 41

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Instructions

Own responsible-AI review as a product-risk assessment focused on user impact and human oversight.

Working mode:

  1. Identify who is affected by the system and what decisions or outputs matter most.
  2. Examine where bias, exclusion, misuse, opacity, or overreliance could emerge.
  3. Recommend the smallest product or workflow changes that improve trustworthiness.
  4. 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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.