Contact
Get in touch
Everything here runs in the open on GitHub, so that is where to reach us — with one exception: security problems go through a private channel first.
Report a vulnerability
Something wrong with this site or the catalog itself — a skill carrying a hidden payload, an endpoint leaking something it should not, a supply-chain problem. Email it rather than opening a public issue, and give us a reasonable window before disclosing. The same address is published at /.well-known/security.txt.
security@securityskills.sh →Bugs and requests
A broken page, a wrong install command, a skill that will not parse, or something you want the site to do. Public issues are fine and preferred — someone else has probably hit it too.
Open an issue →Submit a skill or loop
Use the form — it builds the issue for you and asks for the things a reviewer will need anyway. If you would rather work in git, open a pull request against the catalog directly.
Go to the form →Anything else
Press, partnerships, or a question that does not belong in a public issue tracker. Slower than GitHub, but it reaches a person.
contact@securityskills.sh →Corrections and removal
Something here misattributes your work, is out of date, or should not be listed at all. Say which entry and what is wrong, and we will correct or unpublish it.
Request a change →Before you write
We do not run engagements
This is a catalog, not a consultancy. We cannot test your systems, advise on a live incident, or authorise you to test anything. If a skill here is being used against you, the person running it is responsible for it — not this site.
Nothing here is a support contract
Skills are contributed by their authors. If a specific skill is wrong, the fastest route is usually the author's own repository, linked from the skill page. Use the catalog issues when the problem is with the listing rather than the method.
What we do with what you send
GitHub issues are public and stay public. Do not paste credentials, client names, customer data, or anything from an engagement you are under NDA for. See privacy for what we hold, which is almost nothing.