DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to check that an installed Sure Forge copy matches the source with Sure Forge

Confirm that an installed copy of the skill is byte-identical to the repository version.

Who it is forA maintainer or team lead who installed Sure Forge into a shared project and wants to confirm the copy has not drifted.

The problemA copied skill folder can be incomplete or edited, and an agent following a changed copy will behave differently.

The outcomeA verification result that shows whether the installed folder matches the source, plus unit test results.

What you need first

  • An agent host that reads Agent Skill folders, such as Claude Code, Codex, Cursor, Devin CLI, or Hermes Agent
  • Node.js 22.20 or newer for the Skills CLI, or a manual copy of the skills/sureforge/ folder
  • Python 3.11 or newer for the verification scripts

Steps

  1. Clone the Da7-Tech/SureForge repository and open its root folder. (inferred, check the README)
  2. Run python3 -B -m scripts.verify_install --installed path/to/installed/sureforge with the path to your installed copy.
  3. Run python3 -B -m unittest discover -s tests -v to check the package tests.
  4. Note any file the install check reports as different, and reinstall or recopy that file.
  5. Rerun the install check until it passes.

Prompt for your agent

In the Da7-Tech/SureForge repository, run the install verification against <installed skill path> and then the unit tests. Expected output: a pass or a list of mismatched files, and the test summary. Verify that the commands ran from the repository root with Python 3.11 or newer.

Caveat. The README lists these checks, but it does not say how a Python environment should be set up beyond Python 3.11 or newer.

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