Add a rule-audit skill: offline static analysis of AI system prompts

Open
#590 4 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

  • #589 by @roli-lpci — closed without merging

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
78/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
python
Domain
tooling

Research direction

Start by comparing existing skills to the AgentSkills progressive-disclosure format, then inspect the category list in the README and the registration structure in marketplaces/openhands-extensions.json. Add skills/rule-audit/SKILL.md and adapter scripts that import rule_audit from a plain pip install rule-audit environment; done when the marketplace JSON parses and all acceptance criteria are met.

Written by the indexing model from the issue text.

Description

Desired Behavior

The extensions catalog should include a skill for static analysis of AI system prompts / agent rule files: detecting contradictory rules, coverage gaps, priority ambiguities, and meta-paradoxes before they cause runtime agent misbehavior. It should run fully offline (no model calls, deterministic), so it can be used in CI.

The rule-audit analyzer (PyPI: rule-audit, MIT) provides this; packaging it as an AgentSkills-format skill under skills/rule-audit makes it usable from OpenHands directly.

Acceptance Criteria
  • skills/rule-audit/SKILL.md exists and follows the AgentSkills progressive-disclosure format used by other skills in this repo
  • Skill is registered in marketplaces/openhands-extensions.json with a valid category from the README's category list
  • Bundled adapter scripts import rule_audit from a plain pip install rule-audit environment without modification
  • Marketplace JSON parses as valid JSON
Dominant language
Python
Stars
184
Forks
137
Avg merge
1d 19h
Merged PRs (30d)
46

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OpenHands/extensions

All issues in OpenHands/extensions

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.