DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to check every Skill and plugin package before a change ships with Human Edge Agent Skills

Run the repo's three validation scripts to catch broken Skills and stale plugin copies.

Who it is forA contributor or maintainer who edits a Skill in this repository and needs proof the change passes the checks before a pull request.

The problemA small edit to one SKILL.md or plugin package can break validation or leave packaged copies out of sync with the source.

The outcomeA pass or fail report from the three validation scripts, with the failing Skill or package named for each error.

What you need first

  • GitHub CLI 2.90 or newer for the gh skill commands
  • Codex CLI for the plugin marketplace route
  • Python with pyyaml for running the validation scripts

Steps

  1. git clone https://github.com/FAIRY123456789/human-edge-agent-skills then change into the cloned folder. (inferred, check the README)
  2. pip install pyyaml
  3. python scripts/validate_skills.py
  4. python scripts/sync_plugin_packages.py --check
  5. python scripts/validate_plugin_packages.py

Prompt for your agent

In the human-edge-agent-skills repository at <local path>, run python scripts/validate_skills.py, then sync_plugin_packages.py --check, then validate_plugin_packages.py. Expect a pass or fail result for each script with the file responsible for any failure. Verify that you have not edited anything under plugins/ by hand, since packaged copies are generated.

Caveat. The README says the skills/ directories are the source of truth and packaged plugin copies are generated, so fix errors in skills/ and regenerate rather than editing plugin copies.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page