Contribute a skill, with your AI
You do not need to know git. Paste this into your agent and answer its questions about one GRC job you do well.
The contribution prompt
Read https://github.com/better-isms/grcskills/blob/main/skills/.system/submit-skill/SKILL.md and follow it. Interview me about one GRC job I do well, including my thresholds, examples and the mistakes I see, draft it in the grcskills format, validate it, show me the files, and submit it as a pull request once I say yes.
Your agent shows you every file before it submits anything.
What your agent does
- Interviews youYour thresholds, examples and the mistakes you see, for one job.
- Drafts the skillOne SKILL.md in the library format, with a “What good looks like” section and hard rules.
- Validates itRuns
node tools/validate.mjsand fixes every line it reports. - Opens the pull requestOnly after you say yes. Without git, it files a “Submit a skill” issue instead.
What happens after
- Automatic checksCI runs the validator with a read-only token. An outside pull request may only change its own
skills/<your-slug>/folder. - Security gateA skill runs inside other people’s environments, so it may never send data off the machine, download or run code, read credentials, address reviewers or skip the reader’s approvals.
- Content reviewNo text from any standard, a framework accuracy challenge, and a second model that did not write the skill.
- The founder approves the mergeEvery outside merge needs his approval of the exact commit. Automated verdicts are advisory and never merge outside text.
Credit, not contact details
Your author page shows your name, title, LinkedIn profile and company domain, never an email address. Profiles go live once we confirm the LinkedIn profile is yours. Ask for a correction or removal at any time by opening an issue.
Found a problem in a skill?
Report it privately through a GitHub security advisory, not a public issue. A confirmed bad skill is reverted and a new release is cut.