Contribute

Submit a loop

A loop is a prompt with a stop condition. Send the whole thing — the cycle, why it holds, and above all what has to be true for it to finish. Review happens in the open on GitHub.

Skill13 domains Loop7 in register

Submission

Loop title*Phase*Where in an engagement this loop runs

When to use*One or two sentences, starting “Use this when…”

Done when

What has to be true for the loop to finish? Without this it is a prompt, not a loop.

Stop condition*What that meansHow a reader can tell the condition is actually met

The cycle*One step per line, at least three — the steps that repeat. Why it holds*Why the loop is shaped this way, in a few sentencesPrompt*The text people paste. Name the authorized scope, and say what the loop must stop and ask about.

Your name*CompanyShown on the loop page — optional

ContactLinkedIn or email, shown on the loop page — optional

Lands at

/loops/<loop-title>

I confirm this loop is my own work or openly licensed, that it names an authorized scope, and that it stops and asks rather than acting on production or accepting risk on the operator's behalf.

Still needed

·a loop title
·when to use it
·a stop condition — what has to be true for the loop to finish
·at least three steps in the cycle (0 so far, one per line)
·why it holds
·the prompt itself
·your name
·the confirmation at the bottom

opens a pre-filled issue on github.com/securityskills/skills

What happens next

01
You open an issue
The form builds a pre-filled GitHub issue. Nothing is sent anywhere until you press submit on GitHub itself.
02
A maintainer reviews
A real stop condition, a cycle that repeats only while evidence improves, an authorized scope named in the prompt, and decisions handed back rather than taken.
03
It goes live
Merged loops get a page in the register with a ref, a phase, and a copyable prompt. Nothing to install.